Subscribe
Accepted Solution

OnCommand 5.0 - Can you import SnapVaults of SMVI-created backups and use with Host Package 1.1?

Hi All,

IHAC that formerly used SMVI to take snapshots of their VMware environment.  They then used SV-SMVI to SnapVault the SMVI-created snapshots to a secondary location. Now, the customer would like to switch to using OnCommand 5.0 and the Host Package 1.1 to take these VMware snapshots and SnapVault them.   However, they want to import the existing SnapVault relationships into Protection Manager and use them with the Host Package.  That way, they can avoid re-baselining the relationships.

QUESTION:  Is this example of importing SV relationships supported with OnCommand 5.0  & Host Package 1.1? 

I suspect it is not supported as the Host Package likely uses named snapshots and passes that information to the SnapVault relationship that Protection Manager would create.  If you import an existing SV relationship, I suspect the names snapshot functionality wouldn't work as PM didn't create that relationship.  However, I have no means to test this at the moment.

Re: OnCommand 5.0 - Can you import SnapVaults of SMVI-created backups and use with Host Package 1.1?

Importing relationships into a virtual dataset is not supported.

https://communities.netapp.com/message/77015#77015

Re: OnCommand 5.0 - Can you import SnapVaults of SMVI-created backups and use with Host Package 1.1?

Hi Reid,

     The reason why one is not able to import an existing external SV relationship into a VMware dataset is because, in a VM dataset only virtual object( like VM, datastore or datacenter) can be added to the primary of the dataset.

When you try to import as a external relationship which are basically volume or qtree there is no VM to storage mapping which give what vm or datastore is hosted on this volume.

Also as you said, VMdataset are app consistent which does named snapshot transfer, but thats not the reason for not supporting import of a relationship. The named snapshot are created by HS by taking vmware snapshot followed by netapp snapshots and registering the same with PM. Which can very well be done with named snapshot as well. Its basically vm to storage mapping and QA qualification of the same that makes it  unsupported.

Regards

adai