Comprehensive data protection for all workloads
Post Reply
william88
Enthusiast
Posts: 46
Liked: 13 times
Joined: Feb 27, 2017 7:47 am
Full Name: William
Contact:

Feature request: disable backup copy job after the current run completes

Post by william88 »

Hi,

When we want to stop the backup copy job, a pop-up warns us that the backup status will be inconsistent if we stop it now.
It would be good to have the option to disable the job after the current run completes.

Thank you
david.domask
Product Manager
Posts: 3999
Liked: 974 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Feature request: disable backup copy job after the current run completes

Post by david.domask »

Hi william88,

Request is understood from technical perspective, but may I ask why do you want to disable it?

If it's to control when data can transfer, doesn't a Backup Window help here?

If you could explain the use-case a bit more will help us to better understand your need.
David Domask | Product Management: Principal Analyst
william88
Enthusiast
Posts: 46
Liked: 13 times
Joined: Feb 27, 2017 7:47 am
Full Name: William
Contact:

Re: Feature request: disable backup copy job after the current run completes

Post by william88 »

Hi David,

Thank you for your reply.

Currently, the job is configured to copy immedialy every restore point (mirroring). The repository is hosted by our provider (WAN transfer).
Occasionally, our remote storage space becomes full or experiences technical issues; when this happens, we want to deactivate the task properly whilst we find a solution
The problem is that the job relies on around eight other source jobs (each containing numerous VMs), and for each source job, the task is retried numerous times, which takes a long time and generates a lot of error emails… Then the job restarts automatically, and if we’re not on the VBR console, we can’t stop the task properly.

Please do let me know if my explanations aren’t clear.
david.domask
Product Manager
Posts: 3999
Liked: 974 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Feature request: disable backup copy job after the current run completes

Post by david.domask »

Thanks for the explanation, I understand the situation, but I guess not quite sure on the benefit of disabling it each time as you'd need to re-enable it later on manually.

We can consider the request, but for now I would advise use a post-job script and Disable-VBRBackupCopyJob. Keep in mind, disabled jobs need to be re-enabled manually, so I'm really not sure automatically disabling the job is really the answer here, and if the target storage frequently has issues, it's better to find a more permanent solution. If space contention is persistently an issue, I would recommend you and your Provider use the Data Change History Veeam One report to better size your allocated space and to better predict your future growth.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], DanielJ, Google [Bot] and 201 guests