Free tools Windows power users keep installed
One-click scans. No signup required.
Back up often enough that the oldest restorable copy is never older than the data loss your site can tolerate. A static game-news site may need a copy after each content or configuration change, while a store, community, or live-service application may need daily, hourly, or near-continuous database protection. Set a recovery point objective (RPO), automate backups to meet it, keep an isolated off-site copy, and prove the plan with 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.
Start with RPO and RTO, not a calendar
Your backup interval should be the result of two business decisions:
As an Amazon Associate I earn from qualifying purchases.
- Recovery point objective (RPO): the maximum amount of 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.
- Recovery time objective (RTO): how quickly the website, server, database, and supporting services must be working again.
If your RPO is four hours, a job that runs once per day is inadequate: a failure immediately before the daily job could erase almost 24 hours of changes. An hourly copy provides a shorter theoretical loss window, but only if the job completes, the copy is usable, and you can retrieve it during an outage. RTO affects the design as well. A compressed archive may satisfy an RPO but take too long to download and rebuild for a site that must return online in minutes.
Write separate RPO and RTO values for the assets that matter to your operation: web files, databases, uploaded media, server configuration, certificates, encryption keys, deployment files, and logs. A game site might tolerate recreating an old article image, but not losing paid orders, account changes, moderation actions, or leaderboard updates.
#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.
How often should different websites back up?
The following are starting schedules, not universal mandates. NIST SP 800-123 says backup frequency depends on volatility, data type and volume, available media and time, criticality, and threat level. Measure how quickly your data changes and shorten the interval until it fits the documented RPO.
| Website or workload | Practical starting schedule | What to protect |
|---|---|---|
| Static brochure, portfolio, or small game-community landing site | Run an automated periodic copy and create an additional copy after every content or configuration change. | Web files, media, deployment configuration, domain and TLS certificate records, and the hosting configuration needed to rebuild. |
| Blog or CMS publishing regularly | At least daily database and file copies; increase frequency during heavy publishing, migrations, or upgrades. | Database, themes and plugins, uploaded media, environment variables, and administrator configuration. |
| E-commerce, membership, or other high-change application | Hourly or more frequent database and log protection when the business cannot recreate that much activity. | Orders, payments and inventory records, user accounts, sessions where needed, application files, and transaction logs. |
| Live-service or highly transactional game backend | Use continuous or near-continuous replication only after verifying its restore and isolation properties; otherwise use a tested interval that meets the RPO. | Primary databases, write-ahead or transaction logs, object storage, queues, service configuration, and secrets. |
| Server and infrastructure configuration | Take a full image before major changes and on a recurring weekly-to-monthly cadence appropriate to the environment. | Operating-system state, web-server and database settings, infrastructure definitions, certificates, keys, and secure rebuild documentation. |
A “daily backup” can still fail your RPO if the site changes faster than expected. Review the schedule after a new game launch, a traffic surge, a database migration, a hosting move, or a change in ransomware risk.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the right backup layers
No single backup type is ideal for every recovery. Layering reduces both recovery time and the chance that one damaged set leaves you without a usable copy.
Full backups
A full backup captures the selected server or data set at a point in time. It is the simplest source from which to rebuild and is useful before upgrades, migrations, or major configuration changes. Full jobs consume more storage, bandwidth, and processing time than change-only jobs, so many environments run them weekly to monthly and use smaller jobs between them, subject to the RPO.
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.
Incremental backups
An incremental backup records changes since the previous backup, whether that previous job was full or incremental. It minimizes each job’s time and storage requirement, which makes daily or more frequent protection practical. Restoration can require the last full backup plus every required incremental set, so your restore procedure must preserve chain order and verify that no set is missing or corrupt.
Differential backups
A differential backup records changes since the last full backup. Each differential grows until the next full job, but a restore generally needs only the full backup and the latest differential. This trades more storage and transfer capacity for a simpler, often faster recovery than a long incremental chain.
Database and transaction-log protection
For a database-driven site, copying only web files is not enough. Back up the database on the interval required by the RPO and protect transaction or write-ahead logs when the database engine supports point-in-time recovery. Logs can reduce the gap between full database snapshots, but they also require consistent retention, secure storage, and a tested replay procedure.
Images, uploads, and configuration
Keep user uploads and generated assets with the database schedule that governs their references. Capture web-server settings, scheduled jobs, environment variables, deployment manifests, DNS information, certificates, keys, and dependency versions. A database restored without the application version and configuration that can read it is not a complete recovery.
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.
Apply the 3-2-1 rule with isolation
The NIST National Cybersecurity Center of Excellence describes the 3-2-1 pattern: maintain three copies of the data, on two media types, with one copy off-site. The production server counts as one copy only if a second and third copy are independently recoverable.
- Three copies: production plus two backup copies gives you alternatives when one copy is corrupted or unavailable.
- Two media types: combine storage classes, such as production storage and removable or object-based backup storage, rather than placing every copy on one device or volume.
- One off-site: keep a copy in another location or failure domain so a datacenter, fire, or regional incident cannot remove every copy.
CISA’s StopRansomware guidance adds two properties that matter during an attack: keep critical backups offline and encrypted, and regularly test their availability and integrity. “Offline” means an attacker using production credentials cannot directly modify or delete the copy. A NAS connected to the same administrative domain can automate jobs, but it is not by itself an off-site or isolated backup. Use separate credentials, restrict network access, encrypt data in transit and at rest, and consider immutable retention where your storage system supports it.
Set retention by purpose, not one arbitrary number
Retention answers a different question from frequency: how far back can you recover? NIST guidance recommends defining retention by data and log type, business and legal needs, protection requirements, destruction, and archiving.
A workable policy can have several tiers:
- Short-term points: frequent incrementals or database/log copies for recent mistakes and outages.
- Daily points: a rolling set for ordinary operational recovery.
- Weekly or monthly points: longer-range recovery from slowly discovered corruption or an administrator mistake.
- Event-driven points: a protected full copy before a software upgrade, schema migration, hosting change, or major content import.
- Archive points: records retained for contractual, regulatory, tax, or business reasons, with a documented destruction date and access controls.
Long retention increases storage cost and the amount of sensitive information exposed if a backup is stolen. Short retention can make an undetected compromise impossible to unwind. Document who approves retention, who can delete copies, how legal holds work, and how encryption keys are recovered.
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)
Build a schedule that runs without guesswork
- Inventory recoverable assets. List sites, databases, object storage, code, configuration, certificates, secrets, queues, and external services. Record owners and dependencies.
- Write RPO and RTO values. State the tolerated data loss and restoration time for each asset, including a complete rebuild rather than only a file download.
- Select backup layers. Combine full images with incremental or differential jobs, and add database or transaction-log protection where point-in-time recovery is required.
- Automate and monitor. Schedule jobs, encrypt the output, send it to a separate location, and alert on failures, partial completion, missed windows, unusual size changes, and expired credentials. A backup that silently stopped is not protection.
- Separate access. Use backup credentials that production administrators and applications do not share. Limit deletion rights, require stronger authentication, and isolate at least one copy from routine network access.
- Define retention and rotation. Keep the daily, weekly, monthly, and event-driven points your business needs. Ensure the retention period is longer than the time in which corruption or compromise could remain undetected.
- Document recovery runbooks. Include where copies are stored, how to obtain keys, how to rebuild the server, how to restore the database and files, how to update DNS, and how to validate the application.
- Test and improve. Schedule restores, record elapsed time and failures, and change the design when the measured result misses the RTO or RPO.
Test whether the backups actually restore
Successful backup-job status proves only that data was written. NIST SP 800-209 calls for periodic restore tests against the required recovery time and health validation of backup copies; CISA likewise recommends regular availability and integrity testing.
Test three recovery scopes
- File restore: retrieve a deleted configuration file, media asset, or game-community upload and verify permissions, ownership, and checksums.
- Database restore: restore to an isolated environment, replay logs if used, run consistency checks, and confirm that expected records and timestamps are present.
- Complete rebuild: provision a clean server, install the documented dependencies, restore configuration and secrets, load files and the database, then exercise login, publishing, payments, APIs, background jobs, and monitoring.
Record the start and finish time, the backup point used, missing dependencies, data loss measured against the RPO, and the steps that required undocumented knowledge. Keep the test environment isolated from production so a test cannot overwrite live data.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Choose a validation cadence
NIST SP 800-209 offers a heuristic of roughly one to 1.5 orders of magnitude fewer validation samples than the backup frequency. In practical terms, hourly copies might be validated daily, while less frequent jobs can be checked on a correspondingly longer cycle. This is a planning heuristic, not a substitute for risk-based testing: test more often after a platform change, a failed job, a security incident, or a change to the restore process.
Diagnose common backup failures
“The job succeeds, but the site will not start”
The copy may omit environment variables, certificates, file permissions, database extensions, scheduled jobs, or external-service credentials. Add those dependencies to the inventory and perform a clean-server rebuild test.
Best Value
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
“Backups exist, but ransomware deleted them”
Production credentials may have write or delete access to every copy. Move one copy to an offline or immutable target, use separate credentials, encrypt it, and test that recovery personnel can access the keys without granting production systems deletion rights.
“The restore is too slow”
Your RTO may require a different design: a more recent full image, shorter incremental chains, faster storage, prebuilt infrastructure, or a standby environment. Measure download, decompression, database replay, DNS changes, and application validation separately.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors“Storage costs keep rising”
Classify data by RPO and retention need, use incremental or differential protection between full backups, compress and deduplicate where appropriate, and expire copies according to the approved policy. Do not reduce frequency or delete long-range points until the owner confirms that the resulting RPO and retention still meet business requirements.
“The database copy is inconsistent”
Use the database engine’s supported backup or snapshot mechanism, coordinate application quiescence when required, and include transaction logs for point-in-time recovery. A filesystem copy made while the database is writing may not be a usable database backup.
When to revisit the schedule
Review backup frequency, retention, isolation, and restore tests after a major application release, database or hosting change, traffic or transaction increase, new legal requirement, security incident, or change in the cost or availability of storage. Recalculate the real change rate and confirm that the oldest available restore point remains inside the RPO during the busiest period, not merely during a quiet week.
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.
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 →
