1. When backup is included
Backup is included only where a product description or order expressly states it. Some unmanaged infrastructure may have no backup by default.
2. Independent backup
Customers should maintain independent copies of important data outside the same failure domain. AlpineLayer backup reduces risk but is not a substitute for customer continuity planning.
3. Schedule and retention
Backup frequency and retention differ by plan and must be published with the product. Expired restore points are deleted automatically and may not be recoverable.
4. Restoration
Self-service restores may be available on supported products. Managed restores can overwrite existing data, so customers must verify the selected restore point.
5. Limitations
Backups may fail or be incomplete because of corruption, application locks, unsupported files, customer encryption, malware, quota limits, credentials, network interruption or platform failure. No backup system can guarantee recovery of every object or application state.
6. Termination
After cancellation, backups may be deleted according to the service retention schedule. Customers should export required copies before termination.
7. Restore testing
Business-critical customers should perform periodic restore tests. Managed disaster-recovery services can include formal testing when contracted.