Frequently Asked Questions (FAQs). .
If you used the IP address or fqdn within Backup Exec to create the backup jobs, then you must use the matching connection setting when logging into vSphere.
See the Monitoring View section of the Users Guide for more detail.Supported platforms include the following: - Backup Exec 2012 - VMware vCenter Server version.0.0 - VMware vSphere Client version.0 to.0 - VMware ESX version.0 to.0 - VMware Workstation.0 or later (required for Virtual Machine Validator feature).Problem, this plug-in is for use with Backup Exec 2012 with the Agent for VMware Virtual Infrastructure installed and configured to backup virtual machines. .View the backup status of the virtual machines.If you used the Hostname on its own (sometimes incorrectly described as the netbios name) when creating the backup jobs against the vCenter or ESX host, then you must connect to that vCenter or ESX host during login to the vSphere client using the same Hostname.Solution, attached are windows server 2008 r2 sp2 pack 2 32 bit the installation instructions and file(s) needed for installation.You must connect to the VMware machine (vCenter or ESX host) the same way you used when adding the VMware server objects into Backup Exec in order to create the backup jobs.Is there a way I can save the media server credentials from the Symantec Backup Exec plug-in tab?Exclude virtual machines from backup jobs.Note: VMware Workstation can be downloaded from VMware downloads at the following URL: m/go/vmvalidator - ApplicationHA version.0 (required for Virtual Machine Auto Recovery feature) - Microsoft.Net version.5 SP1 - Adobe Acrobat or any other PDF reader (required for viewing the VMware Plug-in help.The plug-in does not save credentials due to security reasons.
Similarly, the vSphere client console prohibits you from saving user credentials from a vCenter or ESX host.
Validate the virtual machine backups using the Virtual Machine Validator feature.