Backup Copy Last Day of Month archival

[akrietsch]

Hello, I have set up numerous backup copy jobs to move my backups offsite. They each are set up to keep a certain number of restore points for monthly backups. I have selected "Last day of the month" in the scheduling options. Now that it has been a few months, I have looked back at the restore points and noticed that it is never quite the last day of the month that is actually being kept. It is always a day or two off. An example of one of the VMs in these jobs is as follows.

FULL 6/29 (last day should be 6/30)
FULL 7/29 (last day should be 7/31)
FULL 8/30 (last day should be 8/31)
FULL 9/28 (last day should be 9/30)

We backup our VMs every evening between the 7pm-12am window. Our backup copy jobs are set up as "continuous" and they copy every 1 day, starting at 3:00am. Is the fact that these jobs start at 3:00am and the actual backups are from the previous day's evening what is throwing off the dates? If so, what should I change to get these dates lined up properly?

[Shestakov]

Hello Alex,
GFS backup is created in the last day of retention.
My guess is in June there was an incremental run on 29th and on 30th backup copy didn`t find any new restore points so no increments were created on 30th. Thus 29th restore point was recognized as the last backup of the day.
By the way, what is the basic retention?
Thanks!

[akrietsch]

We get backups each day, so there would have been one for 6/30. If it was just one month that was off then maybe it was just a missed backup, but every month's month-end backup is off by a day or two. As for what the basic retention is, on this particular backup copy job we have it set to keep 15 restore points and 4 monthly backups (on last day of the month).

[Shestakov]

Looks strange. Do you have Read the entire restore point from source backup instead of synthesizing it from increments option enabled?

[akrietsch]

No, that option isn't checked.

[Shestakov]

Thanks for the reply.
The issue looks like a bug so I would suggest to contact Veeam support for deeper investigation.
Once you do, please post support case number here.

[akrietsch]

Thanks, #02366548.

[onob9999]

I guess that the schedule for BC job is "continues" which would trigger the job to start at 00.01 and the RP will be based on available RPs at that point. Probably there is no RP for 30/6 at that point?

//Jon

[Shestakov]

Hi Jon,
I had the same assumption, but Alex (OP) said that was not a case, so let`s wait for the support investigation.

[YouGotServered]

Hey guys, any update here? I'm not having this problem, but I'm wildly curious. If this is some Veeam behavior, I'd like to know how it works / thinks

[Shestakov]

Looks like there was a bug which is now fixed. To obtain hotfix, contact support team or wait for the upcoming release.
Thanks!