Discussion: how are you protecting your data?

[#1]

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

[#2]

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.

[#5]

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

[marktheblue45]

I thought so. Weird thing with the exchange mail stores and logs. Snapshot produces 5 snaps not one per volume. SQL DB and logs behave as I'd expect. One snap operation per volume = 0ne snap on Nimble.  

Not quite there yet..

[marktheblue45]

I have discovered the following:-

Vol collection contains 6 DB and 6 log volumes and the collection show 6 snapshots corresponding the the Commvault Job ID. Unfortunately the individual volumes show 6 snaps each. Therefore 12 volumes with 6 snapshots = 72 snaps. I'm missing something or else there's a bug/limitation here?

Regards,

               Mark.

[#8]

Mark,

In the lab I configured two Exchange 2010 databases to be protected with a single Simpana subclient:

- 2 Exchange database volumes

- 2 Exchange log volumes

- All volumes (4) in the same volume collection

- 1 Simpana subclient (Exchange Database) with the contents of both databases (Microsoft Information Store\DB1 & Microsoft Information Store\DB2) included

I see one volume collection snapshot corresponding to the single Simpana job ID, as well as a single snapshot for each volume in the collection with the same Simpana job ID.

In your use case are you protecting all 6 Exchange databases with a single subclient or multiple subclients?

Thanks, Bill

[marktheblue45]

Alas multiple so I've created 6 vol collections. Each collection contains DB and corresponding log volume inline with the subclient.

We did multiple subclients to have multiple streams on the go and it's not such a chore because exchange is the only DB snap/backup configured in this way. SQL is generally straightforward i.e. A User Database and corresponding log volume pair.

Delighted so far just a shame that one can't purge out the 3 hourly (snap every 3 hours from 09:00 until 18:00) every 4 snaps like you can with Nimblestorage own snaps.

I'm sure this might become an option in the longer term because our 2 exchange server total 11 DB and log volume pairs. Commvault keeps snaps for 7 days so that's 4 * 7=28 for the 3 hourly multiplied by 22. 616 snaps plus 7 daily multiplied by 22.  154 snaps. Total snaps 770!

Good Fun,

                 Mark.

[marktheblue45]

We have 2 exchange servers one with six mail stores and the othe with 5. Could consolidate into 2 subclients but not an issue now I've done the new volume collections

[marktheblue45]

Thanks to everyone for their tips and suggestions. Collectively we got there in the end.

Fabulous forum