Backup-as-a-Service (BaaS) and Disaster-Recovery-as-a-Service (DRaaS/RaaS) represent two major models ensuring high availability for the enterprise. All companies want to protect their production data against such disasters as fire, flood or human faults. And, when such disasters happen, these companies want to minimize their losses and restore their data as soon as possible.
In Backup-as-a-Service model a provider offers online data backup to its own off-site storage systems. So, when choosing this solution, a company shall decide what files will be backed up. If it’s application development, databases, images, source code and all other files are required to resume operation from the point when a disaster happens.
The provider’s function here is to ensure data consistency and restore backed up copies. If the client’s infrastructure goes out of order, the client is responsible for its redeployment and shall restore all other files beyond BaaS Service Level Agreement (SLA) manually. Therefore, after a serious interruption like fire, the company also has to install and configure required hardware.
In other words, BaaS provider restores only data.
Disaster Recovery-as-a-Service (DRaaS/RaaS)
Although the backup function is often a part of DRaaS (or RaaS), the process of data recovery is still different. In this case, company servers are replicated (mirrored) off-site as recovery instances in a cloud. The replication level depends on a DR-scenario, so it could be a minimum, scaled-down running environment or a full-scale suspended copy of the infrastructure in a cloud.
Choose BaaS if...
- The company infrastructure can be easily reassembled in case of a disaster
- Your business is not focused on application or web-service maintenance (e.g., access to the data is not required frequently)
- Your measured RPO and RTO don’t exceed the expected rate
- You have a disaster recovery specialist on board
- You need a cheap solution
Choose DRaaS if...
- The company infrastructure consists of multiple parts that can’t be easily reassembled in case of a disaster
- You develop web-services or applications that require 24/7 access
- The amount of data increases dramatically
- You’ve hired generalists to deal with a lot of different tasks
- You can bear additional expenses