Re: [Bacula-users] Error with DR backups
DAve wrote: Martin Simmons wrote: On Mon, 16 Nov 2009 09:29:07 -0500, DAve said: 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20947 I am at a loss to understand why. The volumes can be pruned almost immediately as the backup is only for DR purposes and each volume will be recycled each night. The only problem I see is that the client is paying for 60GB and the backups have begun using more than that amount, so volumes are being reused within the current backup. That seems a very likely reason, especially if you have set Purge Oldest Volume = yes. When Bacula purges a volume, it removes whole jobs, not just the info for that volume. __Martin Added ten more volumes to the pool. Two days complete, no errors... DAve A week, no errors. Looks like that was the issue. Thank you to everyone who responded on/off list with ideas. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Adams http://appleseedinfo.org -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
Martin Simmons wrote: On Mon, 16 Nov 2009 09:29:07 -0500, DAve said: 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20947 I am at a loss to understand why. The volumes can be pruned almost immediately as the backup is only for DR purposes and each volume will be recycled each night. The only problem I see is that the client is paying for 60GB and the backups have begun using more than that amount, so volumes are being reused within the current backup. That seems a very likely reason, especially if you have set Purge Oldest Volume = yes. When Bacula purges a volume, it removes whole jobs, not just the info for that volume. __Martin Added ten more volumes to the pool. Two days complete, no errors... DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
On Mon, 16 Nov 2009 09:29:07 -0500, DAve said: 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20947 I am at a loss to understand why. The volumes can be pruned almost immediately as the backup is only for DR purposes and each volume will be recycled each night. The only problem I see is that the client is paying for 60GB and the backups have begun using more than that amount, so volumes are being reused within the current backup. That seems a very likely reason, especially if you have set Purge Oldest Volume = yes. When Bacula purges a volume, it removes whole jobs, not just the info for that volume. __Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
I have tried several things now to correct this error without success. - Checked and repaired MySQL db with MySQL tools (mysqlcheck). - Cleaned MySQL db with bacula tools (dbcheck). - The offending pool has been removed and a new pool created and volumes added. The backup ran without error over two weeks and then the error returned. - The temp directory has been changed to a directory with more than enough space to contain the entire backup set. - The backup job has been moved in the schedule to a period that was not concurrent with any other job. Still, the one job that has 200GB+ of files succeeds, and the job with only 60GB fails, same error. 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 16-Nov 08:25 director-dir: Allied-ex3.2009-11-16_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20947 I am at a loss to understand why. The volumes can be pruned almost immediately as the backup is only for DR purposes and each volume will be recycled each night. The only problem I see is that the client is paying for 60GB and the backups have begun using more than that amount, so volumes are being reused within the current backup. I will next try increasing the number of volumes to see if that helps. Still open to suggestions, more than happy to repost all files. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
DAve wrote: DAve wrote: Cedric Tefft wrote: DAve wrote: No change, same error. 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20604 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Error: Bacula 2.0.3 (06Mar07): Baffling. You might be running out of disk space on /tmp or /var or wherever the DB engine writes its temp tables. The important thing is that you will probably only see this condition WHILE bacula is actually trying to update the database. If you check it now, you will probably find you have plenty of space -- don't let that fool you. Interesting idea. When that client is running I have a another very large job that starts before, and ends after. I will check that out, though I have never seen this with MySQL. DAve My /tmp dir had but 300mb left. The client that is backing up, when the failing backup starts, has 192GB of data and tens of thousands of files. I changed the mysql tmp dir to another spindle which has 90gb left. It is also a different spindle than the logs and the database. We will see at 1am. DAve No change, same error. So I do not believe it to be a SQL error or an error with the bacula DB. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
DAve wrote: Ran dbcheck, found several paths to correct and also orphaned files. dbcheck results, second run, everything looks good. Select function number: 16 Checking for Filenames with a trailing slash Found 0 bad Filename records. Checking for Paths without a trailing slash Found 0 bad Path records. Checking for duplicate Filename entries. Found 0 duplicate Filename records. Checking for duplicate Path entries. Found 0 duplicate Path records. Checking for orphaned JobMedia entries. Checking for orphaned File entries. This may take some time! Checking for orphaned Path entries. This may take some time! Terminated Reran mysqlcheck as #mysqlcheck -q -r -uroot -p bacula Enter password: bacula.BaseFiles OK bacula.CDImagesOK bacula.Client OK bacula.CountersOK bacula.Device OK bacula.FileOK bacula.FileSet OK bacula.FilenameOK bacula.Job OK bacula.JobMediaOK bacula.LocationOK bacula.LocationLog OK bacula.Log OK bacula.Media OK bacula.MediaType OK bacula.PathOK bacula.PoolOK bacula.Status OK bacula.Storage OK bacula.UnsavedFilesOK bacula.Version OK I will see what happens tonight. DAve No change, same error. 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20604 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Error: Bacula 2.0.3 (06Mar07): Baffling. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
DAve wrote: No change, same error. 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20604 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Error: Bacula 2.0.3 (06Mar07): Baffling. You might be running out of disk space on /tmp or /var or wherever the DB engine writes its temp tables. The important thing is that you will probably only see this condition WHILE bacula is actually trying to update the database. If you check it now, you will probably find you have plenty of space -- don't let that fool you. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
Cedric Tefft wrote: DAve wrote: No change, same error. 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20604 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Error: Bacula 2.0.3 (06Mar07): Baffling. You might be running out of disk space on /tmp or /var or wherever the DB engine writes its temp tables. The important thing is that you will probably only see this condition WHILE bacula is actually trying to update the database. If you check it now, you will probably find you have plenty of space -- don't let that fool you. Interesting idea. When that client is running I have a another very large job that starts before, and ends after. I will check that out, though I have never seen this with MySQL. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
DAve wrote: Cedric Tefft wrote: DAve wrote: No change, same error. 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error updating job record. sql_update.c:194 Update problem: affected_rows=0 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Warning: Error getting job record for stats: sql_get.c:293 No Job found for JobId 20604 30-Oct 07:09 director-dir: Allied-ex3.2009-10-30_01.00.02 Error: Bacula 2.0.3 (06Mar07): Baffling. You might be running out of disk space on /tmp or /var or wherever the DB engine writes its temp tables. The important thing is that you will probably only see this condition WHILE bacula is actually trying to update the database. If you check it now, you will probably find you have plenty of space -- don't let that fool you. Interesting idea. When that client is running I have a another very large job that starts before, and ends after. I will check that out, though I have never seen this with MySQL. DAve My /tmp dir had but 300mb left. The client that is backing up, when the failing backup starts, has 192GB of data and tens of thousands of files. I changed the mysql tmp dir to another spindle which has 90gb left. It is also a different spindle than the logs and the database. We will see at 1am. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error with DR backups
DAve wrote:
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as before, and now I have
been running without error since the 7th.
I am at a loss to understand why. I need to go into SQL
Re: [Bacula-users] Error with DR backups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see
nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as before, and now I have
been running without error since
Re: [Bacula-users] Error with DR backups
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see
nothing
different.
I am putting the client's config below and the larger backup output
and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
getting job record for stats: sql_get.c:293 No Job found for JobId
20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error:
Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as before, and now I have
Re: [Bacula-users] Error with DR backups
DAve wrote:
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
Ryan Novosielski wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed
size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an
error.
There have been days when the error does not occur and I can see
nothing
different.
I am putting the client's config below and the larger backup output
and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning:
Error
getting job record for stats: sql_get.c:293 No Job found for JobId
20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error:
Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger
backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and
he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as
Re: [Bacula-users] Error with DR backups
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as before, and now I have
been running without error since the 7th.
I am at a loss to understand why. I need to go into SQL and see what is
different as doing list media pool=exch3-allied-Pool shows no
difference
Re: [Bacula-users] Error with DR backups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DAve wrote:
DAve wrote:
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
I find nothing different between the two configs that would explain why
one works and the other does not. So I created a new media pool called
exch3-allied-Pool, changed the name of the pool resource to the new name
in the director config, added volumes same as before, and now I have
been running without error since the 7th.
I am at a loss to understand why. I need to go into SQL and see what is
different as doing
Re: [Bacula-users] Error with DR backups
DAve wrote:
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
Changed the pool resource to not autoprune and the error was the same
last night.
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
AutoPrune = no
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
The larger client mentioned above, again, no problems. If I have Job
Retention = 1 week then why is my current job not found in the catalog?
From the manual,
Job Retention = time-period-specification The Job Retention directive
defines the length of time that Bacula will keep Job records in
the Catalog database after the Job End time. When this time period
expires, and if AutoPrune is set to yes Bacula will prune (remove)
Job records that are older than the specified File Retention period.
As with the other retention periods, this affects only records in the
catalog and not data in your archive backup.
And the error clearly states No Job found for JobId 20126, when the
job is still running.
the only mention I ever seem to find of this error is a recent post by
Joshua J. Kugler, with no solution other than his issue went away and he
will keep an eye on it until it returns.
DAve
--
Posterity, you will know how much it cost the present generation to
preserve your freedom. I hope you will make good use of it. If you
do not, I shall repent in heaven that ever I took half the pains to
preserve it. John Quincy Adams
http://appleseedinfo.org
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile
Re: [Bacula-users] Error with DR backups
DAve wrote:
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
Hmmm, I have a second client configured in the same manner. The only
difference is that the second client has 240 1gb volumes instead of 60
1gb volumes. The configs are identical and the larger client has no
issues. Both backup jobs start and finish within 10 minutes of each
other, yet the smaller backup has it's job purged and the larger backup
does not.
Still digging.
DAve
--
Posterity, you will know how much it cost the present generation to
preserve your freedom. I hope you will make good use of it. If you
do not, I shall repent in heaven that ever I took half the pains to
preserve it. John Quincy Adams
http://appleseedinfo.org
--
Come build with us! The BlackBerryreg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9#45;12, 2009. Register now#33;
http://p.sf.net/sfu/devconf
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Error with DR backups
Good afternoon.
I am having a recurring issue with a backup that is configured for DR
purposes. The client purchased a fixed amount of space and wants to
overwrite the volumes each night. They have a local backup system in
place and we are using Bacula to get those backups offsite for the
evening only. I setup Bacula to use a number of volumes of fixed size,
and the volumes are written over each night.
Everything worked fine for a period and then began producing an error.
There have been days when the error does not occur and I can see nothing
different.
I am putting the client's config below and the larger backup output and
media list online at these URLs.
Job Output
http://pixelhammer.com/Backup-allied-ex3-fd%20Full.txt
bconsole media list
http://pixelhammer.com/allied-media.txt
The error I am seeing,
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
updating job record. sql_update.c:194 Update problem: affected_rows=0
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Warning: Error
getting job record for stats: sql_get.c:293 No Job found for JobId 20126
05-Oct 08:38 director-dir: Allied-ex3.2009-10-05_01.00.02 Error: Bacula
2.0.3 (06Mar07): 05-Oct-2009 08:38:53
The client config,
Job {
Name = Allied-ex3
FileSet = Allied-ex3
Write Bootstrap = /data/backups/Allied-ex3.bsr
Type = Backup
Level = Full
Client = allied-ex3-fd
Schedule = Allied-ex3
Storage = storage2-allied-ex3
Messages = Allied
Pool = ex3-allied-Pool
Priority = 10
#Enabled = No
}
FileSet {
Name = Allied-ex3
Enable VSS = no
Include {
Options {
#compression = gzip
IgnoreCase = yes
}
File = D:/archivesink/
}
Exclude {
}
}
Schedule {
Name = Allied-ex3
Run = Level=Full FullPool=ex3-allied-Pool mon-sun at 01:00
}
Client {
Name = allied-ex3-fd
Address = xxx.xxx.105.12
FDPort = 49202
Catalog = DataVault
Password = xx
File Retention = 1 week
Job Retention = 1 week
AutoPrune = yes
}
Storage {
Name = storage2-allied-ex3
Address = xxx.tls.net
SDPort = 49022
Password = xx
Device = FileStorage-allied-ex3
Media Type = File
}
Pool {
Name = ex3-allied-Pool
Pool Type = Backup
LabelFormat = ex3-allied-
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
Volume Retention = 12 hours
Maximum Volumes = 60
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1G
}
I am reasonably certain the problem is PEBKAC and my understanding of
pruning and retention. I cannot see where I have gone wrong.
Thanks,
DAve
--
Posterity, you will know how much it cost the present generation to
preserve your freedom. I hope you will make good use of it. If you
do not, I shall repent in heaven that ever I took half the pains to
preserve it. John Quincy Adams
http://appleseedinfo.org
--
Come build with us! The BlackBerryreg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9#45;12, 2009. Register now#33;
http://p.sf.net/sfu/devconf
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
