BaaS limitations
Review these limitations before configuring backup plans or restoring data.
Backup chains and plans
A volume can belong to only one backup plan at a time.
A volume can use either local or remote backup storage, but not both.
A backup plan can retain from 1 to 30 restore points.
Deleting a backup plan does not delete its existing restore points.
Disconnecting a volume terminates its current incremental backup chain but does not delete existing backups.
To resume backups after disconnecting a volume, delete all its existing backups and add it to an existing or new backup plan.
Changing backup storage
The backup storage selected for an existing plan cannot be edited. If a volume already has restore points in one backup storage, those backups must be deleted before the volume can use another backup storage.
Backup quota
BaaS does not display the individual size of each restore point. Incremental restore-point size depends on changed disk blocks and can increase after:
operating system or software updates;
disk defragmentation;
archiving large amounts of data;
file system changes or volume expansion;
swap activity or other intensive writes.
Monitor the total BaaS quota and allow sufficient capacity for the full backup and subsequent incremental restore points.
Restores
Restoring a backup creates a new volume; it does not recreate the original instance or network configuration.
The primary project storage must have enough free space for the full provisioned size of the restored volume.
Deleting backups is irreversible.
Software RAID and encryption
BaaS is not recommended for software RAID configurations that depend on simultaneous, write-consistent backups of multiple volumes. Volume backup tasks run sequentially, so restoring the volumes may produce an inconsistent RAID set.
Test restores before using BaaS with volumes encrypted by third-party software. Some encryption products bind data to the original device identifier and may reject a restored volume.