Re: [CR] Wooljersey - NOW: Backup Strategies

(Example: Production Builders:Cinelli:Laser)

Date: Fri, 24 Jul 2009 11:56:12 -0700
From: <mrrabbit@mrrabbit.net>
To: donald gillies <gillies@ece.ubc.ca>
References: <20090724180251.8A6B819D8D@ug6.ece.ubc.ca>
In-Reply-To: <20090724180251.8A6B819D8D@ug6.ece.ubc.ca>
Cc: classicrendezvous@bikelist.org
Subject: Re: [CR] Wooljersey - NOW: Backup Strategies


RSNAPSHOT...is what you just described the rough equivalent of in manual terms...

Robert Shackelford San Jose, CA USA

Quoting donald gillies <gillies@ece.ubc.ca>:
> 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).
>
> - Don Gillies
> San Diego, CA, USA
> _______________________________________________
>
>
> --
> PRIVACY WARNING: For auditing purposes, a copy of this message has been
> saved in a permanent database.
>

--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.