[ENHANCEMENT REQUEST] Upgrade backup to restore original job state, and time stated to be more realistic

[AlexHeylin]

Case # 07014199

Enhancement requests for:

1. Update statement on time to something more realistic, not one minute - more like 4-10 mins. It’s better to say longer than it takes, than to say too short.

2. Upgrade backup to return job to previous enabled / disabled state upon completion. Without this an admin has to sit and wait for it to finish
just to reenable the job, which is something the task could do itself – OR they can’t wait and backups will not occur until the job is enabled again, likely after the failure to backup triggers a manual process to check on the jobs.

[Mildur]

Hi Alex

Thanks for the requests.
Can you please check your case id? I cannot find it in the system. Cases for Veeam Backup & Replication currently are starting with #06******

Best,
Fabian

[AlexHeylin]

Hey Fabian,
Yep - it definitely shows Case #07014199 in my.veeam.com. I see another recent case starting 07 too.
Thanks

[david.domask]

Hi @AlexHeylin,

I can explain the case numbering, we did some changes on the CRM backend, so new cases will start with 07*, so everything's normal there Existing cases will still be with 06*.

As for your requests, I can see the logic on it. Out of curiosity, would maybe adding a parameter that will re-enable jobs to the script from the User Guide for automated upgrades be suitable for short term? Or you'd rather avoid scripting entirely?

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

[AlexHeylin]

Hi David,
While you're here - can I ensure you've seen Case #06410170 - thanks.
My use case was entirely GUI based. I think it's more a case of expected (and useful) behaviour. It might even not be worth "fixing" it if this is only going to happen once on the VBR version change - but I think it's worth acknowledging the expected behaviour and aiming to code to it the next time a situation like this occurs where an post upgrade action (etc) is run and jobs need to be disabled. All of that said - automation is always good (when it works!), so if there's not a switch for it then perhaps there should be too.
Thanks

[david.domask]

Hi Alex, thanks for the response just wanted to check if this helped your use case, but I will suggest the change for the automation script regardless.

As for the case, I will DM you.