דילוג לתוכן
Articles and Knowledge Centre / Backup and Recovery

Backup scheduling and version retention: how to match your business needs

How long should a backup be kept— a week, a year, or until someone requests a file we’ve already forgotten existed? There is no single answer that fits every business. Good retention policies and scheduling start with business needs, requirements applicable to the data, and recovery scenarios. Here we will go over…

12.10.2026 · 7 min read
Figure on backup scheduling and version retention: this is how it is tailored to business needs

How long should a backup be kept — a week, a year, or until someone asks for a file we’ve already forgotten existed? There’s no single answer that fits every business. Good retention policies and schedules start with business needs, applicable information requirements, and recovery scenarios. Here we’ll go over the considerations that help define them in an organized way.

Frequency and duration of retention

  • When is a recovery point created?
  • How many versions are kept?
  • When is it permitted to delete?
Key principles at a glance

What to keep, and for how long?

A retention policy explains how long an organization keeps information for operational purposes or to meet applicable requirements. In the backup software described in the source, Retention Policy manages the automatic creation and deletion of copies. Each previous state of a file is called a version.

Several versions can be created over a file’s lifetime, according to the settings. The system tracks file versions and allows them to be managed. A list of previous backed-up versions is kept alongside user files. Retention policy options are available in the backup plan settings. The source refers to further documentation on retention policies and versioning.

Building a policy that fits each data group

To build a useful policy, start by becoming familiar with the information. Go through the following steps — before defining when the system deletes it.

Distinguish between types of information

Backup and retention settings for operating system files, databases, and user documents usually differ. They should be based on internal RTO and RPO, on a recovery or business continuity plan, and on work requirements.

How far back do you want to go, and at what level of detail? A monthly copy may suit one need, while weekly, daily, or hourly copies may suit another. The source also refers to examples of retaining work files and personal files. The choice should match actual use.

Distinguished by lifecycle

Some information needs to be kept for a few weeks and retrieved quickly, and some information needs to be kept for years and then securely deleted. Backups that are needed frequently can be kept locally for quick access; long-term archives can be stored in the cloud in dedicated storage tiers. The question is when and how you will need them.

The source describes support for a separate retention policy for each storage destination in a hybrid backup plan.

Build plans according to data groups

Create a backup plan for each data group you defined in the previous steps.

Define retention in each plan

  • Number of versions to keep: Determine how many previous states of the file should be retained. The source describes a version as a copy of a file that differs from its previous state and is saved in storage.
  • Lifecycle policy for each group: Information retained to meet requirements may be needed for a long period. It can be separated into a dedicated plan and stored in an archive for the required time. The settings may vary according to the type of storage or service layer. Copies that need to be quickly accessed can be kept locally, and long-term archives in the cloud.
  • Deleting information that is no longer needed: The Purge setting allows automatic deletion of old files, unnecessary versions, or files deleted at the local source. This is a flexible and powerful setting, and it should be examined carefully. The source generally recommends keeping at least the last version even when deletion is enabled.

Reviewing the plans and running the backups

In the fifth stage, check the backup plans and the retention settings. In the sixth stage, activate the backups. Further down, the source provides recommendations from the solutions architecture team.

Both time and storage also need planning

Reviewing industry requirements

The source mentions frameworks such as FISMA, HIPAA, PCI, SOX, and GLBA, and emphasizes that retention requirements vary between types of information and industries. It gives an example of seven years of retention for debtor and beneficiary records and tax reports, and five years for customer invoices, attributing this to SOX.

Tailor retention to recovery scenarios

If it may be necessary to access information a year after it has been deleted, retention settings should allow for this — and it should be checked that it is actually preserved. The source also describes Delay Purge, a postponement of the deletion of versions that have reached a certain age. The name sounds promising, but it is important to check what it does in your version.

For example, in the source the retention period is set to one day and the deletion delay to 90 days. After one day the version becomes a candidate for deletion but is preserved for an additional 90 days before deletion. This is an example of the mechanism described in the source; its behavior should be verified in your product version and the settings you use.

Manage the incremental backup chain

The source recommends keeping a chain of a reasonable size of 14 incremental backups and occasionally scheduling a full backup.

Consideration is given to the load on production

Backup of a user on the network and on input and output resources, and therefore it can compete with regular work. Weekly backups can be scheduled outside of working hours or on the weekend; for daily backups, limiting bandwidth can be considered. Employees should not be aware of the backup window based on the time it takes to open a file.

The source describes a Bandwidth Throttle feature in the backup software that allows bandwidth limits to be scheduled, and refers readers to the product documentation for more detail.

The policy should fit your business

When asked how to set up retention, the answer is usually 'it depends.' This is not evasion: the type of information, retention requirements, cost, and recovery needs really change the answer. There is no one-size-fits-all policy. The source refers to its support community for reviewing scenarios with architects, support staff, and backup personnel.

Continue reading