Help With Restoring
jw schultz
jw at pegasys.ws
Thu Jan 9 04:35:00 EST 2003
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, mhanze at hanzehome.com wrote:
> > > 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 /*
> > > CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/current && echo
> "Daily
> > > backup ran on `date`" >> /var/log/backup.log
> >
> > Notice that if you have any dotfiles in / (that is, flies that begin
> with
> > a "."), this will not copy them, but normally you wouldn't have dotfiles
> > in / so it shouldn't matter. Might want to start using / instead of /*
> > from now on though, just for good form.
>
>
> Thanks fot the tip :)
>
>
> >
> > > This has been working fine and I've even been able to restore files
> using
> > > scp from time to time. now I'm faced with a bare metal recovery cause
> of a
> > > botched upgrade from Redhat 7.1 to 8.0 that failed half way through.
> This
> > > machine was still accessible via console and ssh (putty). I signed in
> via
> > > ssh and ran...
> > >
> > > # cd /
> > > # scp -r CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/.* .
>
> > >
> > > This was running for a while and then i lost my connection and cant
> > > reconnect. I won't have console access till the morning but any advice
>
> > > would be greatly appreciated.
> >
> > Don't you mean:
> >
> > scp -rp CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/. .
> >
> > ?
> >
> > The command you list above won't copy anything, since there are no
> > dotfiles in the root directory. Also, you have backup2 in the rsync
> > command and backup1 in the scp command.
> >
> > Maybe that was just a typo though...
>
>
> As never having restored anything more that a few files at a time as the
> Linux newbie that I am, I'm sure i was off. Thanks for the tip again :)
> Typo it was. Should have been backup2 in the scp command.
>
>
> >
> > One final thought. Sometimes scp has issues with symlinks (as in,
> copying
> > the target instead of the link). Might want to use:
> >
> > cd /
> > rsync -av CENTRAL_SERVER_IP:/backup1/BACKED_UP_SERVER_FQDN/current/ .
>
>
> I will try this first thing in the morning when I have console access.
>
> Just one more thing; Based on the script I use, am I SOL or with a little
> elbow greese in the morning get my server back?
>
>
> Thank you for your time and advice. I really appreciate it!!!!!
>
> Mark
>
> >
> > Mike
> >
> > --
> > To unsubscribe or change options: http://lists.samba.
> > org/mailman/listinfo/rsync
> > Before posting, read:
> http://www.tuxedo.org/~esr/faqs/smart-questions.html
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw at pegasys.ws
Remember Cernan and Schmitt
More information about the rsync
mailing list