Symantec Backup Exec Management Plug-in for VMware® Virtual Machine Validator Best Practices


Best practices for Virtual Machine Validator feature

Best practices include tips and recommendations to help you use the Virtual Machine Validator feature more effectively. For more information about the Virtual Machine Validator feature, see the Symantec Backup Management Plug-in for VMware User’s Guide.

The following best practices are for using the Virtual Machine Validator feature:

  • When you validate virtual machines that are dependent on each other, ensure that you select those backup sets for the virtual machines that were created at the same time or close in time.
  • If you validate virtual machines from different subnets at the same, ensure that the validation platform is in a different subnet.
  • Use system logon account to connect to the media from the vSphere Client.
  • When connecting to the media server from the plug-in specify the fully qualified domain name. Connecting using the NetBIOS name may fail in some cases.
  • If the validation settings are correct and you choose to cancel a job, you are prompted to save the validation settings. Click “yes” to save the settings, which are used for the next validation job for the virtual machine.
  • Virtual Machine Validator requires at least one successful GRT-enabled full backup that was created within the last three months.
  • To validate a 64-bit virtual machine on a 32-bit validation platform, you must enable Virtualization Technology (VT) on the validation platform. You can enable VT from the BIOS settings.
  • When validation jobs are running, do not interrupt the validation tasks running on the VMware Workstation. Doing so might cause the validation job to fail.
  • Only the virtual machines that are supported by VMware Workstation can be validated using the Virtual Machine Validator.
  • While validating deduplication-based backups, the default virtual machine power-on timeout is set to 30 minutes. However, if the backups are stored on a remote computer, you must adjust the timeout settings of “Virtual Machine Power on targeted to deduplication storage folders” as per your network.
  • It is not recommended to use network paths, mapped drives, and removable drives to store the temporary backup validation files and reports.
  • Do not validate same backup set at the same time from different validation platforms.
  • By default, if you want the virtual machines selected for validation to be listed in a specific order, you must configure a vApp and add the virtual machines to the vApp in the required order. If you do not do so, you can still change the order of the virtual machines in the “Add scripts for the selected virtual machines” panel of the Validation wizard.
  • If a virtual machine fails to boot, you can investigate the problem by looking at the VMware logs that are copied in the reports directory by the Virtual Machine Validator feature.
    If you face any issues while investigating the problem, report the issue to Symantec Support. While reporting an issue, please provide the VMware logs to Symantec Support.
  • Make sure that the media server NetBIOS name is reachable using the ping tool.
  • If UAC (User Account Control) is enabled on the validation platform, you must run the vSphere Client using the “Windows Run As Administrator” option.
  • If you have limited system resources, we recommend you to use “Validate one virtual machine at a time without setting up a private network” option for validation.
  • You must manually delete the older unwanted reports from validation reports directory to free up disk space.
  • Virtual Machine Validator uses temporary storage folders to create the temporary validation files and validation reports.  Ensure that the volume has enough space to hold the temporary validation files and reports. It is recommended to have more than 10 GB of free space if you want to validate multiple virtual machines at a time.
  • While upgrading the plug-in, if you want to retain the Virtual Machine Validator settings, you must copy the “VMValidatorCatalog.xml” file from ‘\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Symantec Backup Exec Management Plug-in for VMware’ directory and store it in a safe location.
    After the upgrade is complete, replace the new “VMValidatorCatalog.xml” file with the one that you have stored.
  • Make sure that your virtual machines have VMware tools installed before backing them up. It is a pre-requisite for the Virtual Machine Validator feature to work.
  • While validating multiple virtual machines by setting up a private network, make sure that the VMware Workstation has enough free custom NICs.  The number of custom NICs that are required depends on the number of subnets you have in the virtual machines that are selected for validation. You can find the list of free custom NICs on the VMware Workstation by accessing Edit->Virtual Network Editor.
  • If you are validating multiple virtual machines and their backup sets reside on different backup-to-disk folders residing on separate media servers, select a logon account that can be used to access all the backup sets. Ensure that the logon account you select has administrative privileges on all the media servers that contain the backup-to-disk folders.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)