Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

10413

July 1st, 2015 00:00

Hyper-V BAckup failure (Saveset Problem)

Hi Community,

I get a strange problem this morning:

We are backing up an Hyper-V environment based on Windows 2012 with NMM 8.2.0.1 and Networker 8.1.2.6.

The VM file are located on a SMB3 Share on a file cluster.

If I backup one VM with savesset APPLICATIONS:\Microsoft Hyper-V\[Vm Name], everything is fine.

But if I try to backup the all Hyper-v environment with saveset APPLICATIONS:\Microsoft Hyper-V\,

backup is failing with the following message in NMM.log (see please attachment).

Any Idea?

Thanks

Greg


1 Attachment

2 Intern

 • 

217 Posts

July 16th, 2015 06:00

Hi,

With the help from EMC support, we have:

- Trying to install this KB: https://support.emc.com/kb/186499

- re-register the dll for vss writers Re: Backup Error Using NMM 2.3 Build 81

  (Not sure this step is realy needed)

- Updating NMM to latest version : https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA17000000013lz

- Correcting some errors we found in the HYPER-V-VMMS Logs

Now everything works fine. Thanks Carlos for your help.

Have a nice day

Greg

2 Intern

 • 

217 Posts

July 1st, 2015 01:00

And were did I find the HVVMMS log?

Thanks

1.7K Posts

July 1st, 2015 01:00

Hi Gregoire_Perrenoud


You mention this is a cluster environment, are you backing up using the physical node name or the virtual cluster name?


Please note:


Backups over SMB 3.0

NMM 8.2 supports Hyper-V VMs residing on Widows Server 2012 and 2012 R2 SMB 3.0. You back up stand-alone servers and non-CSV failover clusters over SMB the same way you back up local VMs. To back up CSVs over SMB, NMM does not use federated backup architecture. Instead, you configure a backup for each server like a stand-alone Hyper-V server.


Also, have you configured the additional permissions required for Hyper-V backups over SMB 3?

SMB3 permissions.jpg

Thank you,

Carlos

1.7K Posts

July 1st, 2015 01:00

Also, have you checked the Application and HVVMMS event logs?

Thank you,

Carlos

2 Intern

 • 

217 Posts

July 1st, 2015 01:00

Hi Carlos,

we are backing up each node separately.

And as we are able to backing up a single VM, permission looks to be OK. Don't you think so?

Thanks for your help

Greg

1.7K Posts

July 1st, 2015 03:00

Could be that permissions are OK, but worth to double-check.

As for the logs, you will find them here:

Event Viewer > Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS > Admin

Also please ensure that IC services (Integration Components) are installed in all VM's, with same version as Hyper-V hosts.

Ensure that the "backup snapshot" option is enabled on the VM's under the IC services options in the VM configuration.

Also check the VSS writers on the VM's themselves.

Thank you,

Carlos

2 Intern

 • 

217 Posts

July 1st, 2015 04:00

Nothing found in VVMMS log corresponding to the time of backup.

Integration ComponentsOK

backup snapshot" option is enabled OK

VSS writers . OK

For the permission, how can i know which user is used (until now nsrexecd run always with LOCAL/system account). Should we change that? If yes, how?

Thanks again

Greg

2 Intern

 • 

217 Posts

July 1st, 2015 04:00

And that's what we found as error message on the savegroup.

Hope it will help.

It's look like nsrsnap_vss_sve was not able to find file he needs on the Scale Out File Cluster.

Greg

1 Attachment

2 Intern

 • 

217 Posts

July 7th, 2015 23:00

Hi community,

I still try to make these Backup working without success. The error happens as NEtworker try to mount the file system in the C:\Program File\EMC Networker\nsr\tmp folder of the Hyper-V host. At this time, i always get these two errors:

-    info PS: (CMTDXlator::GetCorrectPath) Path component HYPERV1$@{65D03565-A287-4B2B-A8FD-3845F45A750B}$      not on PIT path 'C:\rtrs-data01.media.int874843747\'.

-    critical ERROR : Failed to verify file path

     (\\rtrs-datasofs\hyperv1$\HyperV\Snapshots\8878170F-8258-42B0-BDA7-C160F3A8E504\) for the writer "Microsoft      Hyper-V VSS Writer". Files(*) under the path can not be backed up. Possible reason could be a missing file or folder      in the specified path.

-    critical NMM .. FAILED to get correct file path for

     \\rtrs-datasofs\hyperv1$\HyperV\Snapshots\8878170F-8258-42B0-BDA7-C160F3A8E504\, filespec='*', Writer Name :      Microsoft Hyper-V VSS Writer.

Any Idea? We are running these Backup with a domain admin account, so special SMB3 permission seem s to be ok.

Thanks for your help

Greg

1.7K Posts

July 8th, 2015 00:00

Hi Gregoire,

I think this could be related to orphaned snapshots, or live snapshots, so please check the VM and see if there is any snapshot. If there is, check if it can be deleted and delete it.

If you don't see any snapshot, could be that there was an orphaned snapshot left behind, so in that case the best way usually is to move the VM/CSM to another node to have the VM consistent.

Thank you,

Carlos

2 Intern

 • 

217 Posts

July 8th, 2015 06:00

Hi Carlos,

it's look like there is no snapshot. As i try to backup the all Hyper-V environment, I'm not able to move the VM to another host. During Backup, I see that the snapshot is being mounted on the Hyper-V host, and then the issue happens and the mount disappear from the host.

I get these error now in my savgrp log:

APPLICATIONS:\Microsoft Hyper-V: Backup of [APPLICATIONS:\Microsoft Hyper-V] failed

get correct file path for \\rtrs-datasofs\hyperv2$\HyperV\Snapshots\37BE891C-7BE2-466C-9736-09BB3C9452F2\, filespec='*', Writer Name : Microsoft Hyper-V VSS Writer.

48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessSelectedComponent)  FAILED

48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessWriterSavesetComponents)  FAILED

48462:nsrsnap_vss_save:PS: (CMTDXlator::ProcessWriterSavesets)  FAILED

48462:nsrsnap_vss_save:PS: (CMTDXlator::PrepareSnapshotObjects)  FAILED

Could that helping us?

Thanks for your help

Cheers

Greg

2 Intern

 • 

217 Posts

July 13th, 2015 01:00

Hi community,

Any further help about this subject will be greatly appreciated.

I already have opened an SR by EMC. Without succes until now.

Thanks

Greg

No Events found!

Top