Hi guys, I am having problems with one particular VM which is causing me headaches.
Basically if the snapshot removal process takes place between 9am and 5pm we quite often get calls from the client saying they have been kicked off (it's a DC). The Veeam job which this particular VM is a part of features around 12 servers so de-dupe is pretty good and I want to keep it there, but I'd love to be able to independently say how many retries this one VM goes ahead with - what do you guys think of this idea?
The job as a whole is set to carry out 3 retries, which is helpful for the other servers - just not this one.
-
- Enthusiast
- Posts: 68
- Liked: 2 times
- Joined: Jun 14, 2012 10:56 am
- Full Name: Jamie Pert
- Location: twitter.com/jam1epert
- Contact:
Veeam Feature Request: Independent retry values
@jam1epert on Twitter
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam Feature Request: Independent retry values
Jamie, connectivity issues during snapshot commits are typical. I do not fully understand your point regarding job retries in this context as VM is still backed up successfully.
-
- Enthusiast
- Posts: 68
- Liked: 2 times
- Joined: Jun 14, 2012 10:56 am
- Full Name: Jamie Pert
- Location: twitter.com/jam1epert
- Contact:
Re: Veeam Feature Request: Independent retry values
The backup is completed fine, but for some reason a few servers we deal with have a hissy fit when the snapshot removal process finishes. Overnight this is fine, but if a retry occurs and finishes during business hours it's a big problem
@jam1epert on Twitter
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam Feature Request: Independent retry values
Got you, thanks for the feedback.
Who is online
Users browsing this forum: Google [Bot], massimiliano.rizzi, NightBird and 122 guests