Keep more than one copy, on more than one kind of storage, with at least one copy away from your main location. Then test a restore. A backup you have never restored is only a hope.
This guide covers video libraries you manage. FAST-VID does not back up, synchronize or upload your files. It prepares a supported public-link file that your browser saves locally; the backup system is your responsibility.
The 3-2-1 strategy, without the guarantees
CISA describes the 3-2-1 rule as a trusted guideline: keep three copies of important files, on two different types of storage media, with one copy off-site. The primary file plus two backups is the usual interpretation.
The rule helps with drive failure, accidental deletion and a local disaster, but it is not a guarantee. Ransomware, stolen credentials, a bad sync or a fire can still affect multiple copies if they are not isolated and tested. Treat 3-2-1 as a baseline to adapt, not a certificate of safety.
| Copy | Example | Purpose |
|---|---|---|
| Primary | Working drive or NAS | Everyday access and editing |
| Local backup | External drive kept separately | Fast restore after drive failure |
| Off-site backup | Cloud or drive at another location | Protection from local loss or damage |
Local, external and off-site copies
A second folder on the same drive is not a backup. Use a different device or medium, and keep it disconnected or offline when it is not in use. An external drive is convenient but can be lost, stolen, dropped or damaged along with the computer.
An off-site copy can be a cloud service or a drive stored at another trusted location. Cloud storage is convenient, but it is not automatically a backup: a sync client can propagate deletion, and an account compromise can affect the cloud copy.
For a large library, a NAS can hold the primary copy and a USB drive can hold a rotating backup. Keep at least one copy outside the same power, network and physical risk area.
Cloud backup versus synchronization
Sync keeps devices aligned. If you delete a video locally and the deletion syncs, the cloud copy may disappear too. A backup service should preserve a separate restorable version for a defined retention period, even if the source changes.
Some consumer cloud plans offer both sync and version history; neither is necessarily a full backup. Check what is retained, for how long, whether deleted files count against quota, and whether you can restore a previous version without the sync client overwriting it again.
For important material, use a backup method that you can disconnect or make read-only. A sync folder that is always mounted is exposed to the same mistakes as the working folder.
Checksums and file integrity
A checksum is a fixed-length value computed from a file's bytes. Comparing checksums before and after a copy, or between two copies, can detect an unexpected change. Common tools include Get-FileHash on Windows and sha256sum on Linux; macOS and other Unix-like systems may provide shasum.
A checksum detects differences; it does not repair a damaged file. If two copies differ, you need a known-good source or another copy to restore from. A matching checksum also does not prove the file is playable, so test playback.
Record the checksum and the date it was taken. Recompute it after moving files or restoring a backup. Do not rely on a checksum alone as your only integrity control.
Versioning and accidental deletion
Version history can recover an overwritten edit, but retention is finite and provider-specific. It may not cover a deleted file after the trash retention period, and a sync client can overwrite a restored version if it is still active.
Keep a separate archive copy of completed projects, and do not let the only historical copy live inside the same sync account. For important projects, keep an offline copy and a documented restore procedure.
Before deleting a library folder, confirm that the backup copy is complete and independent. Emptying a local trash does not necessarily delete a cloud copy, and deleting a cloud copy does not necessarily delete a local backup.
Test a restore
Pick a small file and a representative large file, restore them to a different folder, and open both. Check duration, audio and the expected resolution. CISA recommends testing backups so that restoration is proven rather than assumed.
A restore test can reveal a missing password, a disconnected drive, an expired cloud session or a backup that contains only placeholders. Fix the process before you need it in an emergency.
Document where the backup lives, how to unlock it and who can access it. Store recovery credentials separately from the backup so one loss does not take both.
Format and player compatibility over time
A file can survive on disk and still become inconvenient to play if the software that understands it disappears. MP4 is widely supported, but the codec inside matters and player support changes. Keep a note of the codec, and keep a player or conversion path available.
Do not assume any medium lasts a fixed number of years. Drives, flash, discs and cloud services all have failure modes and provider risks. Refresh copies periodically and verify them.
For a long-term archive, keep the original file and a checksum, document the format, and test playback on a current system. Conversion may be useful for access, but preserve the original if you need fidelity.
Retention, encryption and privacy
Backups can contain personal or licensed material. Encrypt sensitive backups and protect the keys. An unencrypted external drive is easy to read if it is lost; a cloud backup depends on the provider's security and your account security.
Check how long the provider retains deleted data, where it stores it and who can access it. Use multi-factor authentication and a recovery method you control. Do not upload material you are not authorized to store.
FAST-VID does not create, encrypt or retain a backup for you. Its 500 MB output limit applies to the prepared file, not to your backup capacity or retention plan.
Frequently asked questions
What is the 3-2-1 backup rule?
Keep three copies of important files, on two different storage media, with one copy off-site. It is a useful baseline, not a guarantee.
Is cloud sync a backup?
No. Sync mirrors changes and can propagate deletion. A backup should preserve a separate restorable copy with its own retention.
What does a checksum do?
It detects whether file bytes changed. It does not repair a damaged file or prove that a player can open it.
How often should I test a restore?
Regularly enough that you trust the process and know the steps. Test after changing drives, cloud services or backup software.
Does FAST-VID back up my downloads?
No. FAST-VID does not back up, synchronize or upload a library. You choose the storage and backup method.
Sources and references
- CISA: Back up business data and the 3-2-1 rule
- CISA: Data backup options
- Microsoft: Get-FileHash
- GNU Coreutils: sha2 utilities
- FAST-VID: Cloud storage for video files
Try FAST-VID
Open the FAST-VID downloader for a supported public link, then back up the saved file with your own tools. FAST-VID does not create, synchronize or verify backups.