#VEEAM BACKUP TO CLOUD ARCHIVE#
#VEEAM BACKUP TO CLOUD FULL#
#VEEAM BACKUP TO CLOUD DOWNLOAD#

If you went the 'different architecture' route I outlined above, the VBK (and the VMs, their restore points, files, etc.) are still in your VBR console. It would have to be re-downloaded and then imported for the files/restore points to be there. Rick, does Enterprise edition of Veeam mitigate this? If the VBK file is not in a repository anymore, can I still search for what backup it was in with Enterprise? Or am I misunderstanding the difference between Standard and Enterprise? If the VBK is removed from the local repository AND put in Amazon/Azure, etc., then it is out of the catalog in the VBR console. That's not really possible with anything except a one-way import to EC2. I was hoping maybe there was a way to have a VPN to EC2 where I could use EC2 to extend my onsite production center and send backups or replicas directly there and have instances that just needed to be turned on if things went bad onsite. My takeaway was I would need to have my VBK files in S3 first, and then pull those VBK files down to an EC2 instance running Veeam and then restore the VMDKs and then import those VMDKs into an EC2 instance, correct? Yes, Correct.

#VEEAM BACKUP TO CLOUD ARCHIVE#

If you couldn't tell, I don't have a whole lot of experience with this fancy cloud thingy :), but I'm looking for easy options to store my backups offsite and to keep my yearly archive backups.

#VEEAM BACKUP TO CLOUD DOWNLOAD#

So as it currently stands was I correct in my assumptions about what I can do right now with just Veeam Standard?ДЎ) If I'm moving VBK files to the cloud for offsite storage, I'm going to have to download the whole thing and import it into Veeam to search the contents? Would the second scenario you described with EC2 avoid this? I'd assume so since I'd have a VPN connection and it would like the file is still on disk somewhere?Дў) If I know what VBK the file I want is in, I'm downloading the whole VBK to do that restore. We have 15MB up and down on a fiber connection.

#VEEAM BACKUP TO CLOUD FULL#

Now small is relative, but look at the size of your VBK and ask if your web bandwidth has enough legs to get the full backup size up there.Well currently the total backup size for the VBKs are around 500GB (there's 3 total VBKs since I do 2 separate jobs for our 2 most critical servers and 1 job with our remaining servers).

If you have a 'small' data profile, that's a good way to get files to the cloud. I'm just trying to come up with a plan for storing offsite backups for DR purposes as well as for holding on to backups for the required amount of time and I just want to wrap my head around how this process would work. I would imagine this would be determinate on whether I can present my cloud storage as a local or networked drive maybe? Can someone walk me through the following:ДЎ) How am I finding what backup this file is in? I'm using Veeam Essentials Standard and I understand there is a difference in searching online/offline backups? Does that mean I am going to need to download all VBK file first to search them?Дў) Assuming I know what VBK file holds the file I'm looking for, again am I having to download the whole VBK to access it or is there some way I can restore from the VBK file that is 'on the cloud' so to speak. So let's say I get a request to find a missing file that is several months old and I don't have in my shorter term onsite backups that are on my NAS. Let's say I am looking to move my Veeam backups to 'the cloud' so I have a copy offsite and maybe also for long term archiving of monthly/yearly backups.

I'm hoping someone can just walk me through this process here. I figured I would start another thread since this is going in a slightly different direction.

Veeam backup to cloud