Re: [CR] Wooljersey - NOW: Backup Strategies

(Example: Production Builders:Peugeot)

Date: Sat, 1 Aug 2009 22:31:12 -0500
From: "John Thompson" <johndthompson@gmail.com>
Organization: The Crimson Permanent Assurance
To: <classicrendezvous@bikelist.org>
References: <20090724180251.8A6B819D8D@ug6.ece.ubc.ca>
In-Reply-To: <20090724180251.8A6B819D8D@ug6.ece.ubc.ca>
Subject: Re: [CR] Wooljersey - NOW: Backup Strategies


On 07/24/2009 01:02 PM, donald gillies wrote:
> By the way, for backup on a Linux or UNIX machine, the easiest
> strategy is as follows :
>
> 1. Create a 'find' command that traverses the file system to be
> backed up (i.e. web pages), copying files over to a 2nd file
> system on a second volume, on a second disk.
>
> this is easy to do because you can interactively type
> in find commands and see the results, to make sure you
> have the correct 'find' command.
>
> 2. Edit the periodic process-scheduling file, /etc/crontab (as
> root) or us the "at" or "atrun" command (depends on your
> system type), to schedule the 'find' command to copy files
> onto the backup volume EVERY NIGHT. You can use the 'newer'
> attribute of find to copy only files that have been updated.
>
> 3. If your disk crashes, just re-install UNIX and then copy the
> latest backup image of the file system over to the new UNIX
> file system.
>
> If you need details, please contact me off-list. It's something
> I've done before, on my personal UNIX system(s).

I use dump/restore on my *nix systems (linux, FreeBSD, NetBSD). This provides incremental backups, an interactive restore capability, and on linux (with LVM) and FreeBSD at least the ability to safely back up live file systems.

--

-John Thompson (john@os2.dhs.org)
Appleton WI USA