BaaS (Backup-as-a-Service) refers to a backup platform that delivers software, storage, security, and networking through a converged Software-as-a-Service subscription model.
A shared model of BaaS is essentially a multi-tenant environment; whereas, a dedicated instance BaaS model refers to a single-tenant SaaS architecture.
Taking a more in-depth comparison of HubStor’s virtual machine backup models—shared versus dedicated SaaS models—this post offers guidance to help you decide which model is right for you.
At-a-glance comparison of shared versus dedicated BaaS models
We previously documented the general differences between multi-tenant and single-tenant SaaS architectures here.
Looking specifically at HubStor’s BaaS model differences, the following chart offers a breakdown:
|SaaS tenant architecture||Multi-tenant||Single-tenant|
|Pick your deployment region?||Yes*||Yes**|
|Self hosting option||No||Yes|
|Inline storage reduction||Yes||Yes|
|Storage tiering and retention policies||Yes||Yes|
|Chargeback analysis and reporting||No||Yes|
|Expandable to other virtual machine backup scenarios||Yes||Yes|
|Expandable to content archiving use cases||No||Yes|
|Expandable to file system backup and cloud tiering||No||Yes|
|Expandadable to PaaS and SaaS backup (e.g., Office 365)||No||Yes|
|Multi-region scale out with central admin panel||No||Yes|
|Legal hold and discovery search||No||Yes|
|Security hardening options like IP whitelisting||No||Yes|
|Option to prepay consumption for discounted rates||No||Yes|
|Option to pay by invoice in arrears||No||Yes|
* HubStor currently supports shared instance deployments in the East US, West US, and North Europe regions. Expansion to more regions will occur in the future.
** The full list of hosting regions for a dedicated instance is available here.
When is HubStor’s shared BaaS model best to use?
The shared deployment model is ideal for organizations that want a simple virtual machine backup solution at an incredibly competitive price point.
If your sole focus is to protect your virtual machine environment, your backup storage requirement is less than several hundred terabytes, and you want a convenient backup solution at the lowest price point, then the shared architecture is going to be your best fit.
When not to go the shared BaaS path
Before you jump into the shared model with both feet, here are some important considerations:
- It is a multi-tenant environment, which means that you can’t expand it to any of the other HubStor capabilities such as Office 365 backup, video storage, email journaling, etc.
- Being shared, you don’t have as many options for compliance and security in terms of options for data sovereignty and security configuration hardening.
- If you prefer annual billing arrangements to align with the finance operations of your company, keep in mind that the dedicated instance approach offers this flexibility only.
You can get an analysis of the pricing differences here.
Primary reasons to go with a dedicated instance
Dedicated instances aren’t for everyone, especially when you have a smaller virtual machine environment to protect, because the costs implications of dedicated cloud resources skew the price economics. In other words, with more extensive data volumes or multiple use cases, you are more likely to achieve economies of scale with the dedicated cloud resources.
Here are the main reasons to start out with a dedicated tenant:
- Scaling up (or out) is in your future such that you plan to leverage your HubStor environment for large volumes of virtual machine backup data storage and/or, you plan to take advantage of the HubStor platform’s ability to solve multiple backup or archiving use cases beyond virtual machines.
- Business use cases such as immutable retention and eDiscovery are on your radar.
- You need to scale your HubStor tenant across multiple cloud regions while maintaining global identity and security, and central administration.
- You require maximum performance for ingress/egress of data.
- You must have access to HubStor’s advanced options for security hardening and data sovereignty.
- Self-hosting is preferred.
- You require flexible payment options such as paying by check or wire transfer.
- Your finance structure requires you to prepay annually in advance.
If any of the reasons above are right for you, then a dedicated instance is going to offer better alignment with your needs.
What happens if you want to change down the road?
How easy is it to jump from shared to dedicated, or vice versa?
Let’s say you started in the shared model, but later wanted to start a dedicated instance to expand into other use cases. You could either continue your dedicated instance in parallel to using the shared instance for your virtual machine backups, or you could easily switch your virtual machine backups to leverage your dedicated instance moving forward.
Moving from a dedicated instance into the shared model is just as simple. However, keep in mind that you can leverage the shared model for virtual machine backups only. You would not be able to move Office 365 backup, file share backup, or message journaling into a shared environment at this time.
General advantages of both BaaS models
Regardless of which path you take, HubStor’s elastic BaaS models offer some unique advantages that our competitors lack:
- There is no requirement for any upfront payments and no lock-in from term commitments.
- You don’t need to count virtual machines, CPUs, or host machines. Pricing is based on the usage of cloud resources, not some arbitrary software licensing concept.
- You pay only for what you use, so there is never any panic due to underprovisioning, and never any waste from overprovisioning.
- There’s no technological lock-in. We make it easy to get your data out if you ever need to change course.
Please connect with a HubStor technologist if you want to see a demo or look at a pricing estimate.