Brown, Wade ASL (GE Healthcare) wrote:
If we had the hash values saved when BackupPC_link runs, we could reconnect the links much faster.
I thought the pool filenames *were* the hash. If that's true, then they are already "saved" and available.
In the case of an off-site backup, I wonder if the cpool could get copied directly and the per-pc files are changed such that they are no longer hardlinks but simply contain the hash.
I don't see why not. Just change the hardlink into a file whose contents are the name of the pool file it pointed to. That seems like trival one liner in a script, both converting and unconverting the link. Since it seems too easy, there must be a "gotcha" which I am missing!
The idea here is to reduce the time it takes to make the offsite copy. Obviously, to pull it back, some reconstruction needs to take place. But that's only in the event of disaster, right?
Not necessarily. If it's trivial to make a duplicate pool, then you would have an easy way to keep a hot-standby (offsite) backuppc server, which I think is usually the goal. Again, there must be a "gotcha" because somebody would have done it by now. :-)
------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
