Had to stop job, now what?

Hyper-V specific discussions

Had to stop job, now what?

Veeam Logoby JCauthen » Fri Dec 04, 2015 4:05 pm

When stopping a job I get the warning "Backup's files for this job will be left in the inconsistent state. One or more VMs will have incomplete, unusable restore points. Stop the job anyway?"

I'm fine with losing the backups that didn't complete but I don't want to jeopardize the restore chain any more than I need to. What is the best way to maintain integrity?
JCauthen
Novice
 
Posts: 5
Liked: never
Joined: Tue May 12, 2015 1:31 pm
Full Name: Joshua Cauthen

Re: Had to stop job, now what?

Veeam Logoby foggy » Fri Dec 04, 2015 4:22 pm

You should be fine with stopping the job, previous restore points will not be compromised. The next job run should clean up inconsistent restore point and start creating new one.
foggy
Veeam Software
 
Posts: 14752
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Had to stop job, now what?

Veeam Logoby JCauthen » Fri Dec 04, 2015 5:52 pm

Oh super. Thanks.
JCauthen
Novice
 
Posts: 5
Liked: never
Joined: Tue May 12, 2015 1:31 pm
Full Name: Joshua Cauthen

Re: Had to stop job, now what?

Veeam Logoby blaked36 » Sun Jan 03, 2016 12:27 am

foggy wrote:You should be fine with stopping the job, previous restore points will not be compromised. The next job run should clean up inconsistent restore point and start creating new one.


Does that include continuing the prior backup chain? One issue I've had is that I'd like to continue a prior backup chain after canceling an active full backup. For instance, let's say the last active full backup (.vbk file) is from December 1, and I have 15 .vib files made since that December 1 .vbk. If a new active full job started last night and I had to cancel it for some reason, could I run an incremental that continues the chain from the December 1 .vbk? In the past it seems like it only wanted to do an active full at that point, even if I didn't choose that.
blaked36
Lurker
 
Posts: 2
Liked: never
Joined: Sun Jan 03, 2016 12:17 am
Full Name: Blake Dollens

Re: Had to stop job, now what?

Veeam Logoby foggy » Tue Jan 05, 2016 10:40 am

Blake, in case you've initiated and then stopped active full, the next job run will clean up inconsistent restore point and attempt an active full run again.
foggy
Veeam Software
 
Posts: 14752
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Had to stop job, now what?

Veeam Logoby mkaec » Thu Jan 07, 2016 2:49 pm

foggy wrote:You should be fine with stopping the job, previous restore points will not be compromised. The next job run should clean up inconsistent restore point and start creating new one.

That's good to know. The dialog text made me think I'd be losing the whole chain.
mkaec
Expert
 
Posts: 179
Liked: 48 times
Joined: Thu Jul 16, 2015 1:31 pm
Full Name: Marc K

Re: Had to stop job, now what?

Veeam Logoby blaked36 » Tue Jan 12, 2016 5:16 pm

foggy wrote:Blake, in case you've initiated and then stopped active full, the next job run will clean up inconsistent restore point and attempt an active full run again.


Okay, that's consistent with what I've seen. As long as I know what to expect, that's fine. I guess I could call it a "feature request," though: the ability to stop an active full backup and continue on from the prior chain's active full and .vib files. Thanks for clarifying.
blaked36
Lurker
 
Posts: 2
Liked: never
Joined: Sun Jan 03, 2016 12:17 am
Full Name: Blake Dollens

Re: Had to stop job, now what?

Veeam Logoby PTide » Tue Jan 12, 2016 5:44 pm

Hi,

I guess I could call it a "feature request," though: the ability to stop an active full backup and continue on from the prior chain's active full and .vib files. Thanks for clarifying.
Then you might be interested in such feature as "stop job gracefully" which is available in v9. When active full is stopped gracefully the next job run will continue making active fulls for those VMs that have not been processed during previous run, and place them into single .vib file alongside with incrementals for VM that have been processed. With per-VM backup chains graceful stop will do even smarter thing - each VM-chain will be continued with incrementals from the last succesfull restore point.
PTide
Veeam Software
 
Posts: 3022
Liked: 247 times
Joined: Tue May 19, 2015 1:46 pm


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 10 guests