Le mardi 20 Décembre 2005 22:02, David Rees a écrit : > cpool uses hardlinks. rsync by default does not preserve hardlinks > which is why the copy you make explodes in size. If you specify -H to > rsync, it will preserve hard-links, but expect it to take a LONG time.
just to give an idea of performance moving the backuppc data directory i have recently moved all directories backuppc backuppc/conf backuppc/pc backuppc/pool backuppc/cpool backuppc/log backuppc/trash all those directories were containing 5 800 000 files for about 120 Go on reiserfs lvm2 file system on iscsi disk the destination was to ext3 lvm2 file system on iscsi's disks (the iscsi layout was soft initiator and the lan between the backup server and the NAS is Gb) i have used "rsync -arH source dest" commande line to do the job and the jobs take about -> 23 hours on P4 3.5 Ghz -> same place on disk system after (about 120 Go) -> no problem detected on hardlinks all run perfectly on the new directory --> about 2.7Go of memory during the jobs <-- ( 1Go of real memory and 4Go of swap on local hard disk) hope this can help somebody. a+ mna. -- Ce qui ne fut pas sera, et nul n'en est à l'abri. Jacques Bergier ------------------------------------------------------- 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_idv37&alloc_id865&op=click _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
