Start a Conversation

Unsolved

This post is more than 5 years old

1542

November 22nd, 2016 02:00

VMWARE Backups Complete but VM shuts down after backup.

Dear All

I have a customer, which is having ESXi 5.1 and around 7 physical ESX servers and 60 Virtual machines on them.

NetWorker version is 8.2 with target as Data Domain - DD2500.  We are using hot add as the backup procedure. WE cannot perform backups using VBA.

When backups start, they run and complete successfully, but after sometime (say after 30 mins) and sometimes even during backups the VMs reboot. We have tried NBD and hot add both and same issue persists. When he stops performing backups - the reboots vanish.

Is there something that we are missing, I have raised support cases with EMC and VMWARE both... none of them found any configuration issue.

Thanks!

96 Posts

November 22nd, 2016 04:00

Hello.

Take a look at the Vcenter Event Logs and alerts. You should see an event when snapshot is created and, once backup ends, the snapshot should be deleted. Maybe the datastore turns inaccessible?.

Check if VDP is not present. VDP and VBA are incompatible.

November 22nd, 2016 08:00

Hi ledugarte ,

Thanks for the answer, but we are not using VBA, also the snapshot gets deleted after the backup completes...

November 22nd, 2016 08:00

Dear Deb

Thanks for the reply, we did disable the CBT and then tried backups and still faced the same issue.

We enabled CBT and the issue persisted.
Also we are not using VBA here...

156 Posts

November 22nd, 2016 08:00

ETA 484547: NetWorker, Avamar: VMware Snapshot operation may power off NetWorker or Avamar virtual machine clients after VMware Image Backup with Changed Block Tracking (CBT) enabled.

https://support.emc.com/kb/484547

156 Posts

November 22nd, 2016 11:00

If you are not using VBA then what you are using?

November 22nd, 2016 11:00

We have 7 Virtual Client Licenses for 7 physical servers and we are using VADP process via Virtual proxies with hot add... to Data Domain.

96 Posts

November 22nd, 2016 13:00

Please check the vmware.log file for an affected virtual machine to see what is the cause of the power-off signal. Maybe it could be related to locked files.

No Events found!

Top