From: sabujp <bac...@ba...> - 2009-02-19 19:40:25
|
> Hard-links cannot cross > filesystems, so creating a second filesystem won't work. Your only > choice would be to create a second BackupPC instance and move clients > over to the new instance. > Well this is possible using the instructions here: http://backuppc.wiki.sourceforge.net/move_backup_data+ or in the manual under "Copying the pool". I've started this process (moving several TB) but my only question is regarding the commands from the manual here: su __BACKUPPCUSER__ cd NEW_TOPDIR mkdir pc cd pc __INSTALLDIR__/bin/BackupPC_tarPCCopy __TOPDIR__/pc | tar xvPf - In the last command that runs BackupPC_tarPCCopy, does this perl command look at any of the configuration files on the local host or does it just get what it needs to re-generate the hard links straight from the old "pc" directory? I looked through the code and don't see that it does look at the local system's backuppc configuration files under /etc/BackupPC . What I'm doing is the following: I have two BackupPC servers host1 and host2. I'm copying the BackupPC directories from a SAN (san2) attached to host2 to the SAN attached to host1 (san1) . Both SANs are available to both hosts through a FC switch so I just umount it on host2 and re-mount it on host1. I then copy the cpool and pool directories to host1's san1. After this is finished I plan on running BackupPC_tarPCCopy on host1 (san1) against the pc directory on san2. Just wanted to make sure BackupPC_tarPCCopy wasn't going to look at host1:/etc/BackupPC/hosts and try something funny . Finally I'll reformat san2 from xfs to jfs (xfs is very unstable on apple g5 xserves) and then do the same thing again to move the backuppc pool, cpool, and pc directories back to san2. Thanks, Sabuj Pattanayek +---------------------------------------------------------------------- |This was sent by sa...@gm... via Backup Central. |Forward SPAM to ab...@ba.... +---------------------------------------------------------------------- |