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 > time of the last backup used to create the Virtual Full. This, I > believe, is because that start time is used when looking to see what > needs to be backed up if you're doing another backup that will be based > off of that job. Thanks. That make sence. "StartTime" is actually something like the "ArchiveDate" or so.
> This can cause issues if you're assuming start time is > the real start time of a job as you've discovered. I went ahead and > added a realstarttime attribute to a job as part of some of my > patches/extensions but those were for 5.2.13 and not the latest release > 7.0.x. OK, I'll get the elapsed time from status report until then. /hans ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
