PROVIDERS: Accelerate income by remotely managing the security of customer workloads within Azure and AWS
It’s no secret that increasingly more organizations are moving to a multi-cloud approach with production workloads which were traditionally within on-premises data centers being dispersed into public hyperscale clouds such as for example AWS and Azure. This creates an excellent opportunity for organizations also it departments to are more agile, cost and secure effective, but also creates challenging for cloud and managed providers that are asked to remotely protect the info that resides in these public clouds.
Veeam COMPANY Console v5 was introduced in February of 2021 and was built upon previous releases to permit Veeam providers further reach to their customers’ environments, offering them the capability to drive new service offerings around cloud-based and physical workloads. One new key feature of Veeam COMPANY Console was the ability of leveraging the built-in public cloud plug-ins in Veeam Backup & Replication v11, extending to the protection of customer workloads surviving in Azure and AWS.
Why this matters
It shouldn’t be considered a surprise to anyone in the managed services industry that workloads which have traditionally lived on-premises are getting into public cloud platforms. Speaking generally, it has been a top-down directive in which a CIO/CEO has driven the hype round the public cloud and what it could offer. In the technical world, whenever a strategy is down driven from the very best, without cause or validation, that can result in issues.
What we’ve seen is really a lift and shift method of workloads moving from on-premises or Infrastructure as something (IaaS) platforms “as-is” to public cloud platforms such as for example AWS and Azure. The outcomes of this certainly are a true amount of on-premises hypervisor-based VM instances migrating to EC2 or Azure VMs. These instances, surviving in the general public cloud now, have the potential never to be managed just as as what that they had been on-premises.
While Veeam makes is simple to migrate VMs in one platform to another through our workload mobility feature, managed providers need a solution to continue steadily to have awareness and control of these managed machines irrespective of where they’re located.
Harnessing the energy of the plug-ins
With the release of Veeam Backup & Replication v10a, the initial public cloud plug-in for AWS premiered also. This allowed the management, monitoring and deployment of Veeam Backup for AWS through the Veeam Backup & Replication console. The feature had a second benefit whereby managed providers could actually regain control of workloads which have moved to the general public cloud. That is done via integration with Veeam COMPANY Console v5.
The easiest way to spell it out how this benefits managed providers is to think about a typical customer. They could have an area vSphere environment with 20 VMs servicing several business-critical applications and services which are under management. They’re supported via Veeam Backup & Replication designed to use Cloud Connect Backup to send backup data up in to the managed providers cloud storage.
A directive then is out by a credit card applicatoin vendor that they can only support their product if it’s housed within AWS , meaning five of the VMs should be migrated to EC2. With the VM/VMs migrated into EC2, previous agentless backups can’t be existing and used Veeam Backup & Replication backup policies can’t be employed. At this true point, Veeam Backup for AWS must be leveraged to execute the snapshots and backups to Amazon S3 restore points of the new EC2 instances.
Prior to the COMPANY Console v5 capability to tap into the general public cloud plug-in capacity for Veeam Backup & Replication, the managed company could have had to track the VMs which were migrated to EC2 manually. To that further, they wouldn’t have already been able to be familiar with the backup policies and also bill for all those services.
Conclusion
Without Veeam COMPANY Console v5, awareness and control of previously-managed workloads because they proceed to AWS or Azure wasn’t possible. Moreover, this feature opens new revenue streams for managed providers to tap into which can not need existed previously. As clients onboard with workloads spread across on-premises or public cloud platforms… or for example, situations where whole applications are stored within public clouds, it now becomes possible to create revenue streams and capture a bit of the market that could haven’t been possible before. Visit Veeam.com to download the FREE Veeam COMPANY Console and begin offering Veeam-powered, today remote-managed BaaS and DRaaS services!