My suggestion would be:
- On the Nimble, created a Volume Collection that contains all your SP servers. (on web gui go to... Manage > Protection > Volume Collections)
-- Make sure that it's setup to synchronize to vCenter (or VSS - pending how your setup is)
-- Add in a regular schedule if you want. [Highly recommended]
-- Add in all the required SharePoint volumes.
- Once it's created click the 'Validate' button to make sure that everything will work properly. If it does then keep going, if not troubleshoot the errors.
- When your ready to do your backups, click the 'Take Snapshot Collection....' button and in a couple seconds you have a live backup.
If all goes south with your SP updates you can just click the 'Snapshots' tab and click the 'Clone' button and restore anything that is required.
Just a heads up though that I'm not running SP in our environment so if there are any SP guru's out there that can correct me please do.
This is the steps I use for all our other server updates.
Hope this helps,
Just remember, if you just click 'Take Snapshot Collection' rather than having the snapshots taken via scheduled Volume Collections you will NOT have 'application consistent' snapshots as VSS would not be invoked.
As stated in Wen Yu's article, VSS 101 and Design Considerations in VMware environment (Part II) | super sonic dog (S.S.D).
"ONLY a scheduled snapshot operation in a Volume Collection would invoke VSS quiescing, a manual snapshot that you take from vCenter Server Nimble plugin and/or Nimble UI would NOT trigger the VSS requestor to request for application quiescing"
I recommend reading all the articles on Wen's site, super sonic dog (S.S.D) | blog for anything technical, helped me understand the 'shadowy' technology that is VSS tremendously.