Hello All,
A few weeks ago, I was working on a migration for VMware and utilizing Storage vMotion (VMFS FC LUN to same).
At the time, VSC 2.1.2 was installed. vCenter is version 5 (had upgraded from 4.1 a couple of months prior although there were no actual ESX migrations to 5).
My plan was to use the VSC to provision all of the datastores, and it worked incredibly well, except for on ONE controller out of six. One of the nodes in an HA pair (3210) was unable to utilize the provisioning and cloning portion to create a new datastore, so I did it manually (created volumes & LUNs, created igroup, mapped to LUNs, rescanned storage adapters, etc...). The LUNs came in perfectly fine and storage vMotion migrations took place without any errors.
My main issue now is that in using the VSC for run fully quiesced backup jobs of the VM's on the LUNs, we can only see the two LUNs that were created from within the VSC. The other two LUNs that were created manually cannot be backed up via the VSC.
Can the VSC only see datastores that you provisioned using the VSC plug-in or should it see all datastores no matter what? It seems to be able to see some NFS datastores that are part of another cluster, although they are not in question as being part of this specific backup job.
We took an outage this past weekend at the client during a maintenance window and I thought that perhaps removing the datastores that had been created manually and then mounting them via the VSC would resolve the issue, however the VSC did not recognize them as valid datastores.
Looking for some assistance on this matter to make sure all of the datastores in question are being backed up in the same VSC backup job.
Thanks so much in advance!
