I'm very interested in this...
My question(s) are why did you have to install a minimal system?
Could you have just booted up with network and rsync and just rsynced to a
freshly paritioned/formatted disk?
What command did you use (to clarify) to make the origal rsync's of your
disk, and what
Dr. Poo [EMAIL PROTECTED] wrote
on 01/11/2003 09:25:18 AM:
I'm very interested in this...
My question(s) are why did you have to install a minimal system?
Could you have just booted up with network and rsync and just rsynced
to a
freshly paritioned/formatted disk?
And your probably
To Mike and the Rsync community,
This is by far
the greatest utility I have ever used for backing up an entire system.
My Redhat server got botched during an upgrade. I reformatted my partitions
and installed a minimal system. Rsync'ed the entire / directory back and
the server came back to
Hi All,
I have been using rsync to backup to a central
server with a 7 day incremental script on 2 Redhat boxen.
#!/bin/sh
PATH=/usr/local/bin:/usr/bin:/bin
DAY=`date +%A`
export PATH DAY
[ -d /root/emptydir ] || mkdir /root/emptydir
rsync --rsh=/usr/bin/ssh --delete -a
rsync --delete --stats --compress --recursive --times --perms --links
--rsh=/usr/bin/ssh --exclude tmp/ --exclude dev/ --exclude proc/
--exclude backups/ --delete-excluded --backup
--backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /*
rsync --delete --stats --compress --recursive
--times --perms --links
--rsh=/usr/bin/ssh --exclude tmp/ --exclude dev/
--exclude proc/
--exclude backups/ --delete-excluded --backup
--backup-dir=/backup2/BACKED_UP_SERVER_FQDN/$DAY -a /*
Using rsync on to restore / might be OK because it creates
copies and then renames but in general it is a bad idea to
try to restore / in-place.
Better to boot from other media, mount root c on another tree
and then restore there.
On Wed, Jan 08, 2003 at 11:20:09PM -0500, [EMAIL PROTECTED]
