Solved

App Aware backups for SQL on EC2 issue

  • 11 August 2021
  • 2 replies
  • 93 views

Userlevel 2
Badge +8

We are doing some testing with EC2 running Windows and SQL.  I enabled App Aware backups and the first issue we have come across is the VSAAppAwareBackupWorkflow is picking up the EC2 instance internal machine name instead of the Domain name.  Is this how it is supposed to work?  The Commserve cannot resolve the internal machine name  - ip-10-49-2-225.us-east-2.compute.internal.  The domain name is Test-CV-SQL-Backup-01.  Any help is appreciated!

icon

Best answer by Gopinath 11 August 2021, 19:30

View original

2 replies

Userlevel 5
Badge +8

Hi,

Please use resolvable fqdn on client properties and refer below BOL page for f/w environment remote installation part or have packages installed on client prior.

https://documentation.commvault.com/11.24/expert/104304_communications_and_remote_installation_requirements.html

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.

 

Regards

Gopinath

Userlevel 7
Badge +23

Hey @Melissa Adams 

Since AppAware needs to communicate to software running on the machine to coordinate with the application, the CommServe will need a route to communicate with the client machine you are backing up - as if it were physical.

Likewise, the first time AppAware is enabled, it needs to able to push install the software. By default it will look at the hostname of the client as received via the VSA (which in-turn looks it up against AWS in your case).

The docs have the procedure on how to get this working in a firewalled (or remote) environment:

https://documentation.commvault.com/11.24/expert/14265_enabling_remote_installation_for_firewalled_environments.html

but to cut to the chase, you should pre-install a filesystem core package to every VM you need to run AppAware backups on. At that time you can configure all the necessary network routing (i.e route traffic through the VSA proxy towards the destination VM).

Reply