Backup Central

Hello,
I am testing BackupPC to do backups for the purpose of disaster recovery. However, I always get similar errors during restore.
I do my restore by booting Knoppix on a different host than the one I backed up, but with similar hardware. I create the partitions, format them, mount them, setup ssh and do the restore from the CGI interface. These are some of the errors I get:
Remote[1]: rsync: symlink "bin/csh" -> "/etc/alternatives/csh": No such file or directory
Remote[1]: rsync: symlink "bin/mt" -> "/etc/alternatives/mt": No such file or directory
Remote[1]: rsync: symlink "bin/pidof" -> "../sbin/killall5": No such file or directory
Remote[1]: rsync: symlink "bin/rbash" -> "bash": No such file or directory
Remote[1]: rsync: symlink "bin/sh" -> "bash": No such file or directory
Remote[1]: rsync: symlink "boot/boot.b" -> "boot-menu.b": No such file or directory
Remote[1]: rsync: symlink "dev/MAKEDEV" -> "/sbin/MAKEDEV": No such file or directory
Remote[1]: rename .arch.WrVolA -> bin/arch : No such file or directory
Remote[1]: rename .bash.I72QU2 -> bin/bash : No such file or directory
Remote[1]: rename .cat.Ya7Ssy -> bin/cat : No such file or directory
Remote[1]: rename .chgrp.SQof23 -> bin/chgrp : No such file or directory
Remote[1]: rename .chmod.M4f1Bz -> bin/chmod : No such file or directory
Remote[1]: rename .chown.CukKY7 -> bin/chown : No such file or directory
Remote[1]: rename .cp.CXZmsG -> bin/cp : No such file or directory
Remote[1]: rename .cpio.Ca5Cnf -> bin/cpio : No such file or directory
Remote[1]: rename .date.UYG0FM -> bin/date : No such file or directory
Remote[1]: rename .dd.MDII6j -> bin/dd : No such file or directory
Remote[1]: rename .df.2G6mxU -> bin/df : No such file or directory
Remote[1]: rename .dir.2jLe6u -> bin/dir : No such file or directory
Remote[1]: rename .dmesg.oMe2A6 -> bin/dmesg : No such file or directory
Remote[1]: rename .dnsdomainname.eAJWLF -> bin/dnsdomainname : No such file or directory
Remote[1]: rename .echo.QcycYe -> bin/echo : No such file or directory
I actually get many more, but you get the idea.
I first noticed these errors when I tried to 'chroot /mnt/sda1' and it could not find /bin/sh. The Home page for the host says the restore was successful, but it also says there were xferErrs.
If I do a second restore over the first restore, either full or just the files that had errors, then I do not get any errors and I am able to chroot, run lilo and reboot into a host that looks just like the one I backed up.
Do any of you know how to prevent these errors?
Thanks,
Chris

On Mon, 2004-06-28 at 14:01, Ruddy, Chris wrote:

If I do a second restore over the first restore, either full or just
the files that had errors, then I do not get any errors and I am able
to chroot, run lilo and reboot into a host that looks just like the
one I backed up.

It sounds like rsync is trying to restore files before the
directory that contains them and the remote rsync isn't
willing to create them on demand - not sure what to do
about it, though. Maybe tar would work better for a
bare metal restore.

---
Les Mikesell
les < at > futuresource.com




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

On 06/28 02:14 , Les Mikesell wrote:
It sounds like rsync is trying to restore files before the
directory that contains them and the remote rsync isn't
willing to create them on demand - not sure what to do
about it, though. Maybe tar would work better for a
bare metal restore.

I always just used tar over netcat or ssh for my test bare-metal restores.
(and the one I did for real).

and yes, I used Knoppix too.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

I am testing BackupPC to do backups for the purpose of disaster recovery.
However, I always get similar errors during restore.

I do my restore by booting Knoppix on a different host than the one I backed
up, but with similar hardware. I create the partitions, format them, mount
them, setup ssh and do the restore from the CGI interface. These are some
of the errors I get:

