On Monday, January 9, 2017 at 10:53:44 AM UTC+1, Claas Goltz wrote: > Am Mittwoch, 4. Januar 2017 18:48:38 UTC+1 schrieb Robert N: > > Hi, > > > > according to the docu, > > http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-27200021 > > bareos does spooling during despooling, "While despooling, all jobs > > spooling continue running. " but what I see in the log, suggest that it > > doesn't: > > > > 03-Jan 18:46 muc1pro-backup-1-sd JobId 10416: Spooling data ... > > 03-Jan 18:46 muc1pro-backup-1-sd JobId 10416: Forward spacing Volume > > "Full-4188" to file:block 2:1136152325. > > 03-Jan 18:46 muc1pro-backup-1-sd JobId 10416: End of Volume at file 2 on > > device "DiskDeviceFull1" (/data/bareos-storage/Full), Volume "Full-4188" > > 03-Jan 18:46 muc1pro-backup-1-sd JobId 10416: Ready to read from volume > > "Full-4189" on device "DiskDeviceFull1" (/data/bareos-storage/Full). > > 03-Jan 18:46 muc1pro-backup-1-sd JobId 10416: Forward spacing Volume > > "Full-4189" to file:block 0:129245. > > 03-Jan 18:47 muc1pro-backup-1-sd JobId 10416: End of Volume at file 2 on > > device "DiskDeviceFull1" (/data/bareos-storage/Full), Volume "Full-4189" > > 03-Jan 18:47 muc1pro-backup-1-sd JobId 10416: Ready to read from volume > > "Full-4190" on device "DiskDeviceFull1" (/data/bareos-storage/Full). > > 03-Jan 18:47 muc1pro-backup-1-sd JobId 10416: Forward spacing Volume > > "Full-4190" to file:block 0:64733. > > 03-Jan 18:47 muc1pro-backup-1-sd JobId 10416: User specified Device spool > > size reached: DevSpoolSize=60,000,205,166 MaxDevSpoolSize=60,000,000,000 > > 03-Jan 18:47 muc1pro-backup-1-sd JobId 10416: Writing spooled data to > > Volume. Despooling 5,940,251,004 bytes ... > > 03-Jan 18:48 muc1pro-backup-1-sd JobId 10416: Despooling elapsed time = > > 00:00:42, Transfer rate = 141.4 M Bytes/second > > 03-Jan 18:48 muc1pro-backup-1-sd JobId 10416: Spooling data again ... > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: End of Volume at file 2 on > > device "DiskDeviceFull1" (/data/bareos-storage/Full), Volume "Full-4190" > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: Ready to read from volume > > "Full-4191" on device "DiskDeviceFull1" (/data/bareos-storage/Full). > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: Forward spacing Volume > > "Full-4191" to file:block 0:221. > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: End of Volume at file 2 on > > device "DiskDeviceFull1" (/data/bareos-storage/Full), Volume "Full-4191" > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: Ready to read from volume > > "Full-4192" on device "DiskDeviceFull1" (/data/bareos-storage/Full). > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: Forward spacing Volume > > "Full-4192" to file:block 0:129245. > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: User specified Device spool > > size reached: DevSpoolSize=60,000,205,110 MaxDevSpoolSize=60,000,000,000 > > 03-Jan 18:49 muc1pro-backup-1-sd JobId 10416: Writing spooled data to > > Volume. Despooling 5,940,250,948 bytes ... > > 03-Jan 18:50 muc1pro-backup-1-sd JobId 10416: Despooling elapsed time = > > 00:00:31, Transfer rate = 191.6 M Bytes/second > > > > > > and so on ... > > > > so what I understand is: > > 1. spool data > > 2. despool data > > 3. after despooling done, spool again. > > > > what does than "While despooling, all jobs spooling continue running" mean? > > > > thanks, > > Robert > > I have the same "problem". I've got about 20 Jobs that needed to be written > on tape. They are all queued by one copy job resp. one selection pattern. > But baroes is only spooling and despoonling one job at time. It could nearly > save half the time, if bareos is spooling job b) while job a) is despooling. > > Is there a job definition missing or something else? > > Job { > Name = "copy-full-to-tape" > JobDefs = "DefaultJob" > Type = Copy > Pool = Full > Level = Full > Schedule = "copy-to-tape" > Selection Type = SQLQuery > Selection Pattern = "select * from Job where Level = 'F' AND > Jobstatus in('W','T') AND(endtime between (NOW() - INTERVAL '6' DAY) AND > NOW()) AND clientid > in(2,12,14,16,20,21,22,23,24,29,31,35,36,37,39,40,42,45,47,48,50,51,64);" > Spool Data = yes > Priority = 15 > } > > thanks.
unfortunately, I can confirm the same. I think the problem is, due to the fact that bareos is NOT able to use more than one volume/storage. so when you do a copy, it's taking job by job, and because only one volume can be opened at a time from the source pool, it's taking the jobs one by one. This scenario could work for the Backup jobs, because there the sources are the fd's ( instead of bareos pools ) which bareos can handle multiple at a time. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
