Quantcast
Channel: All Data Protection posts
Viewing all articles
Browse latest Browse all 3468

Re: SC 4.0 - Unable to create resource groups

$
0
0

The reasons when you can run into issue "Some entities are not SnapCenter compatible." are listed below:

 

  • VMDKs are on unsupported storage; for example, on an ONTAP system running in 7-Mode or on a non-ONTAP device.
  • A datastore is on NetApp storage running Clustered Data ONTAP 8.2.1 or earlier
  • SnapCenter 3.0 supports ONTAP 8.2.2 and later. SnapCenter versions 3.0.1 and 4.0 support ONTAP 8.3.1 and later. The SnapCenter Plug-in for VMware vSphere does not perform compatibility checks for all ONTAP versions; only for ONTAP versions 8.2.1 and earlier. Therefore, always see the Interoprability Matrix Tool (IMT) for the latest information about SnapCenter support.
  • A shared PCI device is attached to a VM.
  • A preferred IP is not configured in SnapCenter.
  • You have not added the SVM management IP to SnapCenter.
  • The SVM is down.

Can you check if you are running into any of these?

 

The corrective actions are pretty obvious but nevertheless listing it here:

 

  • Make sure the SVM is running.
  • Make sure that the storage system on which the VMs are located have been added to the SnapCenter Plug-in for VMware vSphere inventory.
  • Make sure the SVM is added to SnapCenter. Use the Add storage system option on the SnapCenter GUI or on the VMware vSphere web client GUI.
  • If there are spanning VMs that have VMDKs on both NetApp and non-NetApp datastores, then move the VMDKs to NetApp datastores.

Viewing all articles
Browse latest Browse all 3468

Trending Articles