I upgraded 7 different sites from V11 to V12. Every site has a backup job that runs every hour.
Since the upgrade, every single site started doing backups every 2 minutes. This wasn't a one off...this was literally EVERY SITE.
I have no idea why and after I went into the jobs and changed them from hourly to monthly and then back to hourly the schedule looks correct again (but will know in hour I guess )
Just a heads up for anyone using hourly backup schedules to check em
That sounds strange and unexpected.
Could you please open a support case and upload the logs from one server?
We need to check this. Please don't forget to share the case number with me.
We did see this as well on a couple of V12 upgrades last week. After enabling the job after the upgrade it would run over and over every few mins.
For the affected VM backup job at each site we just edited and stepped through to the end (leaving the settings in place) and it then ran on the correct schedule. Was a little odd but otherwise seemed to resolve with that so didn't pursue it any further.
Case # 05951804 - I will try and upload logs...I need to copy from some slow ass sites so the multi-gb logs were failing but I will keep trying.
for us..we were keeping 168 retention points....with a weekly full...I now have 2000+ snapshots and have filled the disk at one site...probably going to delete the entire chain and let it do another full...only way I see to easily recover. that should also move my backups to the new format too I think.
Ha..I changed retention to 30 points and now I am back to having 1TB free...whew....that should hopefully fix the retention going forward.
Niko, based on the case ID provided by Mark the issue is still in research. To get quick assistance, please open a support case and let us know your case ID.
Hello Vitaliy, thank you for your quick reply. i deactivated the backup job, changed the schedule to monthly. then reactivated the job and set the schedule back to hourly. Now the backupjob runs hourly again and not minutely. However, I would not like to have to do this every time I update our customers to V12..
I got confirmation that this is a known issue for backup jobs and agent protection groups.
It only happens under a very specific upgrade path (v10 - v11 - v12) and can be fixed with opening the job/protection group and saving it again. No changes required. This will update the job in the configuration database with the correct properties.
We are discussing internally if we can provide a script to resolve this issue for backup server with a lot of jobs.
