Discussion: how are you protecting your data?

[#1]

It isn't clear (to me anyway) where the process is failing. We should be taking snapshots at the volume collection level.

If you look at the Simpana subclient properties and select the IntelliSnap tab please verify that the "Nimble CS-Series Snap and Replicate" snap engine is selected.

On the Nimble side of the equation please look at the volume collection "schedules" tab and verify that the "advanced" "Snapshot triggered by Commvault" option is selected.

Also verify that the "replicate to" portion of the protection schedule has been completed.

[#2]

If everything is configured correctly the next thing I'd check would be the CVMA & VssSwProvider logs.

The CVMA essentially prepares to take a volume collection snapshot after identifying the tart volumes. You should see the individual volumes being called out as well as the volume collection itself:

7124  18c4 07/08 10:00:28 36 CVSnapEngineNimble::cvso_prepareDevices The snapshot name [SP_2_36_1404838827] will be used for the device [\\.\PhysicalDrive1] 

7124  18c4 07/08 10:00:28 36 CreateAndUpdateSnapMetadata: Setting Metadata [10.18.128.80|0a754fa29e4f0baf6c9ce900656b3266|SP_2_36_1404838827|iqn.2007-11.com.nimblestorage:dpl-tmsandbox-sql2008r2-dbvol-v19a495ee7f96fe8b.0000003d.66326b65|dpl-sql-collection] for device [\\.\PhysicalDrive1]

7124  18c4 07/08 10:00:28 36 CVSnapEngineNimble::cvso_prepareDevices The snapshot name [SP_2_36_1404838827] will be used for the device [\\.\PhysicalDrive2] 

7124  18c4 07/08 10:00:28 36 CreateAndUpdateSnapMetadata: Setting Metadata [10.18.128.80|39ed1ec223d3a6d56c9ce900656b3266|SP_2_36_1404838827|iqn.2007-11.com.nimblestorage:dpl-tmsandbox-sql2008r2-logvol-v19a495ee7f96fe8b.0000003e.66326b65|dpl-sql-collection] for device [\\.\PhysicalDrive2]

7124  18c4 07/08 10:00:28 36 [0:]: Success 

7124  18c4 07/08 10:00:28 36 CVMASnapHandler::prepareVolumeSnaps() - Request for prepareVolumeSnaps Succeeded. Status [0].

Subsequent VssSwProvider logs should indicate:

7228  1928 07/08 10:00:29 36  START Nimble Operation: SnapVolColl 

7228  1928 07/08 10:00:29 36  END Nimble Operation: SnapVolColl Status: SUCCESS

[marktheblue45]

Thanks Bill for your feedback. The system I'm testing with has two volumes, an SQL DB volume and an SQL Log volume. These volumes are in guest connected iSCSI. In the Nimble web GUI how do I set the synchronisation? None or Microsoft VSS (SQL). CV is creating the snaps on the volumes but the volume collection containing these volumes is blank I.e. No snaps. Currently the synchronisation is set to NONE on the Nimble GUI since I assume the CV agent on the VM needs to be left to handle this. I suspect I need to use the VSS synchronisation option within the Nimble GUI?

I do appreciate that this long awaited replication feature is new and the 2.1.4 NOS is a release candidate. I will reach out to Nimble Support again now I have confirmed everything is the same version as Glenn Stewarts scenario. I'm attempting to have our environment backed up to NAS (Coraid) then to tape using Commvault (this is already working beautifully) but want to have app consistent replication using just Commvault triggered backups\snaps to streamline the scheduling and avoid overlapping conflicting snaps as the number of protected systems grow.

Kind Regards,

                       Mark.

[marktheblue45]

it's working !!!!!!!!

Sent some screenshots to someone at Nimble who will be looking to create a KB relating to this.

When the array was added to Comserve it was entered in the correct manner for pre NOS v 2.1.x that is the array name was populated with the iSCSI discovery IP rather than management IP of the array. In the properties of the protected sub clients I wanted to replicate I changed the available snap engines from "Nimble Storage CS-Series Snap" to "Nimble CS-Series snap and Replicate"

Cheers,

             Mark.  

Happy again

[rugby0134]

You rock Mark!  Thanks for figuring this one out for the Community!

[#6]

Mark,

Volume collection synchronization should be set to "none" because we're not using the Nimble VSS provider in this scenario. Instead, the Simpana VSS provider is coordinating everything.

Bill

[#7]

Mark,

Thanks for the clarifications. We've got a recently updated Field Integration Guide coming out that details the Simpana Array Management parameters when using Nimble OS 2.1.x or higher. We've also finalized a Nimble/Simpana Best Practices Guide where we cover a range of recommendations.

Bill

[marktheblue45]

Yes I have set it to none. 

[marktheblue45]

Hi Bill,

           CV has a retention of 7 days but on Nimble I have had to count the number of snaps made in 7 days and enter that value in "Number of snapshots to retain on the replica". Is this as you'd expect?

Regards,

              Mark.

[#10]

Mark,

Yes; if you're seeking to replicate and retain snapshots on the downstream Nimble array such that the number of retained snapshots equals that of the upstream partner you'll need to calculate that number and plug it in as you have.

Thanks, Bill