Backup Copy Job with AWS & S3 / Case #07709332

[LEWISF]

I have jobs that are dedicated to specific SOBRs. There are 4 SOBRs.

The perf tier in each SOBR is a local NAS and the cap tier is AWS from one of our vendors.

The business has a requirement to replicate the AWS to another repository. We have another vendor providing S3 buckets.

I setup 4 separate copy jobs. The source for the copy jobs are backup jobs. Each backup job is dedicated to a specific SOBR.

If job 1 is targeted to SOBR 1, the copy job uses job 1 as the source and the target is the S3 bucket I created for all the jobs that use SOBR 1.
If job 8 is targeted to SOBR 2, the copy job uses job 8 as the source and the target is the S3 bucket I created for all the jobs that use SOBR 2.
If job 10 is targeted to SOBR 3, the copy job uses jo 10 as the source and the target is the S3 bucket I created for all the jobs that use SOBR 3.

The copy jobs are working and have been successful.

I was doing some testing today and discovered that as a source for the copy job I could select an AWS repo as a source and S3 bucket as a target. My question is, should I change the copy job to use AWS buckets as my source and S3 buckets as my target? What impact would that have on egress charges going from my AWS buckets from one vendor to S3 buckets provided by another vendor?

[david.domask]

Hi LEWISF,

In terms of data transferred, no real changes though please note that if jobs use the repositories unintentionally, this data will be copied when sourcing from repositories, so you may have unexpected data transfers.

I think the main difference will be more API calls from the job activity potentially, which AWS charges for but since you have a vendor providing it not sure if you will absorb the costs or not.