Hi Martin & Radoslaw,
This is an old issue raised by me in Jan 2020; which both of you had responded
to earlier.
I am seeing it again as the particular scenario causing the issue did not
appear till now since my last reporting.
I am using bacula v 9.4.4 on Centos 6.4. for disk file based backup.
The backup scheme is weekdays incremental and virtual full back-up on Saturday.
Things were running fine till the interval between the last virtual full back
up job and the current incremental job was less than Max Virtual Full Interval
= 7 days
When this interval exceeded Max Virtual Full Interval = 7 days ; for an
incremental backup, bacula tried to create a new virtual full back-up by
consolidating the latest virtual full backup and all subsequent incremental
backups (...fair enough this is as expected) But while consolidating the jobs ;
it gave error :
Job Log
bacula-server-dir
No prior or suitable Full backup found in catalog. Doing Virtual FULL backup.
bacula-server-dir shell command: run BeforeJob
"/opt/bacula/srpg/scripts/validate_testbed.sh blhwsync11"
bacula-server-dir Consolidating JobIds=49733,49985,50189,50390,50575,50769,50964
Start Virtual Backup JobId 51162, Job=blhwsync11.2020-08-15_15.40.22_18
BeforeJob: blhwsync11 is available in regress.params and reachable
bacula-server-dir shell command: run AfterJob
"/opt/bacula/srpg/scripts/send_fail_mail.sh 51162
blhwsync11.2020-08-15_15.40.22_18 sas-backup-ad...@list.nokia.com"
bacula-server-sd Elapsed time=443746:10:30, Transfer rate=0 Bytes/second
bacula-server-dir
Error: Bacula bacula-server-dir 9.4.4 (28May19):
Build OS: x86_64-redhat-linux-gnu-bacula redhat
JobId: 51162
Job: blhwsync11.2020-08-15_15.40.22_18
Backup Level: Virtual Full
Client: "blhwsync11-fd" 9.4.4 (28May19)
x86_64-redhat-linux-gnu-bacula,redhat,
FileSet: "blhwsync11" 2020-07-29 13:30:02
Pool: "TestbedFull-F" (From Job VFullPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "StorageF" (From Pool resource)
Scheduled time: 15-Aug-2020 15:40:22
Start time: 13-Aug-2020 22:01:41
End time: 13-Aug-2020 22:11:43
Elapsed time: 10 mins 2 secs
Priority: 10
SD Files Written: 0
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Volume name(s):
Volume Session Id: 28
Volume Session Time: 1597408469
Last Volume Bytes: 1 (1 B)
SD Errors: 1
SD termination status: Error
Termination: *** Backup Error ***
bacula-server-sd Fatal error: Read and write devices not properly initialized.
bacula-server-dir Using Device "DeviceF1" to write.
Found 40845 files to consolidate into Virtual Full.
Later I tried running the virtual full backup "explicitly" to consolidate the
last virtual full and subsequent incremental jobs. This went through fine
without any errors.
That means there are enough devices available for read and write for the
virtual full job.
Job Config
Job {
Name = "blhwsync11"
Max Virtual Full Interval = 7 days
Accurate = no # With Accurate = yes, even file deletions, move etc
are covered in differential/incremental backup
DeleteConsolidatedJobs = yes
JobDefs = "blhwsync11"
RunBeforeJob = "/opt/bacula/srpg/scripts/validate_testbed.sh blhwsync11"
}
Job Definition Config
JobDefs {
Name = "blhwsync11"
Type = Backup
Level = Incremental
Client = blhwsync11-fd
FileSet = "blhwsync11"
Schedule = TestbedCycle1
Messages = Standard
Pool = Default
Next Pool = TestbedFull-F
Full Backup Pool = TestbedFull-F
VirtualFull Backup Pool = TestbedFull-F
Differential Backup Pool = TestbedIncr-F
Incremental Backup Pool = TestbedIncr-F
SpoolAttributes = yes
SpoolData = no
Priority = 10
Write Bootstrap = "/opt/bacula/working/%c.bsr"
}
Pool Config
Pool {
Name = TestbedFull-C # This is a pool for weekly full back of
user's data
# each testbed to have one single pool for full backup of max size 10 GB,
retained for 10 days
Pool Type = Backup
Next Pool = TestbedFull-C
Storage = StorageC # this storage maps to disk through virtual
autochanger
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = no # Prune expired volumes
Volume Retention = 90 days #
Maximum Volume Bytes = 10G # Max full backup size per Testbed = 10G
Maximum Volumes = 1000
Label Format = "TestbedFull-C-" # Auto label
Maximum Volume Jobs = 1 # one volume per user's job
Action On Purge = Truncate
}
Pool {
Name = TestbedIncr-C # This is a pool for incre or
differential back of user's data
# each testbed to have one single volume for incr or diff backup of max size
1GB, retained for 14 days
Pool Type = Backup
Next Pool = TestbedIncr-C
Storage = StorageC
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = no # Prune expired volumes
Volume Retention = 90 days #
Maximum Volume Bytes = 1G # Max full backup size per Testbed = 10G
Maximum Volumes = 1000
Label Format = "TestbedIncr-C-" # Auto label
Maximum Volume Jobs = 1 # one volume per testbed backup
Action On Purge = Truncate
}
Thanks
-Yateen
-----Original Message-----
From: Martin Simmons <mar...@lispworks.com>
Sent: Monday, January 20, 2020 8:02 PM
To: Shaligram Bhagat, Yateen (Nokia - IN/Bangalore)
<yateen.shaligram_bha...@nokia.com>
Cc: Bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Issue with config setting "Max Virtual Full
Interval"
Can you post the JobDefs named "blhwsync11" and also the Pool resource
definitions?
__Martin
> On Mon, 20 Jan 2020 11:57:45 +0000, "Shaligram Bhagat, Yateen (Nokia said:
>
> Thanks Martin,
>
> Yes, other backups were running at the time of this jobid 5738, I
> have 100 devices to handle ~200 concurrent backup jobs. Looks like there was
> shortage of free device for reading the previous full backup, although a
> device was reserved for writing.
>
> Regards
> Yateen
>
>
> -----Original Message-----
> From: Martin Simmons <mar...@lispworks.com>
> Sent: Friday, January 17, 2020 8:06 PM
> To: Shaligram Bhagat, Yateen (Nokia - IN/Bangalore)
> <yateen.shaligram_bha...@nokia.com>
> Cc: Bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Issue with config setting "Max Virtual Full
> Interval"
>
> Did you have any other backups running at the same time as jobid 5738? It
> looks like it didn't find a device to read the previous backups.
>
> __Martin
>
>
>>> On Fri, 10 Jan 2020 09:22:04 +0000, "Shaligram Bhagat, Yateen (Nokia said:
> >
> > Hi all,
> >
> > I am using bacula v 9.4.4 on Centos 6.4. for disk file based backup.
> >
> > The backup scheme is weekdays incremental and virtual full back-up on
> > Sunday.
> >
> > Job {
> > Name = "blhwsync11"
> > Max Virtual Full Interval = 7 days
> > Accurate = no # With Accurate = yes, even file deletions, move etc
> > are covered in differential/incremental backup
> > ##Backups To Keep = 3 # default = 0, means all incremental backups till
> > the VirtualFull are consolidated
> > DeleteConsolidatedJobs = yes
> > JobDefs = "blhwsync11"
> > RunBeforeJob = "/opt/bacula/srpg/scripts/validate_testbed.sh blhwsync11"
> > }
> >
> > Things were running fine till the interval between the last virtual
> > full back up job and the current incremental job was less than Max
> > Virtual Full Interval = 7 days
> >
> > When this interval exceeded Max Virtual Full Interval = 7 days ;
> > for an incremental backup, bacula tried to create a new virtual full backup
> > by consolidating the latest virtual full backup and all subsequent
> > incremental backups (...fair enough this is as expected) But while
> > consolidating the jobs ; it gave error :
> >
> > 10-Jan 13:53 bacula-server-dir JobId 5737: shell command: run AfterJob
> > "/opt/bacula/srpg/scripts/send_fail_mail.sh 5737
> > blhwsync11.2020-01-10_13.53.18_22 sas-backup-ad...@list.nokia.com"
> > 10-Jan 13:54 bacula-server-dir JobId 5738: 10-Jan 13:54 bacula-server-dir
> > JobId 5738: No prior or suitable Full backup found in catalog. Doing
> > Virtual FULL backup.
> > 10-Jan 13:54 bacula-server-dir JobId 5738: shell command: run BeforeJob
> > "/opt/bacula/srpg/scripts/validate_testbed.sh blhwsync11"
> > 10-Jan 13:54 bacula-server-dir JobId 5738: Start Virtual Backup
> > JobId 5738, Job=blhwsync11.2020-01-10_13.54.16_04
> > 10-Jan 13:54 bacula-server-dir JobId 5738: Warning: This Job is not an
> > Accurate backup so is not equivalent to a Full backup.
> > 10-Jan 13:54 bacula-server-dir JobId 5738: Consolidating
> > JobIds=4739,5004,5216,5389 10-Jan 13:54 bacula-server-dir JobId 5738: Found
> > 43700 files to consolidate into Virtual Full.
> > 10-Jan 13:54 bacula-server-dir JobId 5738: Using Device "DeviceF1" to write.
> > 10-Jan 13:54 bacula-server-sd JobId 5738: Fatal error: Read and write
> > devices not properly initialized.
> > 10-Jan 13:54 bacula-server-sd JobId 5738: Elapsed time=438512:24:21,
> > Transfer rate=0 Bytes/second 10-Jan 13:54 bacula-server-dir JobId 5738:
> > Error: Bacula bacula-server-dir 9.4.4 (28May19):
> > Build OS: x86_64-redhat-linux-gnu-bacula redhat
> > JobId: 5738
> > Job: blhwsync11.2020-01-10_13.54.16_04
> > Backup Level: Virtual Full
> > Client: "blhwsync11-fd" 9.4.4 (28May19)
> > x86_64-redhat-linux-gnu-bacula,redhat,
> > FileSet: "blhwsync11" 2019-12-10 22:00:01
> > Pool: "TestbedFull-F" (From Job VFullPool override)
> > Catalog: "MyCatalog" (From Client resource)
> > Storage: "StorageF" (From Pool resource)
> > Scheduled time: 10-Jan-2020 13:54:14
> > Start time: 08-Jan-2020 22:00:02
> > End time: 08-Jan-2020 22:00:14
> > Elapsed time: 12 secs
> > Priority: 10
> > SD Files Written: 0
> > SD Bytes Written: 0 (0 B)
> > Rate: 0.0 KB/s
> > Volume name(s):
> > Volume Session Id: 1
> > Volume Session Time: 1578644639
> > Last Volume Bytes: 1 (1 B)
> > SD Errors: 1
> > SD termination status: Error
> > Termination: *** Backup Error ***
> >
> > Later I tried running the virtual full backup "explicitly" to consolidate
> > the last virtual full and subsequent incremental jobs. This went through
> > fine without any errors.
> >
> > So the issue seems to be in the Bacula's handling of the configuration
> > setting : "Max Virtual Full Interval " ?
> > Any advice ?
> >
> > Thanks,
> > Yateen
> >
> >
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
