Hi!
I had the unfortunate event that our RAID housing approx. 1.4TB data was
trashed, so I chose to delete everything and take the last recent backup.
When restoring, I noticed, that Bacula seems to have difficulties to handle a
large amount of files when starting a restore. Everything is quite fine until
I type "done" after marking all files. I split the whole RAID into five sets,
and while for about 450,000 files it takes "done" about 15 minutes to return,
for 2,700,000 files it is about 20 hours spinning one of the 1GHz CPUs at
100% !
Does anybody have some experience with restoring large filesets? Is it just a
problem of our machine or not? Is it a bug?
With 1.36 that problem never occurred me (maybe because I never restored
_that_ many files). I tried 1.38.0 and 1.38.2 with no difference.
Thanks for any help,
Andreas
PS.: I already sent this message, but using a wrong identity, so I got caught
by the "Subscribers only policy" of the list. So excuse me, if it arrives two
times.
-------------------------------------------------------
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
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
