Skip to main content
Question

Last full backup not picked up for copy for selective copy


Forum|alt.badge.img+5

Dear Vaulters,

I have an issue, I have a storage policy with a selective copy for last full backup of the month on the tape library, when i review its jobs i find 30th of march full backup jobs instead of 31st of march full backup jobs.

I made sure that AUX copy job ran 1 hour after 31st of march full backup jobs.

I also noticed that this issue is not happening with all clients, it happens with random clients every month.

Need your support to know the cause the aux copy to pick 30th of march full backup jobs instead of 31st of march full backup jobs? and how to solve it?

 

BR

Forum|alt.badge.img+15

Hello ​@Ahmed Elbably 

Thanks for the great question!
There are a few little things that can make this happen that i would like you to check.

First, don’t worry about when an Aux copy job runs. The Aux copy does not pick anything for copy, it just moves everything that has been marked for copy and is waiting to do so. So don’t stress on when it runs. 

Second, When the month closes the CS will mark all jobs that fit the criteria for copy. in your case the last full of the month. A running job is not a valid job for copy so even if it started on the 31st, did it finish on the 1st? If so it is not valid for copy and the job that ran on the 30th is the job selected. 

If have seen this happen a few times and catch people out.This could also explain why some are hit and some are not. if you are scheduled to run at 10pm on the 31st and only your larger clients run for longer than 2 hours it will result in some picking the 30th for copy and others the 31st. 

Kind regards
Albert Williams


Forum|alt.badge.img+5
Albert Williams wrote:

Hello ​@Ahmed Elbably 

Thanks for the great question!
There are a few little things that can make this happen that i would like you to check.

First, don’t worry about when an Aux copy job runs. The Aux copy does not pick anything for copy, it just moves everything that has been marked for copy and is waiting to do so. So don’t stress on when it runs. 

Second, When the month closes the CS will mark all jobs that fit the criteria for copy. in your case the last full of the month. A running job is not a valid job for copy so even if it started on the 31st, did it finish on the 1st? If so it is not valid for copy and the job that ran on the 30th is the job selected. 

If have seen this happen a few times and catch people out.This could also explain why some are hit and some are not. if you are scheduled to run at 10pm on the 31st and only your larger clients run for longer than 2 hours it will result in some picking the 30th for copy and others the 31st. 

Kind regards
Albert Williams

Dear Albert,

Thanks for detailed explanation.

 

My only concern that some clients are scheduled to backup at the same time let’s suppose at 6:00 pm and finish at 6:30pm daily, on 31st of March at 9 pm an aux copy job ran and i see that not all backup jobs for these clients are picked for copy.

I can understand it’s abnormal behavior and it may be a bug.

What to do as it is a big concern for my team.

BR 

 


Forum|alt.badge.img+15

Hello ​@Ahmed Elbably 

If you think you have found a bug, document it all, make sure you are already on the latest MR and raised a ticket to support. 

They will validate the bug and push it to Dev to fix it in a MR. 

Kind regards

Albert Williams


Forum|alt.badge.img+5

Dear ​@Albert Williams

Thanks for your supportive replies.

 

Sure I’ll do, But first I need to make sure it’s an abnormal behavior,

 

I can see that all affected clients are DB2 databases, I also see that the full backup of 30th of March and command line backup jobs depending on it are available on the selective copy not the full backup of 31st of March.

 

Is it normal ?

 

BR


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings