Best Practice Checklists

An exclusive publication of

Essentials every leader should understand about IT


Issue 3 – Backups, Frequency and Retention Strategy

Backups, Frequency and Retention Strategy — download the printable PDF

Download this article as a PDF

Click Here to Download
Contact Us

Backups, Frequency & Retention

The two settings that decide whether you ever see your data again

Every backup strategy hinges on two choices that sound like housekeeping: how often snapshots are taken, and how they are consolidated and retained over time. They rarely come up in conversation. Yet when data must be recovered, these quiet settings can mean the difference between a full recovery and a permanent loss. The situations below occur more often than most organizations realize.

When it goes wrong

Few backup strategies can recover from every possible situation, and that is normal. Most trade granularity for cost, and for many organizations that exposure is an acceptable risk. The point is not to alarm. It is to make sure the trade is one you chose on purpose.

Silent Data Corruption

An organization dutifully checks its daily backup notifications. Unseen, a rarely accessed disk begins to corrupt. It generates no alerts, so the corruption goes unnoticed for months. By the time it surfaces, it predates the one-year retention window.

Documents needed for an audit cannot be recovered.

Employee Fraud Investigation

Fraudulent transfer requests are created each Tuesday and quietly replaced by Thursday. The firm wants to prosecute and recover funds using the original metadata. But backups consolidate every Saturday.

The Tuesday-to-Thursday trail no longer exists.

Lawsuit or Legal Threat

A harassment claim turns on emails that were deleted between snapshot intervals. The company spends heavily defending itself before the evidence finally surfaces in discovery.

Available sooner, it could very likely have settled the claim for far less.

Accidental or Malicious Deletion

An employee deletes the wrong file, or a departing one purges it on purpose. A file created and deleted within the same month may already be gone once that month consolidates.

How long the file existed decides whether it comes back.

Undetected Crypto Virus

Ransomware quietly encrypts a folder of legal contracts, discovered only weeks later. Management declines to pay, and restores from a clean point before the infection. But that point predates a month of new contracts.

Every contract added that month is permanently lost.

The common thread

None of these is a story about cheap software or a small appliance. In each case the outcome was set, long in advance, by two numbers: how often snapshots were taken, and how long they were kept before consolidation.

Every one of these outcomes could very likely have been avoided. Not with a bigger budget, but with different choices about snapshot frequency and retention. That is the entire point of this issue.

What to Ask Your IT Manager or Provider

and how to know if the answers are good ones

You do not need to administer a backup system to oversee one. You need to know what to ask. A fuller primer on how these mechanisms work is provided at the end, for those who want the detail. First, the part that matters: run the checklist below with your IT professional. If any item is not marked green, it may warrant a closer look.

Suitable Backup Solution

✓
–
?
Does the solution meet the organization’s needs for functionality, schedule, frequency, retention, and consolidation? Both local and Cloud-based virtualization capabilities are recommended for optimal protection in a disaster.

Regular Success / Failure Verification

✓
–
?
Is someone designated to routinely check backup success and failure notifications, and to act on any failure, or on the absence of any notification, after a scheduled backup was to occur?

Media Rotation and Storage

✓
–
?
For solutions without Cloud-based storage, is someone designated to routinely rotate media and safely store backups off site at an agreed interval?

Test Restorations

✓
–
?
Are periodic test restorations performed? Backup images can corrupt silently; testing confirms the data is actually viable before you need it.

Redundant Backup of Cloud Environments

✓
–
?
Are suitable, redundant, third-party backups of Cloud-based solutions (for example, Microsoft 365 email) being performed? Provider retention policies vary, and a redundant backup managed by a separate party protects against gaps.

Encryption at Rest

✓
–
?
Are the backups themselves protected by encryption at rest?

Put it on paper

One clean way to document these settings is a simple weekly schedule. A completed sample is provided for reference; a blank version is available to complete for your own organization.

Sample Backup Schedule

Sample Backup Schedule

A completed example for reference

Download PDF
Blank Backup Schedule

Blank Backup Schedule

Fill in for your own organization

Download PDF
The primer: how this actually worksTerminology, for whoever wants the detail. Optional.+

