No snapshot backup relationships are found in the registered storage systems
•
1 gefällt mir•6,275 views
SMHV 2.0.1 snapmirror update fails
![SnapManager for HYPER-V 2.0.1 triggered Snapmirror update fails
NetApp Release 8.1.2 7-Mode
Error traced in SMHV jog log:
[14/02/2014 23:09:18, (24)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate Snapmirror
update result:
VolumeGuid: C:ClusterStorageVolume4 No Snapshot backup relationships are found in the
registered storage systems. Ensure that the designated virtual storage server is registered.
So, what is broken here?
No Snapshot backup relationships are found in the registered storage systems. It looks like
SMHV 2.0.1 upgrade has broken the snapmirror relationships.
Cause:
BUG: 775953: SnapManager for Hyper-V 2.0.1 does not update SnapMirror relationships.
http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=775953
Solution:
Upgrade to SMHV 2.0.1P1 patch.
ashwinwriter@gmail.com](https://image.slidesharecdn.com/nosnapshotbackuprelationshipsarefoundintheregisteredstoragesystems-140218040334-phpapp01/85/No-snapshot-backup-relationships-are-found-in-the-registered-storage-systems-1-320.jpg?cb=1392700079)
![Patch installation steps
You need a NetApp Support Account in order to download this patch.
IMPORTANT INFO: As per my experience - No downtime is required to accomplish this task.
No reboot is needed. During patch installation, SMHV services will be stopped and restarted.
Hence, you can schedule the patching before the next SMHV backup kicks off.
1. Download the patch from this link.
http://support.netapp.com/NOW/download/software/snapmanager_hyperv_win/2.0.
1P1/
2. Depending upon the processor/OS type, download the appropriate package.
3. Copy the SMHV2.0.1P1 to all the hosts in the HYPER-V clusters [Assuming all the nodes
have SMHV software installed].
4. One by one install the exe on all the nodes. [Start with the Host with least activity or
the one which has no VMs running; this is just to ensure that patch does not break
anything.]
a.
b.
c.
d.
Open the exe.
Follow the prompts, and leave the defaults.
Select modify.
Continue with the installation.
5. Repeat the same steps on all the hosts.
The next SMHV triggered snapmirror update should succeed. This can be traced in the SMHV
job log as shown below:
[17/02/2014 22:30:06, (47)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate
Snapmirror update result:
VolumeGuid: C:ClusterStorageVolume4 Initiated SnapMirror Update Successfully
VolumeGuid: C:ClusterStorageVolume3 Initiated SnapMirror Update Successfully
[17/02/2014 22:30:06, (47)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate - Exit
[17/02/2014 22:30:06, (47)] COMPLETED SnapMirror update for VOLUME: |
ashwinwriter@gmail.com](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Mehr von Ashwin Pawar
Mehr von Ashwin Pawar (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
No snapshot backup relationships are found in the registered storage systems
- 1. SnapManager for HYPER-V 2.0.1 triggered Snapmirror update fails NetApp Release 8.1.2 7-Mode Error traced in SMHV jog log: [14/02/2014 23:09:18, (24)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate Snapmirror update result: VolumeGuid: C:ClusterStorageVolume4 No Snapshot backup relationships are found in the registered storage systems. Ensure that the designated virtual storage server is registered. So, what is broken here? No Snapshot backup relationships are found in the registered storage systems. It looks like SMHV 2.0.1 upgrade has broken the snapmirror relationships. Cause: BUG: 775953: SnapManager for Hyper-V 2.0.1 does not update SnapMirror relationships. http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=775953 Solution: Upgrade to SMHV 2.0.1P1 patch. ashwinwriter@gmail.com
- 2. Patch installation steps You need a NetApp Support Account in order to download this patch. IMPORTANT INFO: As per my experience - No downtime is required to accomplish this task. No reboot is needed. During patch installation, SMHV services will be stopped and restarted. Hence, you can schedule the patching before the next SMHV backup kicks off. 1. Download the patch from this link. http://support.netapp.com/NOW/download/software/snapmanager_hyperv_win/2.0. 1P1/ 2. Depending upon the processor/OS type, download the appropriate package. 3. Copy the SMHV2.0.1P1 to all the hosts in the HYPER-V clusters [Assuming all the nodes have SMHV software installed]. 4. One by one install the exe on all the nodes. [Start with the Host with least activity or the one which has no VMs running; this is just to ensure that patch does not break anything.] a. b. c. d. Open the exe. Follow the prompts, and leave the defaults. Select modify. Continue with the installation. 5. Repeat the same steps on all the hosts. The next SMHV triggered snapmirror update should succeed. This can be traced in the SMHV job log as shown below: [17/02/2014 22:30:06, (47)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate Snapmirror update result: VolumeGuid: C:ClusterStorageVolume4 Initiated SnapMirror Update Successfully VolumeGuid: C:ClusterStorageVolume3 Initiated SnapMirror Update Successfully [17/02/2014 22:30:06, (47)] SnapMirrorUpdateHelper::InvokeSnapMirrorUpdate - Exit [17/02/2014 22:30:06, (47)] COMPLETED SnapMirror update for VOLUME: | ashwinwriter@gmail.com