Configuring a Linux Access Node for VMware Cloud Director

You can deploy a Linux machine to serve as a Virtual Server Agent access node for backups and restores of VMware Cloud Director VMs.

Procedure

  1. Download the Access Node and MediaAgent package from the Commvault Store.

    This package provides an OVA template that is pre-configured with the Virtual Server Agent, MediaAgent, and uses the Mono framework.

  2. Deploy the OVA template and configure the Linux access node.

    For more information, see Deploying a Linux Access Node for VMware Using vCenter.

  3. Perform a remote installation of all available Commvault maintenance releases for the installed service pack on the Linux access node.

Known Issues

  • For browse and restore operations, use a Linux access node and MediaAgent to browse Linux guests, and a Windows access node and MediaAgent to browse Windows guests.

  • Linux proxies get VM used space information from the vCenter, which might report a greater amount of used space than is actually used on NTFS volumes. This behavior can increase the guest size calculation that is used for capacity licensing. To avoid this issue, use Windows proxies for backups.

  • Find operations are only supported for backup operations that collect file and folder information. Find operations are not supported for backups performed using a Linux access node or for any hypervisor that does not support collecting file and folder information. Skipping page files is not supported when using a Linux access node for backups.

  • For backups, Linux proxies do not support metadata collection using the Collect File Details option. For guest file restores, you can use live browse to view and recover files.

    Backups that are performed using Windows proxies do support metadata collection using the Collect File Details option.

  • A known issue in Mono 4.8 might cause backups to fail with one of the following errors:

    TimerCallback() - Exception - Error: SecureChannelFailure (Ssl error:10000096:SSL routines:OPENSSL_internal:EXCESSIVE_MESSAGE_SIZE)
    exception - System.IO.IOException: Invalid parameter at System.IO.FileStream.Dispose (System.Boolean disposing)

Loading...