Artist OS 1.0 – Genesis

Overview

A backup retention policy determines which restore points are kept and when older archives may be removed. A clear policy protects important versions of Artist OS without allowing backup files to consume all available storage.

Why retention matters

• Backup archives can grow quickly when uploads and databases increase.
• Full storage may cause future backups or other server functions to fail.
• Keeping only the newest backup provides too little recovery flexibility.
• Keeping every backup indefinitely makes management and restore selection difficult.
• A documented policy helps partners and administrators follow the same recovery process.

Recommended retention model

For most active Artist OS installations, a layered schedule provides a practical balance between recovery options and storage use.

Backups that should not be removed automatically

Some backups represent important milestones and should be excluded from routine cleanup whenever the Backup Manager supports protected archives or labels.

• The backup created before a major Artist OS update
• The final backup before a server migration
• A known stable version after successful testing
• A backup created before major branding, domain or partner changes
• An archive related to an investigated security or data incident

Label important restore points

Use a clear description when labels or notes are available. The name should explain why the backup exists and when it may be removed.

Pre-update backup — Artist OS 1.2 — keep until verified
Stable production version — 21 July 2026
Before partner domain migration — go.example.com

Configure automatic retention

When retention controls are available in your Artist OS version:

1. Sign in with an administrator account.
2. Open Administrator.
3. Select Backup Manager.
4. Open Scheduled Backups or Retention Settings.
5. Choose the maximum number of daily, weekly and monthly backups to keep.
6. Enable automatic removal of expired routine backups.
7. Confirm that protected or manually retained backups are excluded.
8. Save the policy.
9. Review the next scheduled cleanup date.

Review storage usage

Retention limits should be based on actual archive size and available storage, not only on the number of files.

• Compare the size of recent backup archives.
• Allow additional space for temporary files created during backup generation.
• Leave enough free server capacity for application updates and uploads.
• Investigate sudden changes in backup size before deleting older known-good copies.

Keep an off-server copy

Retention on the main server should be combined with secure storage elsewhere. A server-level failure may remove both the live installation and every backup stored beside it.

• Keep at least one recent verified backup outside the production server.
• Store long-term monthly backups in a separate secure location.
• Protect external storage with strong access controls.
• Encrypt archives when they contain sensitive installation data.
• Document who is authorised to download, retain and remove backups.

Manual cleanup procedure

When backups must be removed manually:

1. Confirm that the newest complete backup is available.
2. Verify that important milestone backups are clearly identified.
3. Download any archive that must be retained outside the server.
4. Remove only backups that have expired under the documented policy.
5. Confirm the remaining restore points after cleanup.
6. Record the cleanup when your organisation maintains an administration log.

Review the policy regularly

Reassess the retention policy after major changes to the installation, server plan or partner activity. A policy suitable for a small new installation may become insufficient as uploads, users and database content grow.

Next step

Continue with Disaster Recovery Guide to learn how backups, access details and recovery responsibilities should be prepared before a serious outage occurs.