-
- Enthusiast
- Posts: 35
- Liked: 9 times
- Joined: Jan 06, 2022 9:20 pm
- Contact:
Strange retention - less than configured
Backup job is configured to retain 28 DAYS on SOBR (local NAS + Object storage)
Backups run once a day with incremental M-Th + Active full on Friday.
SOBR is configured to COPY and MOVE after 14 days from NAS to Object storage.
Here is the kicker: Veeam console shows that only 10 restore points locally (NAS) and correct number of restore points in Object storage. I've only seen local storage get up-to 11 restore points at one point, but then it was pruned back to 10.
Question - why is it not storing 14 days worth of backups locally as configured?
Backups run once a day with incremental M-Th + Active full on Friday.
SOBR is configured to COPY and MOVE after 14 days from NAS to Object storage.
Here is the kicker: Veeam console shows that only 10 restore points locally (NAS) and correct number of restore points in Object storage. I've only seen local storage get up-to 11 restore points at one point, but then it was pruned back to 10.
Question - why is it not storing 14 days worth of backups locally as configured?
-
- Product Manager
- Posts: 9846
- Liked: 2604 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Strange retention - less than configured
Hi Cali
That‘s difficult to say without knowing your entire backup environment.
You say you see 10-11 restore points. Were the backup jobs successful on each day of the last 2 weeks? If the jobs weren‘t successful or they weren‘t running on some days, then that could be the reason you only see 10 restore points from the last 14 days.
Would it be possible to open a support case and upload the log files? Our support engineers will be able to tell you if something is wrong in your environment after seeing the logs.
Thanks
Fabian
That‘s difficult to say without knowing your entire backup environment.
You say you see 10-11 restore points. Were the backup jobs successful on each day of the last 2 weeks? If the jobs weren‘t successful or they weren‘t running on some days, then that could be the reason you only see 10 restore points from the last 14 days.
Would it be possible to open a support case and upload the log files? Our support engineers will be able to tell you if something is wrong in your environment after seeing the logs.
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Enthusiast
- Posts: 35
- Liked: 9 times
- Joined: Jan 06, 2022 9:20 pm
- Contact:
Re: Strange retention - less than configured
There have been a few instances where one VM was failing to get backed up out of the entire set (have a support case opened, no resolution yet). Even if that was the case, then we should not see just 10 restore points on the local storage and correct amount of restore points in the object storage with the exception of that one VM that is lagging behind in terms of the restore points in Object cloud.
Sure, I can open the ticket, although to be honest so far my experience with support has not been great. Most responses seem to be generic with long pauses in between (days) and support engineers changing half-way through. In fact, in most cases I end up finding solution or at least helpful hints via Google, this forum or Reddit and not through the support.
Sure, I can open the ticket, although to be honest so far my experience with support has not been great. Most responses seem to be generic with long pauses in between (days) and support engineers changing half-way through. In fact, in most cases I end up finding solution or at least helpful hints via Google, this forum or Reddit and not through the support.
-
- Veeam Software
- Posts: 219
- Liked: 111 times
- Joined: Jun 29, 2015 9:21 am
- Full Name: Michael Paul
- Contact:
Re: Strange retention - less than configured
Hi,
I might be misreading this but, your backup job runs Monday to Thursday as incremental but then an active full on the Friday? No weekend processing? In which case this is exactly what I’d expect.
2 weeks = 14 days but 2 weeks of weekdays only = 10, so you’d see an 11th temporarily at the end of a backup but then you’d see it drop to 10 again at the end of the next move process, as your backups would be exceeding the 14 day move window.
Is this what you’re seeing?
I might be misreading this but, your backup job runs Monday to Thursday as incremental but then an active full on the Friday? No weekend processing? In which case this is exactly what I’d expect.
2 weeks = 14 days but 2 weeks of weekdays only = 10, so you’d see an 11th temporarily at the end of a backup but then you’d see it drop to 10 again at the end of the next move process, as your backups would be exceeding the 14 day move window.
Is this what you’re seeing?
-------------
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
-
- Enthusiast
- Posts: 35
- Liked: 9 times
- Joined: Jan 06, 2022 9:20 pm
- Contact:
Re: Strange retention - less than configured
I think you are correct. My default expectation was that it would be working more in terms of restore-point days (days for which backups were made) and not just calendar days. Kind of like the backup job has days/restore points option.
Well, asking in the forum ended up being much faster than going through support in my experience yet again
Well, asking in the forum ended up being much faster than going through support in my experience yet again
-
- Veeam Software
- Posts: 219
- Liked: 111 times
- Joined: Jun 29, 2015 9:21 am
- Full Name: Michael Paul
- Contact:
Re: Strange retention - less than configured
Understandable, it’s a small detail to notice but one with large impact!
Not being a Veeam employee I can’t comment on the support part. Might be worth you dropping your case ID in here though so support management can see what’s going on internally, I’m sure they don’t want negative support stories and would want to seek to improve if they’ve fallen short.
Not being a Veeam employee I can’t comment on the support part. Might be worth you dropping your case ID in here though so support management can see what’s going on internally, I’m sure they don’t want negative support stories and would want to seek to improve if they’ve fallen short.
-------------
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
Who is online
Users browsing this forum: Brian.Knoblauch, Google [Bot] and 117 guests