Application Aware VSA Backups

Last post 06-07-2016, 6:47 PM by GopinathK. 4 replies.
Sort Posts: Previous Next
  • Application Aware VSA Backups
    Posted: 06-07-2016, 2:42 PM

    I'm trying to employ App Aware (Exchange) VSA backups and hava a question regarding the Communications requirements for said backups. Books online states that “The CommServe system, VSA proxies, and the virtual machine running the application must be able to communicate with each other”.

     

    To what extent must that communication be? Specific ports? Protocols?

  • Re: Application Aware VSA Backups
    Posted: 06-07-2016, 2:47 PM
    • Ali is not online. Last active: 02-22-2019, 10:44 AM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Hi Eagle, there must be physical connectivity.

    Ports and protocols are standard, as long as the VSA can see the VMWare enviornment.

  • Re: Application Aware VSA Backups
    Posted: 06-07-2016, 2:54 PM

    So there isn't a requirement for the guest OS hosting the Exchange environment to have connectivity to the VSA Proxy?

  • Re: Application Aware VSA Backups
    Posted: 06-07-2016, 3:27 PM
    • Ali is not online. Last active: 02-22-2019, 10:44 AM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Correct, same as a normal VSA backup job

  • Re: Application Aware VSA Backups
    Posted: 06-07-2016, 6:47 PM

    Hi,

    we need below requirements to be met for application aware backups to work. It will find out the application running inside the VM and then push install the required plug-ins inside the VM.

    http://documentation.commvault.com/commvault/v11/article?p=products/vs_vmware/r_vmw_backup_appaware_reqs.htm

    Communications

    The CommServe system, VSA proxies, and the virtual machine running the application must be able to communicate with each other.

    Remote Installation Requirements

    During backups, application plug-ins are pushed to guest VMs running the corresponding applications.

    To enable remote installs, see Prerequisites for Installations Using the CommCell Console.

    To ensure that the CommServe host can communicate with virtual machines running applications, ensure that ports are opened for the first application aware backups as described in Review Firewall and Network Port Requirements

    http://intdocresource2:8086/commvault/v11/article?p=deployment/install/remote_install/r_remote_install_prereq.htm#Review_Firewall_and_Network_Port_Requirement

    For Windows computers, the following ports must be opened temporarily during the remote installation:

    • Port 135 for DCOM (Distributed Component Object Model).
    • Port 139 for NetBIOS Session Service (if you are using legacy Windows computers, such as Windows NT or earlier versions).
    • Port 445 for SMB (Server Message Block) file sharing.
    • Your Windows Management Instrumentation (WMI) port. For instructions on setting up a fixed port for WMI, see Setting Up a Fixed Port for WMI on the Microsoft website.

    Important: If Windows Firewall is enabled on the computer, the following ports must be open in Windows Firewall:

    • Port 135 for DCOM-In (COM + Network Access).
    • Port 445 for SMB.
    • WMI port.
     If you choose not to open ports 135, 139, 445, and WMI port on your network, you can set up a remote cache in the network where the client computer resides.
    • Important: After you install the software and configure firewall settings on the client, the only port that should remain open is the firewall tunnel port (8403 by default).

    Thanks

    Gopinath

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.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy