Skip to main content
Question

Cross region replication

  • March 25, 2026
  • 4 comments
  • 31 views

We are currently using Amazon S3 Standard as the Capacity Tier and S3 Glacier as the Archive Tier for offsite backups in the AWS region.

We are now looking to implement Capacity Tier replication to another AWS region.

Backup configuration:

  • Daily incremental backups and weekly synthetic full backups
  • Backups are retained in the Capacity Tier for 15 days
  • After 15 days, weekly backups are moved to the Archive Tier (Glacier)

Please advise on the best approach to configure replication of backup data between AWS regions for capacity tier

4 comments

matheusgiovanini
Forum|alt.badge.img+8

For cross-region replication in Capacity Tier, use S3 Cross-Region Replication (CRR) on the source bucket.

This will automatically copy objects to another region and is fully compatible with Veeam-generated data.

Veeam itself does not handle bucket-to-bucket replication — it only offloads data to object storage.

 

From veeam documentation:

“Veeam Backup & Replication does not support native S3 replication across buckets.”

https://helpcenter.veeam.com/docs/backup/vsphere/object_storage_repository.html

 


thank you ​@matheusgiovanini  for your time and suggestion.

but as per the VEEAM- it will not support AWS native replication ( s3 cross region replication)// Request you to review and advice !

 

Amazon S3 and S3 Compatible Object Storage Considerations and Limitations - Veeam Backup & Replicat…


matheusgiovanini
Forum|alt.badge.img+8

You’re correct that Veeam Software does not support native S3 replication across buckets.

However, this means Veeam itself does not manage replication, it does not prevent using AWS native replication.

For cross-region scenarios, the recommended approach is to use S3 Cross-Region Replication (CRR) on the Amazon Web Services side.

Veeam will continue to offload data normally, while replication between regions is handled by AWS.


Jean.peres.bkp
Forum|alt.badge.img+8

@dlinfrastructureteam , follow my advices:

 

Use Veeam‑managed replication (Backup Copy to Object Storage) instead of native AWS S3 replication.

  • Create a second S3 bucket in another AWS Region

    • S3 Standard
    • Object Lock enabled
    • Encryption enabled
  • Add the secondary bucket as another Veeam Object Storage Repository

    • Enable immutability
    • Configure as Capacity Tier
  • Configure a Backup Copy Job

    • Source: Primary backups / Capacity Tier
    • Target: Secondary S3 Capacity Tier (Region B)
    • Copy backups immediately
    • Retention: ≥ 15 days (same as primary)
  • Keep replication within the 15‑day S3 Standard window

    • Replication happens before data is tiered to Glacier

Archive Tier Considerations

  • Glacier is for long‑term retention only
  • Do not rely on Glacier for disaster recovery
  • You can optionally archive data to Glacier in Region B independently

 

What Not to Do

  • ❌ Do not use S3 Cross‑Region Replication
  • ❌ Do not replicate Glacier data
  • ❌ Do not rely solely on Archive Tier for DR

 

Component Recommended
Replication method Veeam Backup Copy to Object Storage
Primary tier S3 Standard + Object Lock (Region A)
Secondary tier S3 Standard + Object Lock (Region B)
Use S3 CRR ❌ No
Use Glacier for DR ❌ No

 

Just a reminder. It's extremely important to have an idea of ​​the cost before creating any backups:

My Estimate - Calculadora de Preços da AWS