Guus Houtzager wrote:
Run the shellscript in a screen (if you prefer), sit back and let it do
its work.
It seems that in the main calling script, if you change this line,
rsync -av rsync://10.0.0.2/remotebackup/pc/$i/ .
to this:
rsync -av --delete rsync://10.0.0.2/remotebackup/pc/$i/ .
then the scripts can be run periodically as cron jobs, and should run
much faster after the first run. Or am I missing something?
That brings up another question for anyone here -- does cp -al work
(within the filesystem) on the pool, or on the cpool, or is it also
prohibitively time-consuming? If it works (and you don't run out of
inodes) then it seems you could use it to take an snapshot for the
above scripts to work from, to minimize backuppc server downtime.
-------------------------------------------------------
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
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
