Hi,
when installing a Veeam B&R update you have to manually disable all jobs, even if there aren't any running transfers. Would it be possible to make setup a bit smarter, so that it detects that there are no data transfers currently active and that Veeam setup temporarily disables the jobs by itself and enables them after setup is complete? This would make the requirement for manual intervention when installing an update a bit less work
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
-
- Veteran
- Posts: 3077
- Liked: 455 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Feature request: Make the update process a bit smarter
Hi Franc,
Thank you for the request!
Do you have any suggestions on how to prevent situations when a user kicked off an update and blindly skipped the warning mentioning that all jobs will be disabled automatically? Also, I'm afraid it's a bit complex functionality that can potentially cause issues and lots of bugs, but we'll definitely see if there is something that can be done to simplify this task in future versions.
Thanks,
Fedor
Thank you for the request!
Do you have any suggestions on how to prevent situations when a user kicked off an update and blindly skipped the warning mentioning that all jobs will be disabled automatically? Also, I'm afraid it's a bit complex functionality that can potentially cause issues and lots of bugs, but we'll definitely see if there is something that can be done to simplify this task in future versions.
Thanks,
Fedor
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Feature request: Make the update process a bit smarter
Hi,
but when setup is successful it should automatically enable the jobs again that it had disabled prior to the start of the update. So not blindly disable en enable all jobs, but only those jobs that were enabled at the start of the update so that we don't get into a situation where disabled jobs by the user are also enabled again.
but when setup is successful it should automatically enable the jobs again that it had disabled prior to the start of the update. So not blindly disable en enable all jobs, but only those jobs that were enabled at the start of the update so that we don't get into a situation where disabled jobs by the user are also enabled again.
Who is online
Users browsing this forum: alxz89, Baidu [Spider], C.Lahiani, esteven, JasonBailey and 118 guests