Snapshot Frequency

The interval at which a backup captures changes made since the last snapshot. Changes made and reversed between snapshots are never captured at all.

Consolidation

Consolidation combines backup data or reduces retained recovery points according to the product and retention policy. The illustration below shows one roll-up policy that keeps the final snapshot in each series and discards intermediate recovery points. Other products can create synthetic full backups while retaining earlier restore points until their retention period expires. Confirm exactly which dates and versions remain recoverable.

Granularity before consolidation
Sun
Mon
Tue
Wed
Thu
Fri
Sat
✓
✓
✓
✓
✓
✓
✓
Granularity after consolidation
Sun
Mon
Tue
Wed
Thu
Fri
Sat
⊖
⊖
⊖
⊖
⊖
⊖
✓

Consolidation Schedule & Retention Time

The consolidation schedule is how often consolidations occur; frequent consolidation is what keeps backup data from accumulating and exhausting storage. Retention time is simply how long backups are kept before they are deleted.

Going deeper: what to pin down with your ITThe finer points that separate a backup that works from one that only looks like it does. Optional.+

The following should be discussed with your IT professional(s). Some points may not apply, depending on the type of backup solution you have.

Capacity

Backup capacity must cover the protected data, its rate of change, retention requirements, expected growth, and the space needed for recovery operations. Appliances that can run recovered servers also need suitable CPU and RAM. Follow the vendor’s sizing guidance for the specific model and workload rather than assuming that a single storage multiplier covers every requirement.

Daily Oversight & Management

Who owns this day to day? Who rotates media and takes it off site, and how often? Who confirms that backups actually completed, and acts when they do not? Periodic test restorations should also be agreed upon and scheduled. Oversight that belongs to no one tends to fail when it matters most.

Snapshot Configuration

Snapshot intervals are chosen at configuration and can usually be changed later. It is worth knowing yours, and whether they still fit how your business actually works.

Consolidation & Retention Configuration

How often snapshots consolidate, and how long each tier is retained, is the heart of what you can recover. The sample schedule above shows one way to document it clearly.

Potential Consequences of Common Trouble Issues

Backup systems occasionally exhibit problems that require technical intervention, and the priority is usually to restore normal service. The causes vary. Common ones include:

  • Conflicts or issues with third-party software used to create the images.
  • Problems with the backup appliance or the backup software itself.
  • Problems on the target computer that prevent it from being backed up successfully.

In some circumstances, resolving one of these can require deleting some or all of an organization’s backup history and starting anew. It is rare, and every effort is made to avoid it, but management should understand it is possible. Organizations subject to legal holds, special compliance requirements, or other restrictions governing the handling of data should apprise their IT professional(s) of those restrictions in writing.

Potential Consequences of Exceeding Storage Capacity

An organization can surpass its projected growth and push a backup solution past its recommended capacity before its planned end of life. When a device’s capacity is exceeded, the IT professional(s) may have to alter snapshot, consolidation, or retention settings to free the space needed for backups to resume, and granularity can be lost in the process.

Separately, an employee innocently reorganizing files or freeing space on a workstation may temporarily copy a large volume of data to the company’s server. When that happens, offsite replication (where applicable) can slow to a crawl, delaying the backup of legitimate data for weeks or more.

As above, in some situations resolving these problems could require deleting some or all of an organization’s backup history and starting anew. Every effort is made to avoid it, but management should be aware it is possible.

Return to checklists

To review your current backup and retention settings, it is recommended that you consult your Sandbox Technologies Engineer, Consulting CIO, or Account Manager. Not a client yet? Contact us here to get started.

Contact Sandbox Technologies for a free, no-obligation consultation.

Headquartered in Los Angeles. Serving clients nationwide and internationally since 1997.

Nationwide (Toll-Free)

877-930-8324

Los Angeles

424-207-5130

Support Helpdesk

424-207-5140

    By submitting this form you are confirming that you have read and agree to our Privacy Policy

    * NOTE: Hardware purchase requests submitted via this form will not be honored. Hardware sales are facilitated in support of established customer accounts only.