Matija Nalis wrote: > It is probably not hung, but just very, very slow.
Yes. You probably need a LOT more ram and to tune mysql's parameters. > We've had a same > issue, with about 500 million records in File (and about 120GB on > disk for File.ibd) on (mostly dedicated to mysql) machine (8gig RAM, > 8x2.33 Xeon, different configurations with about 3-6GB for mysql > buffers) -- it could take several hours for 5.0.1 until it completed > and the system was ready for selecting few files to restore. :-( Even with 48Gb ram, a few restores on our system (~255 million File records: up to 4 million files on some full backups but nost are under 100k entries) could take an hour to get past the "building directory tree" stage. It's a _lot_ faster with postgresql and moderate tuning (My other gripes about the changeover notwithstanding, those are annoyances, not showstoppers) The lesson for us was that mysql doesn't scale to huge datasets well and we should have switched to postgres much earlier. AB ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
