Immutable copies
Once sealed, a copy cannot be edited or deleted until its retention window ends, even by administrators.
No. 05 of 06 · Backup and preservation
Every edition, preserved exactly as it went to press.
Proof Copy Backup keeps editions and proofs as immutable copies, so the version you published is the version you can always prove.
05
- Immutable copies
- Edition snapshots
- Three copies, separate locations
- Point-in-time restore
- Integrity checks
- Retention windows
“A backup you cannot trust to be unchanged is just another copy.”
Ordinary backups are built to rescue you from a bad afternoon. They are not built to answer the harder question: what exactly did we publish, and has anyone changed it since? Files that can be edited can be edited by mistake.
Proof Copy Backup seals each edition at the moment you choose. Sealed copies cannot be modified or deleted during their retention window, they are kept in separate storage locations, and they are checked regularly so that damage is found long before you need the file.
What is inside
The features.
Edition snapshots
Snapshot on a schedule, or the moment a story, issue or project is marked published.
Three copies, separate locations
Each sealed edition is written to three independent storage locations to survive hardware and site failures.
Point-in-time restore
Restore a single file, a folder or a whole edition to exactly how it looked on a given date.
Integrity checks
Checksums are verified regularly, and any mismatch is repaired from a good copy and reported to you.
Retention windows
Choose how long copies are protected, from one year to indefinitely, and review them before release.
How it runs
From first file to filed.
- 1
Define an edition
Choose which folders, projects or tags make up an edition or a proof.
- 2
Set retention
Pick how long the sealed copy must be protected from change.
- 3
Seal the copy
At publication, the edition is written to three locations and locked.
- 4
Restore or export
Retrieve any sealed edition whole, or pull out a single file when you need it.
The fine print, plainly
Specifications
| Copies | Three, in separate storage locations |
|---|---|
| Immutability | No edit or delete during the retention window |
| Snapshot triggers | Schedule, publish event or manual seal |
| Retention | One year up to indefinite |
| Verification | Regular checksum audits with automatic repair |
| Restore | File, folder or full edition to a chosen date |
Reader questions
Asked often.
Can an administrator delete a sealed copy?
Not during its retention window. That is the point: the protection holds even if an account is misused or a mistake is made.
How is this different from regular backup?
Regular backup tracks the current state of your files. Proof Copy Backup keeps fixed, sealed editions that never change, so you can always show what was published.
What if a copy is damaged?
Integrity checks detect it, the damaged copy is replaced from one of the other two, and you receive a report of what happened.
Also in this issue.
Full services index →Name Index Drive
Storage organized by clear names, with naming rules enforced automatically.
Press Room Storage
Editorial team storage for drafts, photos and approvals.
Clip Archive
Searchable long-term archive for articles, clips and records.
Byline Shares
Credit-aware sharing with branded link pages.
Wire Transfer Files
Fast delivery of big media bundles to partners.