Hello,
I'd like to have an explanation about what Bacula is doing here:
04-Sep 21:49 iserver-dir: Start Backup JobId 591, Job=Backup_Office.2006-09-04_20.10.00
04-Sep 21:50 iserver-sd: Volume "LUNEDI" previously written, moving to end of data.
04-Sep 21:51 iserver-sd: Ready to append to end of Volume "LUNEDI" at file=12.
04-Sep 21:51 iserver-sd: Spooling data ...
04-Sep 21:57 iserver-sd: User specified spool size reached.
04-Sep 21:57 iserver-sd: Writing spooled data to Volume. Despooling 536,904,176 bytes ...
04-Sep 21:57 iserver-sd: Spooling data again ...
.....
05-Sep 04:11 iserver-sd: Writing spooled data to Volume. Despooling 536,904,194 bytes ...
05-Sep 04:12 iserver-sd: Spooling data again ...
05-Sep 04:19 iserver-sd: User specified spool size reached.
05-Sep 04:19 iserver-sd: Writing spooled data to Volume. Despooling 536,904,197 bytes ...
05-Sep 04:20 iserver-sd: Spooling data again ...
05-Sep 04:25 iserver-sd: Committing spooled data to Volume. Despooling 403,373,976 bytes ...
05-Sep 04:26 iserver-sd: Sending spooled attrs to the Director. Despooling 88,360,603 bytes ...
05-Sep 07:02 iserver-dir: Bacula 1.36.2 (28Feb05): 05-Sep-2006 07:02:35
...
FD Bytes Written: 28,773,270,290
SD Bytes Written: 28,820,945,157
Rate: 867.7 KB/s
As you can see, the last phase of Spooling is at 4:26, but it takes 2h:30m to finish.
What is Bacula doing when "Commintting" and when "Sending spooled attrs"?
The previous flush steps ("Writing spooled data...") were very fast, 512Mb written at high speed.
Then this last long step cause a final Rate very low.
I'd like to have an explanation about what Bacula is doing here:
04-Sep 21:49 iserver-dir: Start Backup JobId 591, Job=Backup_Office.2006-09-04_20.10.00
04-Sep 21:50 iserver-sd: Volume "LUNEDI" previously written, moving to end of data.
04-Sep 21:51 iserver-sd: Ready to append to end of Volume "LUNEDI" at file=12.
04-Sep 21:51 iserver-sd: Spooling data ...
04-Sep 21:57 iserver-sd: User specified spool size reached.
04-Sep 21:57 iserver-sd: Writing spooled data to Volume. Despooling 536,904,176 bytes ...
04-Sep 21:57 iserver-sd: Spooling data again ...
.....
05-Sep 04:11 iserver-sd: Writing spooled data to Volume. Despooling 536,904,194 bytes ...
05-Sep 04:12 iserver-sd: Spooling data again ...
05-Sep 04:19 iserver-sd: User specified spool size reached.
05-Sep 04:19 iserver-sd: Writing spooled data to Volume. Despooling 536,904,197 bytes ...
05-Sep 04:20 iserver-sd: Spooling data again ...
05-Sep 04:25 iserver-sd: Committing spooled data to Volume. Despooling 403,373,976 bytes ...
05-Sep 04:26 iserver-sd: Sending spooled attrs to the Director. Despooling 88,360,603 bytes ...
05-Sep 07:02 iserver-dir: Bacula 1.36.2 (28Feb05): 05-Sep-2006 07:02:35
...
FD Bytes Written: 28,773,270,290
SD Bytes Written: 28,820,945,157
Rate: 867.7 KB/s
As you can see, the last phase of Spooling is at 4:26, but it takes 2h:30m to finish.
What is Bacula doing when "Commintting" and when "Sending spooled attrs"?
The previous flush steps ("Writing spooled data...") were very fast, 512Mb written at high speed.
Then this last long step cause a final Rate very low.
|
|
|
Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
