Veeam immutable backup to AWS
I am attempting to create an immutable backup for my server. I have a VMware virtual server (Linux). I have a direct-attached external drive that I use as the immutable backup repository.
I have created an AWS repository and was hoping to mirror the immutable backup to that storage.
It looks like I needed to create the mirror on a local repository and then have it copied to the cloud. So I decided to add local storage to my VMWare host.
So as you can probably tell, I am completely confused. It feels like a chicken or egg scenario. I am not sure what this should ultimately look like. Don't know if I need to configure the Local Host storage first, or backup repository or configure from the Linux VM.
Is there a resource that says if you have a VMWare environment and want to create a Veeam immutable backup in the cloud, these are the steps you take and the order in which to complete them?
So far I see hundreds or threads, but as soon as I start, I find that there is a prerequisite that hasn't been met. So I am spinning in circles.
Tried to find the EE Gigs feature where I could hire someone to help, and it doesn't look like EE does that anymore.
Who would be kind enough to point me to a resource (human, video or flow chart)?
Thanks in advance.
Make sure the Configuration Backup is _not_ backed up to the USB drive being used as a local repository. SOBR won't let you choose it as a local repository if it is set up that way.
@Andrew Hancock is correct. B2 is a better option.
@Andrew Hancock is correct. B2 is a better option.
ASKER
Thanks so much, Andrew and Philip.
On Step one of Andrews's recommendations, it states that we need to "create a local storage component as a Backup Repository. "
So I have about 10TB of space on the local VMware host. This is actually hard drives on the host server. This is provisioned as a datastore in VMWare. So I have about 10TB of space on the local VMware host. These are actual hard drives on the host server. This is provisioned as a datastore (Linux Host Storage) in VMWare
When I go into Veeam to create a local storage component that will point to that Datastore, it says network path not found.
So I guess, I am drawing a blank about how to make this local store available as a Veeam BU Repository.
On Step one of Andrews's recommendations, it states that we need to "create a local storage component as a Backup Repository. "
So I have about 10TB of space on the local VMware host. This is actually hard drives on the host server. This is provisioned as a datastore in VMWare. So I have about 10TB of space on the local VMware host. These are actual hard drives on the host server. This is provisioned as a datastore (Linux Host Storage) in VMWare
When I go into Veeam to create a local storage component that will point to that Datastore, it says network path not found.
So I guess, I am drawing a blank about how to make this local store available as a Veeam BU Repository.
The IP address of the host is probably the way to do it and setting the username and password set in VMware for repository MOD access as well.
Is Veeam Backup and Replication installed in a VM
Create a 10TB virtual disk but do make sure not to fill the datastore entirely
The VMDK virtual disk will then be stored on the host datastore
You cannot use storage on the ESXi host directly there is no CIFS or NFS server on ESXi
Create a 10TB virtual disk but do make sure not to fill the datastore entirely
The VMDK virtual disk will then be stored on the host datastore
You cannot use storage on the ESXi host directly there is no CIFS or NFS server on ESXi
Ignore my post. Andrew's is much better! :)
ASKER
Since my Veeam Server is a virtual machine and I have the Local Storage set up as a DataStore. Could I just add a second hard drive that points to the new Datastore. Then set up the scale out repository to point to the second hard drive on the Veeam server?
Since my Veeam Server is a virtual machine and I have the Local Storage set up as a DataStore. Could I just add a second hard drive that points to the new Datastore. Then set up the scale out repository to point to the second hard drive on the Veeam server?
Yes, That's what I suggested.
You add a disk to Veeam, which is located on the Host Datastore.
ASKER
Perfect
ASKER
Okay getting closer.
So when I initially tested this, it create the backups and copy to S3 storage. When I try to point to the new scale out repository, it is asking to move all backup files (first picture) to the new backup repository first. When I go to the old back repository, I don't see a move option. (second picture)
- Was able to create the local drive
- Next created the scale out repository
- Now trying to create the veeam copy job to take the backup from the new scale out repository and copy it to the AWS S3 tier
So when I initially tested this, it create the backups and copy to S3 storage. When I try to point to the new scale out repository, it is asking to move all backup files (first picture) to the new backup repository first. When I go to the old back repository, I don't see a move option. (second picture)
Are you given the option to actually move them?
ASKER
That's what I am saying. I don't see a way to move them.
Then the old fashioned copy is the way to do it.
I recommend BeyondCompare by ScooterSoftware.Com (can use the portable version).
It's easy to see what's been copied and what has not.
I recommend BeyondCompare by ScooterSoftware.Com (can use the portable version).
It's easy to see what's been copied and what has not.
So when you create the new backup job, and it backed up VMs, they got copied to S3 ?
that suggests it's working, in that backup job.
So what is happening now ? You are trying to copy existing backups to S3 ?
that suggests it's working, in that backup job.
So what is happening now ? You are trying to copy existing backups to S3 ?
ASKER
I really don't want them as they were for testing, but if I try to delete the files, it says they are "1/6/2022 3:43:32 PM Error [ColoExchange] Failed to delete backup Error: Unable to delete the backup because it is marked as immutable until 11 February 2022 17:46:07."
How do I remove the immutable flag?
How do I remove the immutable flag?
Are you comfortable with leaving the existing backups as is? If you are, then go about setting things up on the SOBR/Storage side and either clone the existing backup jobs or set up new ones and disable the previous ones.
Make sure to check the encryption settings if it is being used.
Immutable means it's there until the all clear date.
Make sure to check the encryption settings if it is being used.
Immutable means it's there until the all clear date.
ASKER
So, nothing seemed to work. I decided to just start from scratch.
Am getting an error that says 'immutable backups feature requires the usage of full incremental backup mode with periodic full". Searched for this error in Veeam and it said to set the Incremental as it is shown below - still gives me the same error.
- removed all backups
- removed backup repository
- removed scale-out repository
- removed Linux server
- Deleted folders in S3 storage
- added Linux server
- added backup repository
- added scale out repository
- tried to create backup job and could not finish.
Am getting an error that says 'immutable backups feature requires the usage of full incremental backup mode with periodic full". Searched for this error in Veeam and it said to set the Incremental as it is shown below - still gives me the same error.
Have just about decided this isn't worth the effort. Placed a call with Veeam to see what they have to say. I think it is going to take someone smarter than I am to figure this out.
Strange. We don't have any issues with setting things up.
That setting is what it wants. We set ours to do that once a month and also do a verification check once a month last day of the month.
That setting is what it wants. We set ours to do that once a month and also do a verification check once a month last day of the month.ASKER
So the Veeam website says "Do not enable synthetic full backups" So I did not check that.
Should I do this??
Should I do this??
I believe that's what it is asking for.
ASKER
Philip,
I believe you are correct, just didn't understand why Veeam references the article I posted above directing not to check that.
So I decided to follow your recommendation and selected the full backup. It completed just fine and the first set of new immutable backups have been completed.
On to the next tasks per Andrew:
1. You need to create a Scale-Out Backup Repository, and before you can do this, you must create a local storage component as a Backup Repository. - Done
2. Then add Amazon S3, as a Backup Repository - Done
3. Create Scale Out Repo - Not sure what this means. How is it different from #1.
4. Create Backup Job, select 3 above.
5. Backup Job runs and finishes.
6. Scale-out Job - copies data to Amazon S3.
I believe you are correct, just didn't understand why Veeam references the article I posted above directing not to check that.
So I decided to follow your recommendation and selected the full backup. It completed just fine and the first set of new immutable backups have been completed.
On to the next tasks per Andrew:
1. You need to create a Scale-Out Backup Repository, and before you can do this, you must create a local storage component as a Backup Repository. - Done
2. Then add Amazon S3, as a Backup Repository - Done
3. Create Scale Out Repo - Not sure what this means. How is it different from #1.
4. Create Backup Job, select 3 above.
5. Backup Job runs and finishes.
6. Scale-out Job - copies data to Amazon S3.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
All this is done and configured on the Veeam Backup and Replication server
1. You need to create a Scale-Out Backup Repository, and before you can do this, you must create a local storage component as a Backup Repository.
2. Then add Amazon S3, as a Backup Repository
3. Create Scale Out Repo
4. Create Backup Job, select 3 above.
5. Backup Job runs and finishes.
6. Scale-out Job - copies data to Amazon S3.
(Backblaze S3 is much cheaper than Amazon S3 - https://www.backblaze.com/b2/cloud-storage-pricing.html)