2012-02-15 01:39 AM
I've recently upgraded to OnCommand 5.0 and was previously using the OSSV plugin for VMWare to backup my VMs to a FAS3160 system. I've been playing around with the OnCommand Host Plugin and have installed it on my vCentre server, have managed to create the datasets and apply the protection policy, but I cannot seem to add and VMs to the dataset (attached screenshot shows the error message)
I'm wondering that the error could be due to my VMWare datastores not being on NetApp storage as they are on EMC.
Any guidance would be much appreciated.
2012-02-15 08:35 PM
Please check you had followed the below steps.
1. Go to Host Service Page and click on "edit". Select the NetApp storage systems and Vfilers(which are holding the datastore)
2. This creates a Job and check whether the Job is sucessful
3. Now go to server Tab and select the VM or datastore. Check for the storage system is listed in the right side
4. Now create a dataset and associate the VM or datastore and add "Local VMWare policy"
5. Attach storage service.
Everything should work fine.
2012-02-16 03:46 AM
This is exactly how I have it setup and am getting the error message that I have attaced in my original post. My concern is that my VMs are hosted on EMC Clariion LUNs.
Is it possible to perform remote backups to NetApp storage using OnCommand?
2012-02-16 03:50 AM
The oncommand host package supports backup of vm that are hosted only on NetApp Storage and not non-netapp. For that use the OSSV version 3.0.1 to backup vm's hosted on non netapp to be backedup to netapp.
2012-02-16 05:07 AM
OnCommand 5.0 Host Package does not work with OSSV. Backups with OSSV from non-NetApp storage work with OC5 the same way they did before - nothing changed.
- Install OSSV agent on ESX host (no Host Package required at all, just Core, and rember, OSSV for ESX is only supported up to ESX3.5)
- add ESX host to DFM database via Protection Manager Interface (the seperate NMC GUI)
- create a dataset within the NMC Protection Manager
- add your OSSV hosts/VMs to that dataset
- apply a protection policy
- assign a secondary ressource pool so that ProtMgr can provision the required secondary storage and initiate the SV relationships (btw. use a provisioning policy with "manual deduplication" for the secondary ressource pool so that dedup and SV interact correctly).
2012-02-16 05:24 AM
Thanks all. I'm looking to move of OSSV for ESX as we are on vSphere 4.1 now and the main fault with the OSSV agent is the lack of support for vMotion.
I'll look into the SyncSort alternative.