Bacula-users

Re: [Bacula-users] How do I know if a job is actually part of a Copy procedure?

2011-04-11 13:00:36
Subject: Re: [Bacula-users] How do I know if a job is actually part of a Copy procedure?
From: Gergely Polonkai <polesz AT w00d5t0ck DOT info>
To: bacula-users <bacula-users AT lists.sourceforge DOT net>
Date: Mon, 11 Apr 2011 18:57:17 +0200
I know it is normal, and it's fine with me. I just want to know (if possible) 
if a given Backup job is started due to a Copy job or not.

On 2011.04.11., at 12:35, <ewan.brown AT stfc.ac DOT uk> wrote:

> I believe that's normal behaviour for copy jobs.
> 
> Cheers,
> 
> Ewan
> 
>> -----Original Message-----
>> From: Gergely Polonkai [mailto:polesz AT w00d5t0ck DOT info]
>> Sent: 08 April 2011 17:04
>> To: bacula-users AT lists.sourceforge DOT net
>> Subject: [Bacula-users] How do I know if a job is actually part of a
>> Copy procedure?
>> 
>> Hello List,
>> 
>> When I start a Copy type job, two jobs are actually started. E.g when I
>> want to copy a job originally called 'client1-full' within a Copy job
>> called 'client1-copy', the database holds two running job records, one
>> of them called 'client1-copy', with the Type field set to 'C' (Copy),
>> and the other called 'client1-full', level F, Type B (Backup). Is there
>> a way to find out if this second one is started because of the Copy
>> job, or it is meant to be run e.g because of a schedule or a console
>> action?
>> 
>> Thanks in advance!
>> 
>> Best regards,
>> Gergely Polonkai
>> --
>> "You need to believe in things that aren't true. How else can they
>> become?" - Terry Pratchett
> 

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>