ThisCalculator

Everyday

SaaS Backup Test Recovery Retention Security Checklist

Updated · Standard formula, shown below

Total backups stored 30 count
Approx. storage needed (GB)
15.0 GB
Result
Backup frequency (hours)
24 h
You entered
Retention period (days)
30 days
You entered

SaaS Backup Test Recovery Retention Security Checklist

Before buying a SaaS backup solution, you must verify how it handles testing, recovery, retention, and security—these four areas determine whether your data is actually protected. This article explains what to check in each area, common pitfalls, and how to compare vendors so you can make an informed purchase.

Formula

The calculator estimates the number of backups you will retain and the approximate storage needed. The number of backups equals the retention period in days divided by the backup frequency in hours, then multiplied by 24 (since there are 24 hours in a day). Storage is estimated at 0.5 GB per backup, a rough average for a small business with email and documents.

Variables: t = backup frequency in hours, r = retention period in days, n = number of daily backups (calculated as r * 24 / t). Output: total = number of backups retained, storage = approximate storage in GB.

Worked Example

Using the default values: backup every 24 hours (daily), retention of 30 days. Number of backups = 30 days × 24 hours / 24 hours = 30 backups. Storage = 30 × 0.5 GB = 15 GB. So you would retain 30 backups and need about 15 GB of storage.

Why Testing Matters More Than You Think

Most SaaS vendors (like Microsoft 365, Google Workspace, Salesforce) offer some native retention, but they do not guarantee recoverability from accidental deletion, ransomware, or malicious insiders. A dedicated backup tool must let you test restores—not just schedule backups. Ask: Can I perform a test restore to a sandbox environment? How long does a typical restore take? Is there an automated testing feature that verifies backup integrity? Without testing, you may discover too late that your backups are corrupt or incomplete.

Recovery: What Happens When You Need It?

Recovery is the moment of truth. Check the following:

  • Granularity: Can you restore a single email, file, or record, or only entire databases?
  • Speed: What is the RTO (Recovery Time Objective)? Some tools restore in minutes, others take hours.
  • Point-in-time: Can you roll back to a specific moment, or only to the last backup?
  • Cross-user/admin: Can a non-technical user restore their own data, or does it require IT?

Also ask about disaster recovery: if the vendor’s infrastructure fails, how do you access your backups? Look for tools that offer export to local or another cloud.

Retention: How Long Is Enough?

Retention policies vary by data type and legal requirements. For example, financial records may need 7 years, while email might be 1 year. Common retention options include:

  • Daily backups kept for 30 days
  • Weekly backups kept for 1 year
  • Monthly backups kept for 7 years

Ensure the tool supports immutable retention—backups that cannot be altered or deleted even by an admin, which protects against ransomware. Also verify that retention applies to deleted items in the source app (e.g., a user deletes an email; the backup still retains it for the full period).

Security: Encryption and Access Controls

Security is non-negotiable. Check these points:

  • Encryption in transit and at rest: Look for AES-256 at rest and TLS 1.2+ in transit.
  • Customer-managed keys: Can you bring your own encryption key (BYOK)? This gives you control and helps with compliance.
  • Access controls: Does the tool support role-based access (admin, restore-only, read-only)? Can you set up multi-factor authentication (MFA)?
  • Audit logs: Can you see who accessed backups and when?
  • Data residency: Where are backups stored? If you have GDPR or local data laws, you may need backups in a specific region.

Also ask about the vendor’s own security certifications (SOC 2, ISO 27001) and whether they have a history of breaches.

How to Compare Vendors

Create a checklist and compare at least three vendors. Use a trial period to test the actual restore process, not just the UI. Key questions to ask in a demo:

  • Show me a test restore of a single item and a full-site restore.
  • What is your uptime SLA for the backup service?
  • How do you handle backup failures? Do you alert me?
  • Can I export backups to my own storage (e.g., AWS S3)?

Check reviews on third-party sites, but be wary of overly positive or negative posts. Look for long-term users who have actually performed restores.

Common Mistakes and Misconceptions

One common misconception: “The SaaS vendor backs up my data, so I don’t need extra backup.� That is false—most SaaS vendors only protect against hardware failure, not user error or malicious deletion. Another mistake is not testing restores until an emergency. Also, some buyers ignore retention limits: if you need to keep data for 7 years, a tool that only offers 1 year is useless. Finally, don’t assume that a backup tool with strong security features is automatically compliant with your industry regulations—verify with your legal team.

Costs and Alternatives

Pricing for SaaS backup tools is typically per user per month, often $3–$10 per user. Some tools charge for storage separately. Free alternatives include native export features (e.g., Google Takeout, Microsoft 365 eDiscovery), but they are manual and not automated. Open-source tools exist but require technical expertise. Weigh the cost of a backup tool against the cost of data loss: for a business, losing customer data can be catastrophic.

Frequently Asked Questions

What is the difference between backup and archiving?

Backup is for recovery after loss or corruption; archiving is for long-term retention of old data that you may need for compliance or reference. Backup is typically short-term (weeks to months), while archiving is years. Some tools offer both.

Can I restore data from a backup if I accidentally deleted a user account?

Yes, if the backup tool captures user objects and their data. Most tools allow you to restore a deleted user and their associated data (emails, files, etc.) to a specific point in time. However, check if the tool supports restoring to a different user or as a new user.

How often should I test my SaaS backups?

At least quarterly, or whenever you make major changes to your environment (e.g., new integrations, user migrations). Some tools offer automated testing that runs on a schedule—use that feature if available.

What is immutable backup and why is it important?

Immutable backup means the backup data cannot be modified, encrypted, or deleted by anyone, including administrators, for a set period. This protects against ransomware attacks that try to delete backups to force a ransom payment. Many modern backup tools offer this as a feature.

Do I need a separate backup for each SaaS app (e.g., Office 365 and Salesforce)?

Not necessarily. Many vendors offer multi-app support in a single platform, so you can back up email, files, CRM data, etc., from one dashboard. This simplifies management and often reduces cost compared to buying separate tools.

Related

Formula used
in t | Backup frequency (hours) | h | 24 | 1
in r | Retention period (days) | days | 30 | 1
in n | Number of daily backups | count | 30 | 1
out total | Total backups stored | count | n | 0
out storage | Approx. storage needed (GB) | GB | n * 0.5 | 1

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.