hamoud1

5 Posts

2215

May 22nd, 2016 10:00

NMM 8.2 + Hyper-V 2012 R2 Cluster Backup

Hi,

I tried to backup our HyperV 2012 R2 Cluster. It consists of two physical nodes actve-active. Client and NMM module installed on each physical node. And there are no CSV VMs.

When I start the group, I got the message

" This is a federated backup for Hyperv CSV".

"Non-CSV VMs, will be skipped from the backup operation".

Is there possibility to perform a federated backup of non CSV VMs ?

Networker Server : Linux RHEL 6.7, Networker 8.2.2

Thanks in advance

Regards

Responses(7)

gautamgp

226 Posts

0

May 23rd, 2016 01:00

How is the clustering configured then ? If the storage is local then you can add the physical servers as client in NetWorker and back them up as Standalone Servers. All VM's residing on the host will be backed up.

hamoud1

5 Posts

0

May 23rd, 2016 03:00

Hi Gautam,

Thanks for your reply.

The storage is not local. It's provided from SAN. But it's not configured as CSV.

LUN is allocated to each node of the cluster. But it's only accessible by one node, as there is a persistent reservation when it's used, so other nodes can't access to it.

In case of switch of VM from Node1 to Node2, the VM is offline on Node1, Persistent reservation on the disk is released from node1, a persistent reservation on the disk is made by node2, and VM started on node2.

Thanks in advance

Regards

gautamgp

226 Posts

1

May 23rd, 2016 21:00

In that case you can configure the Physical Nodes as Individual Clients and backup all the VM's on that host. Even if the VM fails over it will still be covered by the Other Node.

hamoud1

5 Posts

0

May 24th, 2016 12:00

Hi,

In this case, if I am not wrong, I have to list all VMs hosted by each node and provide them as save sets.

When a new VM is created, or a VM is deleted we will have to change list of save sets on the node.

Our goal is to make an automatic backup of all VMs hosted by the cluster, without take in place a process of asking for add the backup of a new VM to the backup team.

I ll make a test tomorrow and update you.

Thanks in advance

Regards

gautamgp

226 Posts

1

May 24th, 2016 21:00

Not Really, you can use the following "APPLICATIONS:\Microsoft Hyper-V\" as the saveset and that should backup all the VM's residing on the host. Also,

hamoud1

5 Posts

0

May 26th, 2016 10:00

Hi,

I configured a node of the cluster as a client, with save set APPLICATIONS:\Microsoft Hyper-V\ .

The operation was failed. Below log of the job.

If you have any idea.

Thanks in advance

92347:nsrsnap:***************** Snapshot Management operation has started, logging to "C:\Program Files\EMC NetWorker\nsr\logs\nwsnap.raw" *****************05/26/16 19:04:05.500761 [nsr/save/nsrsnap.c 609] Calling nsrrm_host

05/26/16 19:04:05.574767 [nsr/save/nsrsnap.c 884] Calling get_pool_name..

52051:nsrsnap:Printing savecmd=nsrsnap_vss_save.exe after parsing

05/26/16 19:04:06.209806 [nsr/save/nsrsnap.c 1691] Calling snap_wait..

APPLICATIONS:\Microsoft Hyper-V

05/26/16 19:04:26.211940 [nsr/save/nsrsnap.c 1712] Calling parse_fs_logs_and_prefix..

107092:nsrsnap_vss_save:Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsnap_vss_save.exe: Original file name: nsrsnap_vss_save.exe Version: 8.2.2.2.946 Comments: Supporting Microsoft Volume Shadow Copy Service

102345:nsrsnap_vss_save:Data mover host name not specified. Assuming local host: emcu814ph1.emea.cib

102338:nsrsnap_vss_save:Backup is level FULL. Set GLR compatibility to YES.

Microsoft DiskPart version 6.3.9600

On computer: EMCU814PH1

Automatic mounting of new volumes enabled.

47363:nsrsnap_vss_save: nsrpsd service is running on EMCU814PH1.emea.cib.

82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Hyper-V is valid.

Invalid host name - Volume{6303bef2-6aa9-4883-a2c9-6454a93a24b6}.

99496:nsrsnap_vss_save: Invalid host name - Volume{6303bef2-6aa9-4883-a2c9-6454a93a24b6}.

Invalid host name - Volume{7fecfbeb-f24e-4e25-9160-768e34d9a4bf}.

99496:nsrsnap_vss_save: Invalid host name - Volume{7fecfbeb-f24e-4e25-9160-768e34d9a4bf}.

Invalid host name - Volume{7d61ed90-8915-4009-9241-af8c392e01fd}.

99496:nsrsnap_vss_save: Invalid host name - Volume{7d61ed90-8915-4009-9241-af8c392e01fd}.

Invalid host name - Volume{446d621c-d78c-41c7-8f1e-89618370dc6d}.

99496:nsrsnap_vss_save: Invalid host name - Volume{446d621c-d78c-41c7-8f1e-89618370dc6d}.

Invalid host name - Volume{a125c8c0-8d7c-4738-ac50-24dda50b8903}.

99496:nsrsnap_vss_save: Invalid host name - Volume{a125c8c0-8d7c-4738-ac50-24dda50b8903}.

63333:nsrsnap_vss_save:NMM .. process replica not attemped. Preparation step failed.

37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation.

.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

102333 1464282263 3 0 0 11096 2808 0 emcu814ph1.emea.cib nsrsnap_vss_save NSR error 21 Exiting with failure. 0

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

hamoud1

5 Posts

0

May 31st, 2016 03:00

Hi all,

Still fighting with backup of HyperV Cluster. As we don't use any CSV Lun, I configured nodes as stand alone, and lauch a backup for each node. Without succes. I got errors with Invalid hostname - Volume{ ..... as shown below. I have no idea in wich way to investigate.