Comprehensive data protection for all workloads
Post Reply
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Feature Requests

Post by tevans8 » 1 person likes this post

I would like to see that the termination window prevents manual retries (or manual starts if they apply) of jobs set with a termination window.

I would also like to see that if 1 VM in a job stuck in preparing guest for hot backup does not hang the entire job. I would like to see a timeout that allows the job to proceed or the other VMs can proceed without this 1 VM.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Feature Requests

Post by foggy »

tevans8 wrote:I would like to see that the termination window prevents manual retries (or manual starts if they apply) of jobs set with a termination window.
Unless something has changed since this post (need to check), it should work the way you want it.
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

It sounds like the post referenced is saying what my problem is. I have the terminate box checked; however, I want to prevent any user from running a job manually outside of that window. When I raised this with support, they stated that indeed manual retries can be run with the box checked.
Gostev
Chief Product Officer
Posts: 31460
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Feature Requests

Post by Gostev »

tevans8 wrote:I would also like to see that if 1 VM in a job stuck in preparing guest for hot backup does not hang the entire job. I would like to see a timeout that allows the job to proceed or the other VMs can proceed without this 1 VM.
Such timeout is included in Update 1 for v9.
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

Awesome! I see where this post mentions mid-March. I will be on the lookout for it!

Side note, thanks for "The Word from Gostev" in the newsletter. I read it every week.
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

REF: Case # 01723161

Can we bring back the feature in Veeam 7 and previous to not run jobs (retry or otherwise) during termination window? I am still confused by this (above posts and my support cases).
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Feature Requests

Post by foggy »

Support is correct, this is the behavior starting from v8: the terminate window setting prevents the job from running by schedule, but manual runs are allowed.

So your request is more like having the ability to define roles within the Veeam B&R management console to be able to limit the scope of allowed functionality for users.
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

foggy wrote:So your request is more like having the ability to define roles within the Veeam B&R management console to be able to limit the scope of allowed functionality for users.
I would disagree. What I need is the ability to force a policy above ANY user interaction. As a MSP, we have 126 jobs in this particular Veeam console. If multiple fail, someone (no matter their permissions role) may not remember which customer has a termination window and could bulk select and retry. For most of our customers, this is not a concern. But for the ones that it is, it is VERY critical. It bothers me that I have no real control over this and that it's dictated by Veeam software. (This coming from someone who loves Veeam and has been using it for over 4 years for almost 2000 VMs).

In Veeam 7 and previous, at least the window could be disabled to run on-demand. However, there is NO end user control when you WANT to enforce a termination policy. This feature request needs to be re-worded as:

Please create a check box "Allow terminated jobs to be run on-demand". If checked, Veeam would function as it does in v8. If not, it would function like in v7.
Gostev
Chief Product Officer
Posts: 31460
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Feature Requests

Post by Gostev »

I was under impression that we warn and ask for an explicit confirmation when you are trying to perform an action on the job during the blackout window. Or, are you saying this is not the case?
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

I have never seen that nor has support mentioned it.
Gostev
Chief Product Officer
Posts: 31460
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Feature Requests

Post by Gostev »

OK, this is something that we will want to add then.
tevans8
Enthusiast
Posts: 30
Liked: 5 times
Joined: Jun 21, 2012 8:48 pm
Full Name: Travis Evans
Contact:

Re: Feature Requests

Post by tevans8 »

Any clarification as to what this means? Is something coming in v9 U2? Is the something a warning that asks for an explicit confirmation or a feature like I suggested (a check box "Allow terminated jobs to be run on-demand". If checked, Veeam would function as it does in v8. If not, it would function like in v7.)
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Feature Requests

Post by foggy »

Anton was talking about adding a warning in case of manually starting the job outside its backup window. As far as I know, this will be addressed in the next version.
Post Reply

Who is online

Users browsing this forum: Semrush [Bot], ShawnKPERS and 255 guests