[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-users
Subject:    Re: [Bacula-users] problems with copy job
From:       Martin Simmons <martin () lispworks ! com>
Date:       2018-01-04 18:11:38
Message-ID: 201801041811.w04IBcLP009767 () higson ! cam ! lispworks ! com
[Download RAW message or body]

Is the catalog database on the same machine, and if so, did the version of
MySQL change during the OS upgrade?  If it did, then did you need to do
anything to "upgrade" the catalog database?

According to the error message, Bacula thinks that the job being copied is on
dcBS-103.  The full job log of the copy should tell you which jobid this is
(the "Prev Backup JobId").

You could then use this to substitute for $PREV_BACKUP_JOBID in the SQL
command below to check the volume for this job according to the catalog:

SELECT DISTINCT Job.JobId,VolumeName 
 FROM Job,JobMedia,Media 
 WHERE Job.JobId=$PREV_BACKUP_JOBID
 AND Job.JobId=JobMedia.JobId 
 AND JobMedia.MediaId=Media.MediaId;

__Martin


>>>>> On Wed, 3 Jan 2018 14:28:47 -0800, Jerry Lowry said:
> 
> I spent a couple days over the last week upgrading a bacula server from
> centos 6.9 to 7.3 and bacula from 9.0.3 to 9.0.6.
> The backup jobs are working just fine, but the offsite job is failing with
> the following error:
> 
> 03-Jan 14:12 distress JobId 34620: Volume "dcBS-105" previously written,
> moving to end of data.
> 03-Jan 14:12 distress JobId 34619: Warning: acquire.c:235 Read open File
> device "Workstations" (/accounting/Workstations) Volume "dcBS-103" failed:
> ERR=file_dev.c:190 Could not
> open(/accounting/Workstations/dcBS-103,OPEN_READ_ONLY,0640): ERR=No such
> file or directory
> 
> first - the volume dcBS-105 is not full it is sitting at 79%.
> The Workstations device does not have a volume "dcBS-103" in it, never
> has.  It is an offsite backup volume that is 100% full.
> 
> Why is bacula trying to open this volume when it is not in the Workstations
> pool?
> 
> The job has been running with the following configuration for years.
> Job {
>         Name = "CopyWKDiskToDisk"
>         Type = Copy
>         Level = Full
>         FileSet = "Bottom Set"
>         Client = distress-fd
>         Messages = Standard
>         Storage = workstations
>         Pool = WorkstationPool
>         Maximum Concurrent Jobs = 4
>         Selection Type = PoolUncopiedJobs
>         Selection Pattern = "DC-*"
> }
> 
> Ran a mysqlcheck on the database and all is okay.
> 
> Any ideas as to why it is looking in the wrong pool?
> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[prev in list] [next in list] [prev in thread] [next in thread]