<lst_hoe02 <at> kwsoft.de> writes:

> 
> Hello,
> 
> we have a Bareos Install 14.2.2-46 on Linux which is running fine  
> doing disk based backup and virtual full to tape. Now we like to  
> replace the virtual full by a copy job which transfer the disk based  
> full backup to tape. We have therefore tried this copy job:
> 
> JobDefs {
>    Name = "COPY-Def"
>    Type = Copy
>    Enabled = yes
>    Messages = Standard
>    Pool = SHORT
>    Priority = 20
>    Write Bootstrap = "/var/lib/bareos/%c.bsr"
> }
> 
> # TEST Copy Job
> Job {
>    Name = "COPY2TAPE-FS02"
> #  Enabled = no
>    JobDefs = "COPY-Def"
>    Client = fs02-fd
>    FileSet = "FS02Full"
>    Schedule = "COPYCycle"
>    Selection Type = SQLQuery
>    Selection Pattern = "SELECT jobid FROM job WHERE clientid='19' AND  
> type='B' AND level='F' AND poolid='5' AND (jobstatus='T' OR  
> jobstatus='W') AND (endtime > (now() - INTERVAL '7 days'))"
> }
> 

Officially the query should return two items I myself use the following
(which is a variation on the build in CopyUnCopiedJobs)

SELECT DISTINCT j1.JobId, j1.StartTime
  FROM Job j1
  JOIN Pool p1
    ON (j1.PoolId = p1.PoolId)
 WHERE p1.Name    = 'FullBackupsVirtualPool'
   AND j1.Type    = 'B'
   AND j1.jobBytes > 0
   AND j1.JobStatus IN ('T', 'W')
   AND j1.JobId NOT IN (
                SELECT PriorJobId
                  FROM Job j2
                  JOIN Pool p2
                    ON (j2.PoolId = p2.PoolId)
                 WHERE p2.Name    = 'FullBackupsTapePool'
                   AND j2.JobStatus IN ('T','W')
       )
   AND j1.EndTime > (now() - INTERVAL '10 DAY')
 ORDER BY j1.StartTime ASC;

Things might work ok with only a set of JobIds as the StartTime is
not used but only there for sorting purposes.

> 
> and after this the SD on the same machine is gone away. Any idea what  
> we have done wrong or do we need a debugger to solve this?
If things crashed it should have created a traceback file (if you have
gdb installed on the SD) and that gives a stack trace of what went wrong
when it crashed. I would take a look in your runtime directory of the
SD and look for files named *.traceback

When you have one you can create a bug report on bugs.bareos.org and
attach the traceback. That would a least give an idea as to where it
crashes and maybe also a hint as to its fix.

-- 
Marco van Wieringen                   [email protected]
Bareos GmbH & Co. KG                  Phone: +49-221-63069389
http://www.bareos.com                     

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
                 P. Storz, M. v. Wieringen 


-- 
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.

Reply via email to