Recently performed a vCenter Server upgrade from 5.1 to 6.0U2.
The Netapp VSC vCenter plugin was also being used for backups using the plugin through the VIC.
The greenfield installation went without a hitch for vCenter Server 6 environment and hosts were migrated over.
After I upgraded the hosts to ESXi 6.0U2 I had to perform the upgrade of Netapp VSC plugin.
The plugin upgrade process was pretty straight forward with moving the plugin to a new server and pointing to new vCenter server.
After VSC plugin upgrade I ran into a strange issue where ESXi hosts kept randomly disappearing from the vCenter Web client and nothing else getting affected.
Restarted vCenter server and tested with different browsers with no affect.
Disabled the plugin and restarted browser which resolved the issue.
Uninstalled 6.2 and installed 6.1 which seems to have better experience and hosts do no disappear as frequently.
Netapp community has a couple of blog posts related to the issue with no real positive response from Netapp.
Open a case with Netapp and was provide BUG ID 986313 related to issue with no estimate on fix.
The bug can be view on Netapp support -> Tools -> Bug Tools.
Workaround at this time seems to be downgrading or install VSC 6.0 which has the least amount of problems.
Been running into an interesting scenario with a backup process which I hope will help someone else.
I have an exchange backup of DAG with intellisnap which creates a snapshot of each of the exchange database volume on Netapp. The snapshot is then mounted and copied via SAN transport on the backend fiber connection to the storage library on commvault agent.
This has a storage policy to perform a backup copy of the latest snap via SAN transport weekly on Thursdays.
With commvault I find that sometimes the snapshots are not copied to the commvault storage library, without any type of error.
In viewing the jobs for the primary copy of snaphost i just shows a status of “to be copied”, but no failure.
This however causes problems since if you do not pay attention you can sit with weeks of uncopied backup copies of the snapshots, and if you snapshots are set for retention of a few days then you loose all those copies and have to mark them bad! (not good!)
Have not find a way to resolve this, even with the help of Commvault support, but here are a few tips to make sure you are at least inform in more detail regarding this process:
- A good indication that the backup copy is not taking place is when the snapshots on netapp volume is not being deleted.
- Also make sure you setup a very detailed report for the day after the snapshot copy was to take place and make sure the backup copy detailed information is also included in this report.
If however you do run into this problem, and your snapshots have already been rotated on the volumes on storage you would have to perform the following tasks to continue the backup copy process.
(I recommend contacting Commvault support if you are not familiar with your storage, snapshots and intellisnap, the steps below are provided for use at your own risk, you will loose backup data with these steps)
- Verify you oldest snapshot date which are still on volumes for databases
- Select storage policy
- Right click and primary copy and select view -> jobs
- this will list all the backup copies and show the ones with status “to be copied”.
- Select all jobs up to before the date you have for snapshots on Netapp volume.
- Right click and select “Mark job bad” (i know not my favorite step)
- Right click on the storage policy again and select All Tasks -> Run Backup copy.
- This will start the backup copy of your latest snapshot which resides on backup storage volume
Another solution is to manually add snapshots taken during the week to be added for backup copies.
- Right click on the storage policy again and select View -> Jobs
- Right click on the snap you want to create backup copy off.
- Select “Pick for backup copy”
- As a note, you cannot create a backup copy of snapshot which is older than your latest backup copy. so make sure you backup your oldest snapshot first .
Anybody else running into the same problem would love to hear from you.