Enabling Remote Installation for Firewalled Environments
For the first application-aware backup of a virtual machine, the backup must be able to access the virtual machine to install required components. In a firewalled environment with restricted network settings or where WMI ports are not open, you must ensure that the workflow that performs the remote installation can access all virtual machines that run applications.
Before You Begin
Use one of the following approaches to enable remote installations during application-aware backups:
- Commvault V11 Service Pack 7: Perform the steps in the Procedure section. This approach can be used for all hypervisors that support application-aware backups, and for the following applications:
- SQL Server (for SQL Server and for SharePoint support)
- Microsoft Exchange
- Oracle for Windows
- Microsoft SharePoint (on web servers that provide a front end for SharePoint operations)
- Commvault Service Pack 8 and later: For VMware, you can perform the following tasks before running an application-aware backup:
- Install VMware Tools on guest VMs.
- Configure a remote software cache on the VSA proxy that will used for the application-aware backup. Include packages for MediaAgent and any applications that should be protected using application-aware backups.
If VMware Tools are installed on guest VMs, you do not need to install the File System Core package manually (step 3). The first application-aware backup uses VMware Tools to push the File System Core package into the guest VM, and then CVD is used to push an application plug-in into the guest VM.
- Create a client group that contains all virtual machines for which application-aware backups will be performed.
- Define the desired Network topology.
You can use a predefined Network topology as described in Configuring Network Routes.
- On each of the virtual machines that were included in the client group for application-aware backups, perform a local installation or a remote installation of the File System Core package.
During the installation, enter a fully qualified domain name (FQDN) as the client name for the application client. The client that is created contains host information for the guest VM or instance.
For Amazon guest instances, check the client properties and make sure the Host Name box contains the public DNS name for the Amazon instance. For example, ec2-00-000-00-00.compute-0.amazonaws.com.
The client name must be less than 63 characters.
Note: If the VM is part of vCloud, ensure that the VM name including the VM GUID is less than 63 characters.
- Create one or more Virtual Server Agent subclients with application-aware backups enabled. The content of each subclient should include virtual machines from the application-aware backup client group.
During the first application-aware backup for a guest VM, the application-aware backup workflow pushes an application plug-in into the guest virtual machine. For more information, see Performing an Application-Aware Backup.
- Perform an application-aware backup.
During an application-aware backup, the VSAAppAwareBackupWorkflow tries to connect to virtual machines using WMI methods. If the WMI connection cannot be established, the workflow detects the presence of applications and application plug-ins that are supported for application-aware backups, and continues with any remaining configuration that is needed to complete the application-aware backup successfully.
Last modified: 11/19/2018 9:34:34 PM