Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The reliable approach is a tested, layered recovery plan—not a single synced folder. Identify the drawings, models, schedules, contracts, change records, applications, and credentials your business must have to continue; keep several encrypted copies with at least one disconnected from ordinary network access; protect cloud copies against deletion and account compromise; and regularly restore representative data into a clean environment. This sequence follows the general guidance in the Cybersecurity and Infrastructure Security Agency (CISA) #StopRansomware Guide and related advisories. CISA has not issued a construction-specific backup standard, so your project inventory, recovery priorities, retention periods, and test schedule must reflect your own contracts and operations.
Start with the recovery outcome, not the backup tool
After ransomware or another attack, the question is not whether a backup job reported “successful.” The question is whether your team can open the right project information, verify that it is complete, and resume critical work without re infecting clean systems. Define that outcome with operations leaders, project managers, and IT before selecting storage or software.
CISA’s #StopRansomware Guide states: “Maintain offline, encrypted backups of critical data, and regularly test the availability and integrity of backups in a disaster recovery scenario.” Apply that sentence as four design requirements:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Critical: rank the information and services that affect safety, contractual commitments, billing, and active field work.
- Offline or strongly separated: keep at least one copy outside routine production access.
- Encrypted: protect backup data at rest and in transit, with keys and permissions controlled separately from everyday users.
- Tested: perform actual restores and confirm that files, versions, permissions, and dependencies work.
A folder copied somewhere is only one component. A recoverable project may also require the software that opens a model, license or identity configuration, reference files, fonts, plug-ins, database exports, templates, and system settings. Document those dependencies while the environment is healthy.
#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.
Inventory every place project information lives
Make the inventory business-specific. Walk through how a project moves from estimating to design, procurement, construction, closeout, and warranty work. Record where each record is created, who owns it, how often it changes, and what would happen if it disappeared.
| Information or system | Examples to identify | Dependency questions |
|---|---|---|
| Design files | Current drawings, markups, models, specifications, renderings, and survey data | Which applications, versions, plug-ins, fonts, coordinate systems, and reference links are required to open them? |
| Planning and field records | Schedules, daily reports, inspection forms, photographs, RFIs, submittals, punch lists, and safety records | Are records held in a database or platform that also needs configuration, export files, or identity access? |
| Commercial records | Contracts, bids, purchase orders, change orders, payment applications, and correspondence | Which files are legally or contractually significant, and which retention period applies? |
| Shared and local storage | File servers, network shares, workstation folders, laptops, removable media, and office NAS devices | Who administers each location, and can an attack on a user account reach the backup copy? |
| Cloud services | Project-management platforms, document repositories, email, identity providers, and object storage | What can be exported, versioned, undeleted, or restored, and who controls those settings? |
| Recovery components | Application installers, license details, configuration files, virtual-machine images, scripts, and contact lists | Could the project data be unusable without a clean operating system, database, or specialized viewer? |
Assign an owner to every system and note the projects or business functions affected by its loss. Keep the inventory itself in a location attackers cannot alter, such as a printed emergency binder plus a separately protected copy. Review it when a platform, file server, project phase, or software version changes.
Choose recovery priorities with operations
Do not let IT rank files in isolation. A project executive, superintendent, design lead, finance representative, and IT administrator should agree on what must return first. Separate “needed to operate today” from “important but recoverable later.” For each priority, record the latest acceptable version, the people who validate it, and the dependencies required to use it.
- Tier 1—life-safety and active production: information required for current field decisions, approved drawings, critical schedules, safety documentation, and access to essential communication.
- Tier 2—contract and cash flow: executed contracts, change records, payment documentation, procurement data, and records needed to substantiate claims.
- Tier 3—continuity and history: older revisions, completed-project archives, training material, and reference libraries.
These tiers are an internal planning framework, not a CISA-prescribed construction classification. CISA’s general guidance is to understand critical assets, data, systems, and dependencies and prioritize restoration accordingly. Include the software or system image needed to use each tier; restoring a drawing without its referenced files or a database without its application may not restore the business function.
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.
Build separated copies instead of trusting one location
Use multiple copies that do not share the same account, network path, administrator, physical location, or failure mode. CISA’s LockBit advisory summarizes the familiar 3-2-1 pattern—three copies, on at least two types of media, with one copy kept off-site—and emphasizes physically separate, segmented, secure copies. Treat 3-2-1 as a resilience pattern, not proof that any particular arrangement is safe.
| Copy type | Access separation | Strengths | Risks and controls |
|---|---|---|---|
| Production-adjacent backup | Online, but administered separately from working shares | Fast recovery of individual files and frequent snapshots | Ransomware may reach it through shared credentials or network paths. Use separate administration, least privilege, multifactor authentication, and restricted write access. |
| Cloud backup or object storage | Remote account or environment; versioning and delete protection where supported | Geographic separation and scalable retention | A synchronized cloud folder can mirror encryption or deletion. Understand the provider’s shared-responsibility model and maintain an independent recovery path. |
| Immutable retention | Objects cannot be changed or deleted during a defined retention period | Resists routine tampering and some ransomware deletion attempts | Incorrect retention or legal-hold settings can block legitimate cleanup or create compliance problems. Test the exact configuration and approval process. |
| Disconnected removable copy | Offline when not actively performing a backup | Isolated from network attacks and practical for locally stored project data | A single drive is a single point of failure. Rotate more than one encrypted drive, store them securely, and verify restores. |
An external hard drive is therefore a category of backup media, not a complete strategy. CISA’s device-data guidance warns against leaving an external drive connected when it is not being used for backup. Disconnect it after the job, keep it in a controlled location, and protect it from theft, fire, moisture, and unauthorized access. Rotate copies so one failed or damaged drive does not eliminate the only offline version.
Encrypt backups and separate the keys
Encrypt data before it leaves a workstation or server and use the storage service’s encryption controls where appropriate. Protect encryption keys, recovery phrases, and administrative credentials separately from the backup files. If an attacker obtains both the encrypted copy and its key through the same identity system, encryption may not provide meaningful separation.
- Use unique administrator accounts for backup infrastructure; do not reuse domain-wide administrator credentials.
- Require multifactor authentication for cloud consoles and backup management.
- Give ordinary project users read or restore access only when needed; reserve deletion and retention changes for a small, monitored group.
- Record who can unlock an offline drive or approve an immutable-retention change, with an emergency alternative if one person is unavailable.
- Log backup deletions, policy changes, failed jobs, and unusual download or restore activity.
Encryption does not replace physical security or access control. A lost drive with an exposed password is not an offline safeguard, and a perfectly encrypted cloud vault can still be deleted by a compromised administrator.
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.
Set a cadence that matches project change
Choose frequency by asking how much work the business can afford to recreate after losing the latest copy. Active coordination models, daily reports, and change records may need more frequent capture than a closed-project archive. Define retention by contractual, legal, insurance, and operational requirements, then confirm that the chosen service can actually keep and restore the required versions.
CISA’s LockBit advisory describes maintaining backups and backup restoration regularly and summarizes “daily or weekly at the minimum” in that advisory context. That interval is not a universal construction rule. A firm with rapidly changing active projects may need multiple recovery points per day, while a historical archive may use a different schedule. Whatever cadence you select, monitor missed jobs and investigate them instead of silently accepting the last successful copy.
Implement the backup runbook
Write a procedure that a trained employee can follow without relying on an administrator’s memory. The following sequence can be adapted to your platforms.
Free tools Windows power users keep installed
One-click scans. No signup required.
- List sources and owners. Enumerate workstations, servers, shared drives, project platforms, cloud accounts, databases, and configuration repositories. Name the person responsible for confirming each source is included.
- Define the recovery set. For every priority tier, list files, databases, application installers, license information, system images, templates, and reference data. Specify the newest acceptable version and the person who will validate it.
- Configure protected destinations. Use a separately administered backup account or environment, enable versioning or delete protection where available, and configure immutable retention only after legal and operational review.
- Create the offline rotation. Connect an encrypted external drive or other removable medium only for the backup window. Confirm the job completes, safely eject the medium, label it with date and scope, and store it securely away from the production network.
- Verify completion. Check logs, file counts, changed-file reports, and alerts. A green status without examining exclusions or authentication failures is not verification.
- Record the run. Note the date, source systems, backup destination, operator, exceptions, and where the recovery credentials and contact list are kept offline.
- Escalate failures. If a source was unavailable, a quota was exceeded, or files were excluded, assign an owner and deadline. Do not mark the business protected until the missing data is covered.
Keep a copy of this runbook outside systems that could be encrypted during an incident. Include vendor support contacts, internal approvers, building access details, and the sequence for isolating affected networks.
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)
Test that project backups really restore
CISA calls for regular testing of backup availability and integrity and for testing backup procedures. A completed job proves only that data was transferred; it does not prove that a model opens, a database is consistent, or a user can recover the needed revision.
- Select representative samples. Include a current drawing set, a large model with external references, a schedule or database export, a contract document, photographs, and files from each critical platform.
- Restore to an isolated test environment. Use a clean workstation or virtual machine that is not connected to potentially compromised production systems. Never test by overwriting the live project.
- Check integrity and usability. Open files in the required application versions, inspect references and links, verify timestamps and revisions, confirm permissions, and compare checksums or platform integrity reports where available.
- Measure the practical result. Record elapsed time, staff effort, bandwidth, licensing obstacles, missing dependencies, and the largest dataset that can be restored within the business’s tolerance.
- Document and correct findings. Update the inventory, runbook, credentials, software images, and retention settings. A failed test is a defect to fix, not a reason to stop testing.
Set an interval based on change frequency and risk. CISA requires regular testing but does not specify one universal interval for every construction business. Test after major platform migrations, identity changes, retention-policy changes, and any incident that alters the backup environment.
Cloud-synced files are not automatically ransomware protection
Synchronization usually reproduces changes: encrypted files, mass deletions, or corrupted revisions can be synchronized as well. Cloud storage can be part of a resilient design only when you understand its shared-responsibility boundaries and configure recovery features deliberately.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Determine whether the service offers independent version history, point-in-time recovery, recycle-bin retention, legal hold, or delete protection.
- Use a separate cloud account or administrative environment for backups when practical, with multifactor authentication and no standing access from ordinary project accounts.
- Consider cloud-to-cloud backup or export so the only copy is not inside the same provider, identity tenant, or failure domain.
- Evaluate immutable storage carefully. Retention locks can help against deletion but can also prevent required changes or create compliance obligations if configured incorrectly.
- Perform a full restore exercise from the cloud copy, including a scenario in which the primary tenant or administrator account is unavailable.
Ask the provider who is responsible for retention, encryption keys, service availability, account recovery, and geographic location. Obtain those answers in writing and reflect them in your incident plan.
Best Value
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Restore after an attack without reintroducing it
Preserve evidence and coordinate with your incident-response lead, insurer, legal counsel, and relevant authorities before making destructive changes. Do not reconnect a suspected-compromised computer merely to retrieve a file.
- Contain the incident. Isolate affected endpoints, servers, and accounts according to your response plan. Disable suspected credentials and preserve logs; avoid actions that destroy forensic evidence unless safety requires them.
- Establish a clean recovery zone. Rebuild or verify operating systems, identity services, network controls, and security tools from trusted sources. Apply patches and change credentials before connecting restored data.
- Confirm backup provenance. Select an offline or separately protected copy whose creation time predates the compromise. Check backup logs, hashes, version history, and signs of unauthorized deletion or encryption.
- Restore Tier 1 data and dependencies. Recreate the clean application, database, licensing, and configuration components needed to use the files. Restore the smallest useful set first, then have the business owner validate it.
- Validate before expansion. Scan restored files, inspect models and references, check permissions, and monitor the clean environment for suspicious activity. Do not restore every archive until the initial set is trusted.
- Restore subsequent tiers. Bring back commercial records and historical material in the priority order agreed before the incident. Keep a written record of what was restored, from which version, and by whom.
- Resume normal operations gradually. Reconnect users with least privilege, rotate credentials, maintain heightened monitoring, and schedule a post-incident review that updates the backup and recovery runbook.
Compare approaches using recovery evidence
| Approach | Access separation | Recovery speed and scope | Confidence depends on | Operational fit |
|---|---|---|---|---|
| Network backup repository | Online; can be separately administered | Usually efficient for individual files and frequent snapshots | Isolation from production credentials, versioning, and successful restore tests | Frequent changes and centralized IT control |
| Cloud backup with protected versions | Remote; separation varies by account and provider | Scales across offices and projects; large restores depend on bandwidth and export capability | Shared-responsibility review, account recovery, retention, and a tenant-loss exercise | Distributed teams needing geographic separation |
| Immutable object retention | Strong against modification during the lock period | Good for defined recovery points; restoration may require a separate clean environment | Correct retention, legal review, and tested retrieval permissions | Organizations able to manage policy and retention complexity |
| Disconnected drive rotation | Offline between backup runs | Direct for local files; slower for large teams or many systems | Drive rotation, encryption, physical security, and actual restore tests | Small or mid-sized offices and local datasets as one layer |
Choose a combination based on project-data volume, change rate, retention obligations, access controls, geographic needs, and the dependencies your team can restore. No row is a universal winner, and a single copy—regardless of medium—is not a complete recovery design.
Common failure modes and fixes
- The “backup” is a synchronized folder. Add independent versioned or immutable copies and a disconnected rotation.
- The external drive stays plugged in. Eject it after each run and store it offline; rotate another encrypted drive for the next run.
- Only project folders are copied. Add application versions, databases, reference files, templates, licenses, configuration, and system images required to open them.
- Every copy uses the same administrator account. Separate accounts, require multifactor authentication, and restrict deletion rights.
- Jobs report success but exclude files. Review exclusions, permissions, quotas, and logs; test representative files rather than trusting a status badge.
- No one knows what to restore first. Publish the tiered priority list and keep it, contacts, and credentials accessible outside affected systems.
- Immutable retention is enabled without review. Confirm retention, legal, and deletion implications before locking objects.
- Restoration is tested on production. Use an isolated clean environment and document the result, elapsed time, and missing dependencies.
Maintain an offline recovery checklist
- Current inventory of project data, owners, dependencies, and priority tiers
- Backup destinations, account identifiers, retention settings, and encryption-key recovery instructions
- Offline copy locations, rotation dates, and physical-access contacts
- Application installers, licenses, system images, configuration exports, and trusted recovery media
- Incident-response, insurer, legal, cloud-provider, and internal escalation contacts
- Latest restore-test reports, unresolved defects, and the next scheduled exercise
Review the checklist whenever a project platform, identity system, storage location, or major software version changes. A recovery plan remains useful only when its copies, credentials, dependencies, and contact information match the environment your crews actually use.
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.
