The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Back up often enough that the oldest restorable copy is newer than the data loss your business can tolerate. That limit is your recovery point objective (RPO). A static site may need copies after changes and on a recurring schedule, while a busy store or application may require daily, hourly, or near-continuous database protection. A sound small-site baseline combines automated backups, periodic full images, an off-site or offline copy, and documented restore tests.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
There is no universal “daily” rule. Set the interval from the RPO for each important asset, then verify that the resulting restore process also meets your recovery time objective (RTO)—how quickly the site or server must be usable again.
As an Amazon Associate I earn from qualifying purchases.
Start with RPO and RTO, not a calendar
Write down two limits before choosing a schedule:
- RPO: the maximum amount of recent data you can lose after a failure. NIST SP 800-209 defines it as the amount of data that can be lost following a failure.
- RTO: the maximum acceptable time to restore service and make the required data available.
Set these objectives separately for the database, uploaded files, application code, server configuration, certificates, and encryption keys. A site might tolerate losing a day of brochure-text edits but only 15 minutes of paid orders. The stricter asset determines the protection interval for that asset.
| RPO example | Protection implication |
|---|---|
| 24 hours | A successful daily copy leaves no more than one day of intended loss, assuming jobs complete and are monitored. |
| 4 hours | Run or stream protection at least every four hours and confirm that copies are actually restorable. |
| 15 minutes | Use much more frequent database or log capture; a once-daily backup cannot satisfy this objective. |
These are planning examples, not guarantees. Measure the real change rate and ensure the oldest available restore point stays inside the stated window.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
What determines the right frequency?
NIST SP 800-123 notes that backup frequency is determined by several factors. Evaluate all of them rather than choosing an interval because it is conventional:
- Volatility: how often content, code, configuration, or records change.
- Data type and volume: a small configuration file and a large transactional database have different transfer and storage costs.
- Criticality: losing an order, account record, or security key may have greater consequences than losing a replaceable image.
- Available media and backup window: the network, storage, and time available for each job.
- Threat level: ransomware, operator error, account compromise, and hardware failure affect how isolated copies must be.
- Retention, legal, and business requirements: some records need longer preservation or controlled destruction.
NIST’s general pattern is full backups weekly to monthly and incremental or differential backups daily to weekly, subject to the environment’s RPO. Treat that as a starting pattern, not a mandate.
Choose the right backup type
Layering backup types balances recovery speed, storage, and protection against corruption.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Type | What it captures | Strength | Trade-off |
|---|---|---|---|
| Full | The complete selected server, site, or data set at that point in time. | A straightforward recovery baseline and a complete server image. | Consumes more time, bandwidth, and storage than change-only copies. |
| Incremental | Changes since the previous backup. | Efficient for frequent protection and high-change data. | A restore may depend on the full backup and every required incremental in the chain. |
| Differential | Changes since the last full backup. | Recovery generally needs the full backup plus the latest differential. | Each differential grows until the next full backup. |
| Continuous or near-continuous replication | Changes streamed or copied with very small gaps. | Can support a tight RPO for active databases. | Replication can copy corruption, deletion, or ransomware; it is not a substitute for isolated, tested backups. |
Use a full image before major operating-system, database, application, or hosting changes. Combine it with incremental or differential copies so routine jobs do not repeatedly move the entire data set.
Practical schedules by website and server type
The following schedules are editorial starting points synthesized from NIST’s RPO and volatility factors. Adjust them until testing demonstrates that the RPO is met.
| Environment | Starting schedule | What to protect | Important adjustment |
|---|---|---|---|
| Static brochure site | Copy after content or configuration changes, plus a recurring automated copy. | Web files, deployment configuration, certificates, and any content-management data. | Keep several restore points and one off-site copy; shorten the interval if edits are business-critical. |
| Blog or CMS with regular publishing | At least daily database and file copies; increase frequency during active publishing or upgrades. | Database, uploaded media, themes, plugins, code, and configuration. | Take an additional full or image backup before upgrades and schema changes. |
| E-commerce or high-change application | Hourly or more frequent database and log protection when the business cannot recreate that much activity. | Orders, payments-related records, inventory, customer data, files, code, and logs needed for recovery. | Consider continuous protection only after testing its restore process and isolation from production. |
| Server configuration and infrastructure | Full image before major changes and on a recurring weekly-to-monthly cadence appropriate to the environment. | Operating system state, service configuration, firewall rules, deployment definitions, secrets, certificates, and keys. | Store rebuild information securely and verify that a new host can be configured from the protected material. |
A server image alone may not contain everything needed to operate the application. Export databases consistently, preserve deployment and infrastructure configuration, and protect secrets and keys in a controlled store.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Use the 3-2-1 rule, then add isolation
NIST NCCoE’s 3-2-1 guidance means keeping three copies of important data on two media types, with one copy off-site. The production server counts as one copy only if it is supplemented by independent backups.
CISA’s StopRansomware guidance adds two critical properties: maintain offline, encrypted backups and regularly test their availability and integrity. “Offline” means an attacker who compromises production credentials cannot alter or erase the copy. Immutability, write-once retention, a disconnected external drive, or a separately credentialed vault can provide that separation when configured correctly.
A NAS can automate local copies and provide a second media type, but a NAS in the same room or reachable with the same administrator credentials is not, by itself, an off-site or isolated backup. Keep an encrypted copy in a different location and restrict who or what can delete it.
Rank #4
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Set retention as a policy
Retention is not one universal number. Define it by data and log type, business and legal need, security controls, archiving requirements, and documented destruction. A practical policy commonly distinguishes:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Daily restore points for recent operational recovery.
- Weekly and monthly restore points for longer-lived rollback and discovery of slow corruption.
- Event-driven points taken before upgrades, migrations, bulk imports, or other risky changes.
- Archives held only when a business or legal requirement justifies their protection and controlled disposal.
Record the retention period, owner, encryption method, location, deletion authority, and whether a point is immutable. Longer retention increases storage and the number of copies that must be protected and eventually destroyed.
Implement a schedule that can be operated
- Document objectives. Write the RPO and RTO for the site, database, files, configuration, certificates, and keys. Note assumptions such as maximum tolerable transaction loss and the host on which recovery will occur.
- Automate jobs and monitoring. Schedule full, incremental, differential, database, and log protection as selected. Alert on failed, partial, late, or unexpectedly small jobs; a green scheduler entry is not proof that usable data was captured.
- Build independent copies. Keep at least three copies on two media types, with one off-site. Encrypt copies and isolate one from production credentials, as recommended by NIST NCCoE and CISA.
- Apply retention. Create daily, weekly, monthly, and event-driven restore points according to the policy for each data class. Ensure automatic pruning cannot delete the only copy that meets a legal or operational requirement.
- Test recovery. Perform a file restore, a database restore, and a complete rebuild on a documented cadence. Record elapsed recovery time, data consistency, configuration gaps, and any failed step; fix the process and test again.
- Revisit after change. Reassess the schedule after a major application, hosting, database, architecture, or threat change. A new transaction rate or ransomware risk can invalidate an older RPO and isolation design.
Prove that backups restore
A backup that completed successfully can still be unusable because of an incomplete database dump, missing encryption keys, a broken dependency, an expired certificate, or a restore procedure nobody has practiced. NIST SP 800-209 calls for periodic restore tests against the required recovery time and health validation of backup copies. CISA likewise calls for regular availability and integrity testing.
Best Value
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Test at three levels:
- File-level: restore representative uploads, configuration files, and certificates; verify permissions, timestamps where relevant, and application readability.
- Database-level: restore to an isolated environment, run consistency checks, and confirm that expected records and relationships are present.
- Full rebuild: provision a clean server or recovery environment, apply the image and change sets, restore the database, reconnect dependencies, and measure time to a functioning site.
Keep the test environment separate from production so a rehearsal cannot overwrite live data. NIST SP 800-209 offers a validation heuristic of roughly one to 1.5 orders of magnitude fewer validation samples than backup frequency; for example, hourly copies could be validated daily. Use that as a planning heuristic, while testing immediately after major changes and after any failed or suspicious job.
Common scheduling mistakes and corrections
- Using “daily” for every site: map the interval to the RPO and transaction rate instead.
- Keeping only one local copy: add a separate medium and an off-site, isolated copy.
- Treating replication as backup: retain historical, immutable or offline points because replication can reproduce deletion or corruption.
- Backing up files but not the database: export the database consistently and test application-level recovery.
- Ignoring keys and configuration: protect the material needed to decrypt data and rebuild services, not just web content.
- Never measuring restoration: record actual recovery time and compare it with the RTO.
- Letting alerts go unread: assign an owner and escalation path for failed or incomplete jobs.
Decide whether to tighten the interval
Ask how much new data appears between successful restore points and whether that data can be recreated. If losing a day of publishing is acceptable, daily protection may fit. If losing even one hour of orders creates financial, contractual, or regulatory harm, move database and log protection to hourly or more frequent intervals and verify that the recovery process can handle the volume.
Then check the opposite constraint: can the infrastructure complete each job, retain enough history, and isolate copies at that rate? If not, reduce the amount copied per job with incremental or log-based protection, add capacity, or revise the documented RPO with the business owner. The final schedule is the shortest interval that is affordable, operable, isolated, and demonstrated by restore testing to meet the stated objectives.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
