Client components for App-Aware backups

Last post 02-06-2019, 5:26 PM by cre01. 2 replies.
Sort Posts: Previous Next
  • Client components for App-Aware backups
    Posted: 02-06-2019, 2:55 PM

    Perhaps i missed the memo somewhere.

    Our environment is heavily distributed (16 sites spread around the globe) and not particularly well connected (our highest average wan bandwidth is 10mbps, many sites have less).

    As a result, we've deployed a software cache to the media agent at each site and have regular download and sync jobs to keep them up to date.

    However, I can't seem to find a way to tell a first-time app-aware backup to download client components from the local software cache, instead of reaching across our wan to the commserve software cache. 

    Is this possible?

  • Re: Client components for App-Aware backups
    Posted: 02-06-2019, 4:53 PM

    • 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. you have the cache on the VSA proxy?

  • Re: Client components for App-Aware backups
    Posted: 02-06-2019, 5:26 PM

    The MediaAgent is the VSA proxy. The media agent is also physical, if that makes a difference. Backups are performed via NBD.

    App-Aware is successfully pushing packages automatically, it just pushes them from another site, instead of the local cache. 

    The issue is not that i have to manually install, but that the automated install is consuming wan bandwidth instead of using the local cache on the local MedioAgent.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy