+8Hey all - I am working with a customer on SQL log backups. The log RPO on the plan is 15 minutes and we verified in the Java GUI that the auto schedule is also 15 minutes. the problem is the logs are backing up every 30 minutes and we can’t figure why.
What could I be missing?
Thanks!
Best answer by Mike Struening RETIRED
Sharing the case solution:
The RPO set on the plan is designed to check in the database qualifies for a new backup at that set interval.
In this case every 15 minutes it was checking if the log file is 80% utilized as the settings are configured.
- As the log was not 80% utilized it would then skip the 15 RPO backup
It was also set to force a backup every 15 minutes. This was not running every 15 minutes because it calculates the end time of the last job.
15 minutes from the start time of the previous job it checks if it qualifies for a backup.
- As explained above it skips the normal RPO backup because the log is not 80% utalized.
- It also skips the force backup because it has only been about 8-12 minutes since the END time of the last job. As it has not been 15 minutes it then skips the force job.
15 minutes later (30 minutes from the start time of the last job) it does the same check again.
- Either the log file is now 80% utilized or its over 15 minutes from the end time of the last job, so the job then runs again.
Customer reverted to a Daily schedule setting to repeat every 15 minutes as a workaround to get more consistent backups every 15 minutes
+23Hmmmm, definitely an interesting one. I thought perhaps that the jobs were taking a bit longer than expected, extending the time out but that’s not the case.
What’s also interesting is that the jobs are not a straight 15 or 30 minutes apart either, though it’s awfully close to 30 minutes.
I’m going to chat with some of our SQL folks and see if they can advise here.
+18I don’t know the answer, but I’m testing the 15 min config in my lab. It’s working as expected.
Thanks,
Scott
+15You probably already checked, but when you double click that job, can you make sure that the schedule that is being triggered is the one you actually want (15min)?
+8
+23We definitely need that award, and so far you might be a contender!
I’m hoping to get some of our support folks to take a look as well.
+15Create a second schedule similar to the one in question and assign to one of the existing clients currently in the schedule you are showing.
Remove this client from the main schedule you are showing on the screen and see if that shows every 15 or 30?
Did you recently updated the CommCell?
+15Also, by reviewing your first screen shot, I do not see an option marked there for example Daily.
Reading the docs I see that;
Continuous: source
Runs an administration or backup job continuously. The next job session of a continuous schedule starts automatically after the previous job completes. You can define the time interval between two backup job sessions. By default, the next job session starts 30 minutes after the previous job session completes.
+15Yes, I think we are getting to the point here.
Doc: https://documentation.commvault.com/11.24/expert/96314_configurations_for_rpo.html
By default, the plan includes a continuous incremental schedule set to the RPO value for the plan.
It links to the point I mentioned above about Continuous schedules.
Now what I would do here to just quick test is simple change from Continous to Daily and monitor for 30 mins. It should run twice.
+8Job Interval
Set up the job based on the log files in the destination directory.
Back up on file activity every
This parameter ensures that the software does not frequently run the job. The software does not check the other options during this interval.
Force a backup every
This parameter ensures that the software backs up the logs even when the other options have not been met. For example, if the parameter is set to 24 hours and the software has not run an automatic log backup in that time, the software will start a backup without checking the other options.
I’m assuming that this should be following the 15 minutes based on this unless I’m missing something or we don’t have some sort of check box checked.
+15Continuous schedule of VSA snap backup copy may not execute every 4 hours as configured 4471, 4472
See this one too, but the description is not completely clear.
Continuous schedule may kick of jobs repeatedly for SQL subclient 3801, 3802
Maybe Mike has more info on this, but there are quite a few updates related to Continuous jobs, so would not be surprised if any of the above were to fix that.
+23+23Can you create an incident and share the number so I can track accordingly?
+8Thanks for your help on this!
+23Sharing the case solution:
The RPO set on the plan is designed to check in the database qualifies for a new backup at that set interval.
In this case every 15 minutes it was checking if the log file is 80% utilized as the settings are configured.
- As the log was not 80% utilized it would then skip the 15 RPO backup
It was also set to force a backup every 15 minutes. This was not running every 15 minutes because it calculates the end time of the last job.
15 minutes from the start time of the previous job it checks if it qualifies for a backup.
- As explained above it skips the normal RPO backup because the log is not 80% utalized.
- It also skips the force backup because it has only been about 8-12 minutes since the END time of the last job. As it has not been 15 minutes it then skips the force job.
15 minutes later (30 minutes from the start time of the last job) it does the same check again.
- Either the log file is now 80% utilized or its over 15 minutes from the end time of the last job, so the job then runs again.
Customer reverted to a Daily schedule setting to repeat every 15 minutes as a workaround to get more consistent backups every 15 minutes
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
