05-20-2008 08:17 AM
11-04-2008 03:59 AM
12-06-2008 02:24 PM
12-08-2008 01:43 AM
Hi
Yes this works well, as long as BESR 'thinks' it's connecting to the same device name and sees the files it's expecting, then no problem.
All we are talking about is changing the IP Address.
However there is another issue here and that is if the on-site storage device is not the same device as the BESR server then off-site copying is done at a much lower speed than you would expect, as it would seem that the BESR server first copies the data from the on-site storage device then copies it again to the off-site device. I now use ftp directly between the on-site and off-site devices with a four fold speed increase.
Steve
12-09-2008 08:54 AM
04-22-2009 09:11 AM
don't know if anyone is still interested in this, but here is what I did to seed my off-site storage.
1. Locally I set up a Xenserver virtual machine with a USB attached drive and defined the share for off-site copy to use. I used DHCP for the IP addressing, and the UNC path always used just the host name.
2. I shut down the VM and copied it to another USB drive.
3. At the off-site location, I imported the VM from the second USB drive which retained the attached USB drive.
4. The powered up VM was the same machine with same USB drive and network share but with a different IP.
4. Subsequent incremental wrote correctly because the UNC path to the off-site storage was still retained.
5. I then migrated the USB storage via XenCenter to a new SAN location of the storage repository.
Since this took a long time (18 hours or so) I disabled backups for one day.
6. I then resumed normal backups and since the UNC path was identical for off-site storage, incremental resumed.
05-21-2009 03:10 AM
05-29-2009 04:15 AM
05-29-2009 06:59 AM