On Wed, 24 May 2006, Kern Sibbald wrote:
The problem isn't the 360G of data, it could be 10000000G and the problem would be the same. It is the 5 million files. The current code is not very scalable beyond a million or two files when doing an interactive restore. It simply takes too long to build the in-memory tree.
On backups here with ~4 million files in them, the tree build takes less than an hour. I usually just start the restore process and go do something else for a while.
There have been a good number of reports on this list. Most boil down to having the correct indexes defined and the correct tuning of MySQL (or for users other than Peter PostgreSQL).
Tuning the indexes _definitely_ helps AB ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
