Did the backup-to-disk job start on Sunday? Have you tried two other approaches?It worked two times flawlessly (Friday and Saturday) but did not work on Sunday. The Backup-to-Tape-Job which is depending on the Backup-to-Disk-Job didn't even start on Sunday.
Can anybody tell me, in which log file there should normally be a note when a depending job is started?
Yes, the to-disk-job started and finished successfully, the to-tape-job did not even start.Did the backup-to-disk job start on Sunday?
Not yet, because I prefer using dependency between two jobs. That is the easiest to configure and completely independent of any fixed times.Have you tried two other approaches?
Does the tape job start if any new backup file appears? The job consists of several backup files (some Endpoint Backups and one VMware Backup). I would like the to-tape-job start if the last (VMware Backup) job finished. I don't like that rough time frame, with dependencies it would not waste a minute but would directly start.You can select "As new backup file appear" option and specify backup window so the tape job will be restricted to start at the beginning of the time frame.
I think the file-to-tape-job is slower than the backups-to-tape-job. At least it was in V8 in our environment.Another option might be to create a backup to tape for full backups only and set a secondary file to tape job with the include mask configured to pick only the needed incrementals.
At which time did a source job start on Sunday? How both schedules look like?
- Backup to tape Monday 22.05.2016 00:06 *missing*
Where should that be defined? Under "schedule" "Run the Job automatically" is tagged, and "after this job" is selected. It is not possible to define a time frame in that case.And it doesn't have a backup window specified that prevents job execution at the given time frame?
Users browsing this forum: No registered users and 2 guests