[TriLUG] backup methodology
Jason Tower
jason at cerient.net
Thu Feb 20 17:05:18 EST 2003
as long as it's only a couple of gigs, and it's only moving across the lan, i
wouldn't bother with tar/incremental backups unless space on the backup
server is really tight. using the rsync method that jeremy linked to earlier
is probably the best bet, or just copy the files directly if you're really
lazy like me. make a seperate directory for each day of the week and use a
cron job to copy data to the appropriate directory on the appropriate day.
that way if you need to restore a file from three days ago you can do it in
about three seconds. if you have the space for it save the friday
directories and rotate them so you always have three or four, that way you
can go back a month or so if necessary.
jason
On Thursday 20 February 2003 16:37, Mike M wrote:
> On Thursday 20 February 2003 16:10, Jason Tower wrote:
> > depends on what you are backing up to: tape, second internal disk, remote
> > server on lan, ftp/rsync site on wan, etc.
>
> remote server on lan; burn CDs periodically is possible
>
> > also depends on what the
> > downtime/offline maximums are: overnight, an hour, five minutes, five
> > seconds.
>
> 3-4 am is best
>
> > and finally how much data are we talking about: a couple of gigs
> > or a couple hundred gigs?
>
> couple of gigs
>
> > jason
> >
> > On Thursday 20 February 2003 16:06, Mike M wrote:
> > > What works best for backing up disks:
> > >
> > > A) tar everything; keep last N revisions
> > > B) tar everything once every N iterations; tar incremental changes for
> > > all other iterations
> > > C) tar everything; keep everthing; space is cheap; labor is not
> > > D) something else
More information about the TriLUG
mailing list