- Posts: 20
- Liked: never
- Joined: Dec 16, 2009 12:50 am
We've been using Veeam roughly 10 years now. The backup copy feature is great, as we send backup copies to a VM at an offsite datacenter nightly. The storage is presented as an SMB/CIFS file share. I'm concerned about ransomware or a sophisticated attack. We do take security precautions, such as the Veeam server is not on the domain, uses a different admin password, etc. But I know it's not foolproof.
Bear with me, as nearly everything we do is in-house, and I have very little knowledge of Amazon S3. But, what I would like to do is send backup copies to S3 with immutable storage.
What storage tier should I buy, assuming I will send backup copies nightly, and will need capability to make them immutable?
Do I simply setup the object storage in Veeam, point it at S3, setup a SOBR, and then point my backup copy jobs to the SOBR?
Can I move my existing backup copies from the offsite datacenter to the S3 bucket?
Thanks in advance!
- Veeam Software
- Posts: 1630
- Liked: 261 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
1) Both standard and infrequent access (IA) storage classes are supported for Amazon S3.
2) Yes, you just add an object storage as capacity extent to the existing SOBR.
3) Backups can be offloaded to the Capacity Tier by Move or Copy policies. By the way in case of backup copy job, the Move policy can process only full backup files that have a GFS flag.
- SVP, Product Management
- Posts: 29094
- Liked: 5356 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
In this case, may be consider V11 Hardened Repository instead of cloud object storage?
The latter is a great choice for those without a second off-site data center, but it sounds like you do have one. So the only other reason to use immutable backups in Amazon S3 would be implementation of the Zero Trust model (when you want to protect also against malicious sysadmins on staff). But this requires so many other pieces of a puzzle addressed in the environment besides backup... doing it just for backups hardly moves the needle.
Users browsing this forum: No registered users and 10 guests