Backup Copy Job [Feature Request]

Availability for the Always-On Enterprise

Backup Copy Job [Feature Request]

Veeam Logoby mattmcg » Thu Mar 02, 2017 9:11 am

I am using the latest release of Veeam B&R 9.5 (Update 1).
I have configured a Backup Copy Job to copy all of the various backups to an external set of rotated drives.

When viewing the copy status in the desktop client I can see that the copy job is idle (not currently running/processing any VM backups).
However, if I drill down into the copy job I can find the last VMs to be processed are still in the "Processing" state, even though their details say that there was nothing to process for those VMs.
If I then attempt to disable the copy job (because I need to change the rotated drive), The job then issues a warning that I terminated the copy job.
This is not true as it's state was idle and all previous processing was complete.

What I expect to happen when a copy interval completes is that the complete job is marked as a success and then goes into the idle state.
If disabling the job when in the idle state, this should not issue warnings about a process being terminated (as there is not process working (Because it is idle).

As I work for a software house, we have an internal policy where all warnings are treated as errors.
Currently this false warning is causing a lot of internal support requests and email notifications.

Please can this be updated to work as expected?
mattmcg
Novice
 
Posts: 4
Liked: never
Joined: Thu Mar 02, 2017 8:50 am
Full Name: Matthew McAtamney-Greenwood

Re: Backup Copy Job [Feature Request]

Veeam Logoby v.Eremin » Thu Mar 02, 2017 12:23 pm

The job then issues a warning that I terminated the copy job.

This should only happen if during a sync interval a backup copy job hasn't copied anything. If you disable a job that has already archived a restore point within current interval, no warnings will be generated. Thanks.
v.Eremin
Veeam Software
 
Posts: 12864
Liked: 934 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Backup Copy Job [Feature Request]

Veeam Logoby mattmcg » Thu Mar 02, 2017 12:43 pm

In our environment this is sometimes to be expected.

Most of the backups are for templates and VMs that are set to revert to a snapshot on shutdown.
Therefore a Backup Copy interval starts, determines there is nothing changed, then goes idle until the next interval.

This should be equivalent to a completed run and should not cause a warning when disabling as there is actually nothing in-flight.

At the very least this should be an option within the Backup Copy Job configuration?
To set it so that each interval is considered a run rather than, if nothing happened then just sit and wait until something does happen.

Also I find this is also the behaviour when regardless of how many Backup Jobs are part of the Copy Job, and regardless of how many VMs are in each Backup Job.
If the last one had no changes (regardless of whether any other VMs had changes) it also sits and hangs in the idle state where disabling will fire the same warning.
mattmcg
Novice
 
Posts: 4
Liked: never
Joined: Thu Mar 02, 2017 8:50 am
Full Name: Matthew McAtamney-Greenwood

Re: Backup Copy Job [Feature Request]

Veeam Logoby v.Eremin » Fri Mar 03, 2017 8:53 am

This should be equivalent to a completed run and should not cause a warning when disabling as there is actually nothing in-flight.

I don't believe so, since there is no guarantee that no new restore points to copy will appear during current interval.

Therefore, when you disable a backup copy job, you basically terminate it before it does its duty. And that's what the said warning suggests.

Anyway, we do appreciate it feedback; thank you again for raising this issue. We might consider changing existing warning pattern down the road.
v.Eremin
Veeam Software
 
Posts: 12864
Liked: 934 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Backup Copy Job [Feature Request]

Veeam Logoby mattmcg » Fri Mar 03, 2017 9:32 am

So maybe I have the wrong configuration.

I have my backup copy job set to 1 day interval (so the files roll-over on a daily basis).
During this the copy job seems to activate every 2 mins approx to check for changes.

Am I wrong in thinking that these checks for changes should not interfere and cause this warning?

Considering my copy job is just set to copy backups that have already been performed, does it actually need to sit and poll for changes?
Should this not just wait for each backup job to complete (I'm sure there is an event for this as I can setup SNMP ping when job completes).

Even with the polling, as it currently appears to work, why does it produce the warning while it is idle?
Surely the fact it is idle means there is nothing being processed and therefore is safe to disable?
mattmcg
Novice
 
Posts: 4
Liked: never
Joined: Thu Mar 02, 2017 8:50 am
Full Name: Matthew McAtamney-Greenwood

Re: Backup Copy Job [Feature Request]

Veeam Logoby v.Eremin » Fri Mar 03, 2017 10:23 am

Even with the polling, as it currently appears to work, why does it produce the warning while it is idle?

Because it has not copied anything within the current interval. So, in other words it's failed to perform its duty - create a restore point within allocated sync inteval.

Surely the fact it is idle means there is nothing being processed and therefore is safe to disable?

Not exactly. The fact that backup copy job has not copied anything yet does not necessarily mean that it won't copy something before current interval finishes.

I have my backup copy job set to 1 day interval (so the files roll-over on a daily basis).

At what time does a source backup job start? And at what time does a sync interval for a backup copy job start?
v.Eremin
Veeam Software
 
Posts: 12864
Liked: 934 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Backup Copy Job [Feature Request]

Veeam Logoby mattmcg » Fri Mar 03, 2017 10:39 am

Because it has not copied anything within the current interval. So, in other words it's failed to perform its duty.

This I think is irrelevant. If there is nothing to update then how can it be a failure? Granted nothing completed processing, but also nothing started processing.

The fact that backup copy job has not copied anything yet does not necessarily mean that it won't copy something before current interval finishes.

In the case where the copy job is going to a rotated drive repository, should there not be an option to suspend while drives are being rotated?
Ultimately I am not trying to "cancel" the process, I just don't want errors if it tries to do a check while I have disconnected the drive during a rotation.

At what time does a source backup job start? And at what time does a sync interval for a backup copy job start?

My actual backups are configured differently for each environment (users based in different timezones across the world).
Therefore their backups are performed at a time their users are not using the VMs (Although these VMs may still be powered on; e.g. Domain Controllers).
The backup copy job is set for copying all changes throughout the day and is set to "roll-over" at midnight UTC (so there is only a single incremental backup for each day of the week).
The rotated drives can be replaced at any point during the normal UK working day.
mattmcg
Novice
 
Posts: 4
Liked: never
Joined: Thu Mar 02, 2017 8:50 am
Full Name: Matthew McAtamney-Greenwood

Re: Backup Copy Job [Feature Request]

Veeam Logoby v.Eremin » Mon Mar 06, 2017 12:35 pm

If there is nothing to update then how can it be a failure?

Firstly, how you can be sure that there is nothing to update, if the current interval is yet to expire? There is no guarantee that no new source restore points will appear.

Secondly, it's not a failure, but rather a warning.

In the case where the copy job is going to a rotated drive repository, should there not be an option to suspend while drives are being rotated?

Disable option does exactly that. Though, by design if you disable a job within currently lasting interval, and no restore points have been copied within it, a warning will appear.

Anyway, it seems that this discussion is running in circles. I think I got your feature request, so consider your voice counted. :)
v.Eremin
Veeam Software
 
Posts: 12864
Liked: 934 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], jslic and 48 guests