Re: [Bacula-users] v7.0.4 migrate: StartTime older than SchedTime

2014-07-24 Thread Hans Schou
On 07/23/2014 04:30 PM, Thomas Lohman wrote: >> "StartTime" does not get updated when migrating a job. Is this a bug or >> is it the way it is supposed to be? >> > the start time of the new job gets set to the start time > of the copied/migrated job or in the case of a Virtual Full to the start > t

Re: [Bacula-users] v7.0.4 migrate: StartTime older than SchedTime

2014-07-23 Thread Kern Sibbald
Hello Tom, If I remember right, I am waiting for an FLA to be able to integrate your patches. Any status on that? Best regards, Kern On 07/23/2014 04:30 PM, Thomas Lohman wrote: >> "StartTime" does not get updated when migrating a job. Is this a bug or >> is it the way it is supposed to be? >>

Re: [Bacula-users] v7.0.4 migrate: StartTime older than SchedTime

2014-07-23 Thread Thomas Lohman
> "StartTime" does not get updated when migrating a job. Is this a bug or > is it the way it is supposed to be? > I believe that this is the way it is supposed to work. When copying/migrating a job or when creating a virtual Full job from previous jobs, the start time of the new job gets set to

[Bacula-users] v7.0.4 migrate: StartTime older than SchedTime

2014-07-23 Thread Hans Schou
Hi "StartTime" does not get updated when migrating a job. Is this a bug or is it the way it is supposed to be? mysql bacula -e "SELECT JobId, PriorJobId, SchedTime, StartTime, EndTime, RealEndTime FROM Job WHERE JobId IN (90018,89565)" +---++-+---