Send Aux copies to S3

Last post 08-12-2017, 12:12 AM by jjbiv. 2 replies.
Sort Posts: Previous Next
  • Send Aux copies to S3
    Posted: 08-03-2017, 1:17 PM

    We are looking to send secondary copies of our backups to S3 and would like some help clarifying how to best set this up.

    Since the copies are coming from one particular media agent, I presume that when configuring the cloud library, it should be on the same media agent as the source copy??

    For firewall purposes, which systems need to be able to connect to the amazon bucket.  Both Commserve and the specific Media agent?  For restore purposes, will each client in the environment need to connect to the s3 bucket?

    Cannot find answers to these in the documentation, so would appreciate any help.

  • Re: Send Aux copies to S3
    Posted: 08-03-2017, 4:27 PM

    One reason I ask this, is that I'm not sure what Media Agent to associate the S3 bucket to.  It does not make sense to use the same MA as the primary copy, and running a test restore on a temporary CV system, it seems that in doing the restore, the Commserve connects to the AWS, while the media agent does not.  Would be helpful if there was a flow diagram, or some type of document, on how to do this. 

    So I'm wondering what makes the "best practice" when starting off with the cloud for this purpose.

    All the documentation seems to have are broad outlines of the possible.

  • Re: Send Aux copies to S3
    Posted: 08-12-2017, 12:12 AM

    Only the MediaAgents which will write to (e.g. backups or aux copies) or read from (e.g. restore) need to be able to connect to S3. The only time another client would need direct access to S3 is if the client has the MA package installed on it to act as the MA for its backups/restores. If you use a MediaAgent which has direct (i.e. LAN free) access to the source copy, that would probably make the most sense as long as it has available resources to run the aux copy to S3.

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