There are situations when the SVM detected under the Cluster NAS client is incorrectly shown or for some reason needs a refresh.
Solution turned out to be very simple in that case:
1. Remove the SVM [That failed Snap operation] from the Source Metro Cluster.
2. Detect and add it again.
I no longer work for CommVault, but I am still trying to remember this case, rather scratching my head, but I am guessing the logic was, after the switch over from Destination MC to Source MC, the destination SVM with 'mc' as suffix, becomes active as expected, and I suppose it should now be serving Data to Clients from the DC1. The idea behind switching over is to simulate the real life fail-over scenario.
So, ideally SVM_DC2-mc should now be 'ACTIVE' under the Source MC NAS Cluster Client, but b'cos of the switch over mechanism, which is purely Netapp process, there are very good chance that the 'switch' over process did not register with CommVault DB. It may perhaps needs a refresh.
Therefore, a refresh is what I call a 'SVM Remove & Detect' Process on the CommVault side.
Steps:
1. Go to the Source Metro Cluster NAS Cluster Client properties | SVM Tab | and make a note of the SVM that you would like to remove in order to refresh it.
2. Now, go to the specific SVM NAS Client properties | and uncheck the box and click ok.
3. To confirm, go back to the Source Metro Cluster NAS client properties | under SVM Tab, now you should see the SVM missing.
4. Finally, just perform the detect and re-add it.
Attempt another IntelliSnap operation, wish you good luck! If no luck, get in touch with CommVault Support for a CVLT.NET session ;)
No comments:
Post a Comment