> Hi, > > I'm using bacula 1.37.30 for a few days now and I > decided to test a full server recovery. > I discovered that the building the directory tree > takes a very long time (almost an hour) for 429,836 > files. > I started the building of the tree at 11:20 and at > 12:15 I got a prompt. > > The machine is a dedicated bacula machine and was > doing nothing else than building the tree, it'a a > Penium III at 800Mhz with 512MB memory. > > My question is if this is normal for builing the > tree? Because if one of the server dies we want to > recover > as soon as possible. > > Thanks, > > Reinier > > output bconsole: > ---- > +-------+-------+----------+----------------+---------------------+------------+-----------+ > | JobId | Level | JobFiles | JobBytes | > StartTime | VolumeName | StartFile | > +-------+-------+----------+----------------+---------------------+------------+-----------+ > | 1,553 | F | 426,357 | 13,464,836,018 | > 2005-07-30 15:40:00 | 000017L1 | 100 | > | 1,561 | I | 41 | 41,277,841 | > 2005-07-31 01:32:52 | 000034L1 | 106 | > | 1,576 | I | 137 | 101,733,681 | > 2005-08-01 01:31:02 | 000034L1 | 116 | > | 1,598 | I | 2,315 | 101,235,058 | > 2005-08-03 02:09:03 | 000034L1 | 146 | > | 1,607 | I | 1,641 | 220,426,382 | > 2005-08-04 02:03:39 | 000034L1 | 191 | > | 1,617 | I | 1,345 | 100,591,549 | > 2005-08-05 01:51:58 | 000035L1 | 28 | > +-------+-------+----------+----------------+---------------------+------------+-----------+ > You have selected the following JobIds: > 1553,1561,1576,1598,1607,1617 > > Building directory tree for JobId 1553 ... > +++++++++++++++++++++++++++++++++++++++++++++++++ > Building directory tree for JobId 1561 ... > Building directory tree for JobId 1576 ... > Building directory tree for JobId 1598 ... + > Building directory tree for JobId 1607 ... > Building directory tree for JobId 1617 ... > 6 Jobs, 429,836 files inserted into the tree. > ---- > > > Output top (during building tree): > ---- > 32 processes: 2 running, 30 sleeping > CPU states: 98.1% user, 0.0% nice, 0.4% system, > 1.6% interrupt, 0.0% idle > Mem: 131M Active, 36M Inact, 89M Wired, 60M Buf, > 242M Free > Swap: 1020M Total, 120K Used, 1020M Free > > PID USERNAME PRI NICE SIZE RES STATE TIME > WCPU CPU COMMAND > 91877 root 64 0 88948K 87612K RUN 269:36 > 98.39% 98.39% bacula-dir > 93618 root 29 0 1908K 1072K RUN 0:00 > 2.96% 0.54% top > ---- > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software > Conference & EXPO > September 19-22, 2005 * San Francisco, CA * > Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects > & Teams * Testing & QA > Security * Process Improvement & Measurement * > http://www.sqe.com/bsce5sf > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > You are restoring 14GB of data right? For most tape drives this is not a long time. For me a 40GB DLT-IV (native) tape takes 3 to 4 hours to restore. The drive has a 3MB/s data rate which is about 11GB / hour (native). And that is as fast as it will go. If you manage ot get a fileset that is highly compressible you can get better times. But most of my data I get no where near a compression rate of 2.0.
John ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
