Folks,
I have a backup job that backs up our SQL database servers, running at 03:00 a.m., with a Secondary Target that is a backup copy job with the same VMs in it. The backup copy job mode is set to "Periodic copy (pruning)", and the time is set to 15:00. But the backup copy job seems to behave like a Mirroring job, because when the job starts at 15:00, it always says that "The latest restore point is already copied". And the restore points correspond to those in the main backup job, so the copying has clearly occured. But there is nothing in the job logs indicating when the copying was done.
Both these jobs are very old, and both of them were most likely created before the Mirroring copy mode was introduced. Perhaps this has something to do with it? I don't know. This is not really a problem, I am just curious to know why the jobs behave like this.
Kind regards,
PJ
-
- Veteran
- Posts: 502
- Liked: 55 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
-
- Product Manager
- Posts: 9327
- Liked: 2475 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Copy mode - Mirroring vs. Pruning
Hi PJ
I recommend to open a support case when you see such unexpected behavior.
It may be possible that there is an undetected upgrade bug for old copy jobs.
Best,
Fabian
I recommend to open a support case when you see such unexpected behavior.
It may be possible that there is an undetected upgrade bug for old copy jobs.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 502
- Liked: 55 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
Re: Copy mode - Mirroring vs. Pruning
Case #05965831
Who is online
Users browsing this forum: Bing [Bot] and 199 guests