Remote[1]: rsync: symlink "bin/csh" -> "/etc/alternatives/csh": No such file
or directory
Remote[1]: rsync: symlink "bin/mt" -> "/etc/alternatives/mt": No such file
or directory
Remote[1]: rsync: symlink "bin/pidof" -> "../sbin/killall5": No such file or
directory
Remote[1]: rsync: symlink "bin/rbash" -> "bash": No such file or directory
Remote[1]: rsync: symlink "bin/sh" -> "bash": No such file or directory
Remote[1]: rsync: symlink "boot/boot.b" -> "boot-menu.b": No such file or
directory
Remote[1]: rsync: symlink "dev/MAKEDEV" -> "/sbin/MAKEDEV": No such file or
directory
Remote[1]: rename .arch.WrVolA -> bin/arch : No such file or directory
Remote[1]: rename .bash.I72QU2 -> bin/bash : No such file or directory
Remote[1]: rename .cat.Ya7Ssy -> bin/cat : No such file or directory
Remote[1]: rename .chgrp.SQof23 -> bin/chgrp : No such file or directory
Remote[1]: rename .chmod.M4f1Bz -> bin/chmod : No such file or directory
Remote[1]: rename .chown.CukKY7 -> bin/chown : No such file or directory
Remote[1]: rename .cp.CXZmsG -> bin/cp : No such file or directory
Remote[1]: rename .cpio.Ca5Cnf -> bin/cpio : No such file or directory
Remote[1]: rename .date.UYG0FM -> bin/date : No such file or directory
Remote[1]: rename .dd.MDII6j -> bin/dd : No such file or directory
Remote[1]: rename .df.2G6mxU -> bin/df : No such file or directory
Remote[1]: rename .dir.2jLe6u -> bin/dir : No such file or directory
Remote[1]: rename .dmesg.oMe2A6 -> bin/dmesg : No such file or directory
Remote[1]: rename .dnsdomainname.eAJWLF -> bin/dnsdomainname : No such file
or directory
Remote[1]: rename .echo.QcycYe -> bin/echo : No such file or directory

I actually get many more, but you get the idea.

I first noticed these errors when I tried to 'chroot /mnt/sda1' and it could
not find /bin/sh. The Home page for the host says the restore was
successful, but it also says there were xferErrs.

If I do a second restore over the first restore, either full or just the
files that had errors, then I do not get any errors and I am able to chroot,
run lilo and reboot into a host that looks just like the one I backed up.

Do any of you know how to prevent these errors?

What version of rysnc are you using?

I tried a simple test with symlinks that will be created by
rsync before the target files, and it works fine for me.

The rename errors imply that the subdirectory has not been created
or has the wrong permissions. After the first pass, does the
bin directory exist, and if so what permissions does it have?
Is rsync running as root?

Craig


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

What version of rysnc are you using?

rsync version 2.5.6 protocol version 26

The rename errors imply that the subdirectory has not been created or has
the wrong permissions. After >the first pass, does the bin directory exist,
and if so what permissions does it have? Is rsync running >as root?

After the first pass, the bin directory exists with "drwxr-xr-x"
permissions.

Rsync is running as root.

Thanks,
Chris

"Ruddy, Chris" writes:

What version of rysnc are you using?

rsync version 2.5.6 protocol version 26

The rename errors imply that the subdirectory has not been created or has
the wrong permissions. After >the first pass, does the bin directory exist,
and if so what permissions does it have? Is rsync running >as root?

After the first pass, the bin directory exists with "drwxr-xr-x"
permissions.

Rsync is running as root.

Hmmm, I wish I could re-create this - I tried but the symlinks
are created correctly the first time for me. I tried various
cases of symlinks pointing to files that don't yet exist
(ie: further down the sorted list of file names), and ones
that do exist (earlier in the sorted list).

Next question: what is the client machine's OS?

Would you mind trying it with rsync 2.6.2?

Craig