https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC5-0-ignores-datacenter-context-when-adding-backup-job/m-p/104780#M8182 <P>We have been naming our volumes based on function and backup schedule. &nbsp;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.</P><P>&nbsp;</P><P>DC1 has datastores such as LinuxVM4Hour30Day, WinVM1Day7Day, etc</P><P>DC2 also has datastore LinuxVM4Hour30Day</P><P>&nbsp;</P><P>When I try to create a backup job for DC2\LinuxVM4Hour30Day, the wizard shows me the spanned entities that exist in DC1\LinuxVM4Hour30Day</P><P>&nbsp;</P><P>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?</P> Thu, 05 Jun 2025 04:20:57 GMT djaquays0 2025-06-05T04:20:57Z https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC5-0-ignores-datacenter-context-when-adding-backup-job/m-p/104780#M8182 <P>We have been naming our volumes based on function and backup schedule. &nbsp;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.</P><P>&nbsp;</P><P>DC1 has datastores such as LinuxVM4Hour30Day, WinVM1Day7Day, etc</P><P>DC2 also has datastore LinuxVM4Hour30Day</P><P>&nbsp;</P><P>When I try to create a backup job for DC2\LinuxVM4Hour30Day, the wizard shows me the spanned entities that exist in DC1\LinuxVM4Hour30Day</P><P>&nbsp;</P><P>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?</P> Thu, 05 Jun 2025 04:20:57 GMT https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC5-0-ignores-datacenter-context-when-adding-backup-job/m-p/104780#M8182 djaquays0 2025-06-05T04:20:57Z