Good Morning,
I'm trying to figure out why all of our VMs show up in one datastore group.
We're running VCServer 5.5 with SRM 5.5, and we have identical Nimble Arrays at both sites with array firmware 1.4.11 and the Nimble SRA 2.1.0.
We have about 70 VMs. Each VM we have is in it's own datastore on the Nimble - however we have one large volume that is used for VMWare snapshots and another volume that we use for Windows Paging files. We have three volume collections / consistency groups on the Nimble side - two that take simple storage level snaps and a third that takes VMWare snaps before snapping the storage for replication. I would expect all three of these volume collections to show up as separate datastore groups, however SRM is lumping them together. This morning I created another volume and used Storage vMotion to move the VMDKs that have Windows Paging Files for one of our consistency groups to it's own separate datastore for just those few VMs. Afterward, I asked SRM to recompute datastore groups and they still show up as one large datastore group.
Will the location of the VMWare swap files also combine consistency groups into one large datastore? We try and move the swap files off to other, non-replicated datastores to keep replication traffic down to a minimum.
At this point, having one large protection group isn't causing a major issue, but it might down the road as we haved deemed that some VMs don't need to be protected by SRM, however those VMs are eating up SRM licenses by being part of those datastore groups.