But, if I have a second site to replicate my instances, why do I need a Cloud Connect partner? I will accept the argument of OPEX vs. Now, going to DRaaS It's an easy sell to offer DRaaS to a company that requires a complete BCDR plan, designed by a VMCA, that does not have a second site. Veeam support engineers may not all be VMCAs, but they are well versed in simple VBR situations. Why not, as a customer, have a Hardened Linux Repo and immutable cloud storage in a SOBR? There is always the option of contacting Veeam support to assist with a recovery situation.
#Veeam backup price download
Is there a VCSP that offers ≤ $5/TB/month with potentially free download of unlimited data?įurthermore, for a VCSP to offer immutability, they would need to land the Backup Copy Job onto a Hardened Linux Repository or use a SOBR themselves with an immutable cloud storage solution (granted there are Veeam supported on-prem S3-compatible solutions). They made the Veeam Alliance Partner program two months after AWS.
Would having that level of skill not increase the offering cost since you would need to cover the salary of those highly skilled staff members in an effort to maintain your environment?Ĭan a VCSP scale to the level of AWS at the cost point that AWS is capable of scaling? Now, consider Backblaze B2. offsite, scalable, and immutable" option? Maybe they have 100 VMCAs, I don't know, but, I doubt they built up S3 with internal VMCA resources. Would you argue this is "required" when a customer is just looking for a landing zone of backup data? Does AWS need VMCE/VMCAs on staff to be a solid, and recommended (tied for the oldest Veeam validated immutable object storage), solution for an ". You are correct in that a VCSP is highly likely to have highly skilled Veeam engineers/architects. offsite, scalable, and immutable" option, there is cloud storage that will be less expensive and can be justified as a better option than Cloud Connect. To clarify, I would argue that in a majority of cases, if a customer is ONLY looking for an ". This isn't to exclude the other offerings of Cloud Connect partners as viable, just that there are other solutions for the "simple" things that I may see as better options. Both are valid reasons for using Cloud Connect. I stated that my experience is customers go to Cloud Connect when they want cloud to be the first backup location or want an option for DRaaS because they likely do not have a secondary site to do their own replication. I agree that Cloud Connect as the first landing zone is not popular/common. The most common that needs to be considered is that the Veeam Config Backup file cannot land on a SOBR and you will want to create a non-SOBR associated repo for that. You can use your existing repo as the Performance Tier, but, there are some limitations you want to consider.
#Veeam backup price archive
The steps to adding them into Veeam will be the same as far as adding an Object Storage repo, creating a SOBR, and adding the Object Storage repo as Capacity Tier and Archive Tier into the SOBR.Īdding an Object Storage Repo most will fall under S3-compatible: I would look to their documentation for those pieces. Each partner on that list will have their own steps for setting up accounts and buckets with immutability.