- Posts: 13
- Liked: 1 time
- Joined: Aug 30, 2018 4:21 am
- Full Name: John McGuigan
we have a VEEAM setup which has been running successfully for the last few years but space for backups as always is at a premium so I've been looking at getting VEEAM to send some of my backups to the cloud (AWS predominately).
We have one of each of these processes:
1. Daily backup to a repository on a local SAN.
2. Daily replication to a VMWare setup at an offsite location
3. Daily continuous backup copy to a NAS in another building on site.
If I have read things correctly I can:
Create a Scale Out Repository pointing at AWS
Add my existing repository in (1) and possibly (3) to it
Set the retention period (7/14/28 days)
And VEEAM will move the backup data which meets the retention period to AWS
Or have I picked it up incorrectly?
- Veeam Software
- Posts: 4408
- Liked: 553 times
- Joined: Sep 01, 2014 11:46 am
- Location: Austria
I moved the topic to the object storage forum and edited the topic to make it easier to read / find.
yes, you can point the "capacity tier" to AWS. See user guideCreate a Scale Out Repository pointing at AWS
hmm, I'm not sure I understand. You can add your existing repositories to scale out repositories. But you don't want to add both repositories to one scale out repository.Add my existing repository in (1) and possibly (3) to it
Veeam will move files of inactive chains to AWS. So if you have GFS enabled for your backup copy job, then it would do that. For the primary repository: if you have Reverse Incremental, then it would offload old increments to AWS. This section of the user guide has more details.And VEEAM will move the backup data which meets the retention period to AWS
Users browsing this forum: No registered users and 1 guest