Backup as a service (BaaS)
Backup as a Service (BaaS) is a subscription model in which a provider runs the backup software, the storage and their maintenance, while the customer decides what to protect, how long to keep it and who may restore it. Responsibility is shared, and the contract sets where each side's duties end.
What does the provider operate?
- The backup software and its servers, including patching and upgrades.
- The storage that holds the copies, its capacity planning and its hardware refresh.
- Monitoring of the service itself and the separation of one customer's data from another's.
- The physical security and location of the data centers.
What stays with the customer?
- Which systems are protected and how long each restore point is kept.
- Who is allowed to request restores and change retention.
- Recovery objectives: how much data loss and downtime the business accepts.
- Proof that restores work, through tests at realistic data sizes.
- Accounts and credentials used to sign in to the service.
The provider's service level usually covers availability of the platform, not the time a particular restore takes, so the recovery deadline stays with the customer.
Where does the shared model leave gaps?
Gaps sit in the duties that neither list names. Contracts differ on who installs agents, who notices a job that fails silently and who tests restores. Deletion rights are the most important gap: if the provider's staff or the customer's own administrator can shorten retention without a second approval, the immutability on offer is a policy rather than a property of the storage. Data location and legal jurisdiction, covered under data sovereignty, and what happens to the copies when the contract ends, are two more.
What limits restore speed?
A full restore moves the whole data set across the slowest link between provider and customer, which is often the customer's own internet connection. Large restores over a modest link take days, and the case BaaS is bought for, a full recovery after ransomware, is the largest restore of all. Measured restore throughput at the customer's real data size is the figure that matters. Hybrid designs keep a recent local copy for large restores and use the provider copy for site loss.
Why is provider administration a shared risk?
An attacker who compromises provider-side administration can reach many customers at once. Two controls limit that reach: tenant isolation on the shared platform, and locks such as S3 Object Lock that the storage enforces even against provider accounts.
Frequently asked questions
Is BaaS the same as disaster recovery as a service?
No. BaaS stores restorable copies of data. Disaster recovery as a service also keeps compute ready so applications can run at the provider while the primary site is down.
Does BaaS remove the need for in-house backup skills?
It removes infrastructure work. Decisions about retention, restore testing and recovery objectives stay with the customer, because only the customer knows what has to come back first.
Can BaaS data be encrypted so the provider cannot read it?
Yes, when the customer encrypts before upload and keeps the keys. The provider then stores data it cannot read, and the customer carries the risk of losing those keys.
