Subscribe

VSC5.0 ignores datacenter context when adding backup job

We have been naming our volumes based on function and backup schedule.  Recently, we adding a new FAS and vSphere cluster at another location, prompting the creation of a new DC in vSphere and the duplication of datastore names.

 

DC1 has datastores such as LinuxVM4Hour30Day, WinVM1Day7Day, etc

DC2 also has datastore LinuxVM4Hour30Day

 

When I try to create a backup job for DC2\LinuxVM4Hour30Day, the wizard shows me the spanned entities that exist in DC1\LinuxVM4Hour30Day

 

I'm wondering if there's a fix for this beyond having to rename/remount datastores to include DC reference or if I'm missing something?