Host-based backup of VMware vSphere VMs.
Post Reply
User56
Enthusiast
Posts: 30
Liked: never
Joined: Mar 11, 2017 9:53 am
Contact:

Restart Windows Server VM during Backup Operation OK?

Post by User56 »

Hello,

Customer have Vmware ESXi 6.0 essential with 5 Windows Server 2016 VMs.

He has one Veeam JOB for Backup these VMs.

It takes severall hours for the job to complete.

I think it is complete backup once a week and inkr. every day.

Is it ok to restart one or two of the Windows Server Backups during Backup operation? (I mean if the VM is not pending...if the VM Backup is e.g. at 50%)
ejenner
Veteran
Posts: 636
Liked: 100 times
Joined: Mar 23, 2018 4:43 pm
Full Name: EJ
Location: London
Contact:

Re: Restart Windows Server VM during Backup Operation OK?

Post by ejenner » 1 person likes this post

If it hasn't got to the server that you want to restart then that wouldn't be a problem.

Depends on how you have it set up, but even with the server powered off in VMware I would have thought it can still be backed up with some configuration of the backup.

You can view where in the process the job is by clicking on the machines in the job log at the lower part of the console window.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Restart Windows Server VM during Backup Operation OK?

Post by foggy »

I'd also take a look at why it takes so long to backup just a few VMs. What is the total size of these VMs and what are the bottleneck stats for this job?
Anders
Enthusiast
Posts: 58
Liked: 12 times
Joined: Sep 09, 2010 9:45 am
Full Name: Anders Lorensen
Contact:

Re: Restart Windows Server VM during Backup Operation OK?

Post by Anders »

The only time when the VM should not be rebooting is before the VMWare snapshot is being created. After the VMWare snapshot is created on a VM, you can do whatever you like inside it.

If application awareness is activated though, for example on a SQL server, and you want it to truncate the SQL transaction logs when the job is finished, you want the VM to be running the entire time, so the VSS writer state is not affected.
Post Reply

Who is online

Users browsing this forum: No registered users and 77 guests