Hello,
we had a problem with Tape Backup starting after midnight where the source backup was finished before midnight: message "No backup files found" - Case ID 08215350
Support was telling us that's it's normal because tape backup starts at a day where no source backup was done.
We could change the source backup job time slot to the same day as tape job (even if backup window doesn't really fit and even if we don't agree with the behaviour decribed above).
But really anoying was the fact that the tap jobs where no backup files could be found ended with success (green) and not with an error.
Thats why we ask for a feature request to put these jobs on warning or error because no data was copied.
Kr
Dieter
-
DHuppertz
- Enthusiast
- Posts: 43
- Liked: 9 times
- Joined: Nov 08, 2019 10:05 am
- Full Name: Dieter Huppertz
- Contact:
-
david.domask
- Product Manager
- Posts: 4013
- Liked: 976 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: No backup files found - Feature request
Hi Dieter,
Support is mostly correct here, but let me expand a bit: checking the case notes, if I get it right you configured the job to create a Virtual Synthetic Full on tape every day, correct?
The issue here is the Virtual Full Interval; the way it works is that the new interval starts from 00:00 on the day after the last virtual full was written to tape; in the most recent run on the 27th and 28th, the 27th created a Virtual Full on tape as expected, so the new Virtual Synthetic Full Interval was looking for backups created on 28th to create a new Virtual Synthetic Full from, so Support is correct that a schedule adjustment could help here (it looks like normally the source backup completes quite quickly, so moving the tape job to start after the source job will help here, and this may be a legitimate case to use job-chaining (start the tape job after the source job completes))
Understood on the request and noted, but for now please try adjusting the schedule like Support advised, it will help avoid this situation.
Support is mostly correct here, but let me expand a bit: checking the case notes, if I get it right you configured the job to create a Virtual Synthetic Full on tape every day, correct?
The issue here is the Virtual Full Interval; the way it works is that the new interval starts from 00:00 on the day after the last virtual full was written to tape; in the most recent run on the 27th and 28th, the 27th created a Virtual Full on tape as expected, so the new Virtual Synthetic Full Interval was looking for backups created on 28th to create a new Virtual Synthetic Full from, so Support is correct that a schedule adjustment could help here (it looks like normally the source backup completes quite quickly, so moving the tape job to start after the source job will help here, and this may be a legitimate case to use job-chaining (start the tape job after the source job completes))
Understood on the request and noted, but for now please try adjusting the schedule like Support advised, it will help avoid this situation.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 18 guests