PowerProtect Data Manager 19.16 Virtual Machine User Guide

The VIB installation occurs automatically at the cluster level when a virtual machine protection policy is created, with no requirement to restart the ESXi hosts or put the hosts into maintenance mode. When updating PowerProtect Data Manager from a release that used TSDM-enabled policies, the VIB has been optimized to detect if the software already exists in a datastore and only upload the VIB where the software is not shared across ESXi hosts. Also, the VIB will now update on the respective ESXi hosts concurrently instead of sequentially, in batches of 25, skipping any ESXi hosts that are powered off or in maintenance mode

Within the PowerProtect Data Manager UI, the Transparent Snapshot Data Movers pane on the Infrastructure > Protection Engines window provides a hierarchy view of the vCenter Server asset sources that have been added in PowerProtect Data Manager. Use this view to determine if the vCenter or ESXi server is enabled for automatic VIB management, and if the hosts have the VIB installed or are eligible for VIB installation. A vSphere host cluster can have one of the following statuses:

• Installed—The VIB installation on this vSphere host is completed, and TSDM is enabled as the default protection mechanism for the virtual machines on the vSphere host.
• Ready for install—The vSphere host requirements for VIB installation have been met, and the installation will proceed automatically on the vSphere host when a virtual machine running on the cluster is added to a protection policy.
• Ready for upgrade—This status displays when the VIB is installed on the vSphere host and PowerProtect Data Manager is updated, but the VIB is being managed manually. In this case, older VIB versions that are still supported are not updated automatically on the host.
• Not eligible—The vSphere host does not meet the requirements for VIB installation. When TSDM cannot be used, the VMware vSphere Storage APIs – Data Protection (VADP) protection mechanism is used for virtual machine protection operations on this host.
• Failed—The VIB installation on the vSphere host did not complete successfully. The Jobs window provides more information about the issue that caused the failure.

When the automatic VIB installation is started, the following occurs:

• The Protection Engines window updates to display the progress.
• An entry for the job Performing Host Configuration appears in the Jobs window.
• If the host is in a cluster configuration, entries for the tasks Start service and Update service activation policy appear for each host in the vCenter UI.