Veritas Storage Foundation and High Availability Solutions Release Notes

128About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaroundDelete all of the clones that were created when the servers crashed or wererebooted, and redo the wizard operation.Error message does not always display when you select an incorrect clusterto clone (2372713)In cases where multiple FileStore clusters are registered with the same VirtualCenter, the Symantec Quick Clone Virtual Machine Wizard might not provide awarning that you selected an incorrect cluster to clone a golden image. This couldhappen if all of the FileStore clusters are exporting the same file system path,such as /mnt. Instead of an advanced warning that you selected the wrong cluster,you instead see an error on the final page of the wizard when the wizard attemptsto clone the disks (vmdks) of the golden image. The error that displays is similarto the following example:/mnt/goldvm/goldvm.vmdk no such file or directory...WorkaroundThere is no workaround for this issue.Cloning issue in a Japanese environment (2623471)You might be unable to clone with Guest OS Customization or VMware Viewintegration. While using the FileSnap wizard, options may be missing or in anerror state.WorkaroundThe workaround involves temporarily running the vCenter Server in the Englishlocale.To resolve this issue1 From the vCenter Server, stop the following services using the Task Manageror services.msc:VMware VCMDSVMware VirtualCenter ServerVMware VirtualCenter Management WebservicesVMware vCenter Update Manager Services2 Rename the following language directories ja to ja-x:C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jaC:\Program Files\VMware\Infrastructure\VirtualCenter Server\locale\jaC:\Program Files\VMware\Infrastructure\VirtualCenter Server\imgres\ja