What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The reliable approach is a recovery system, not a single copy of a project folder: inventory the files and software each critical job needs, keep several encrypted copies with at least one offline or otherwise isolated, test that real files open after restoration, and recover in priority order on clean systems. This applies CISA’s general ransomware guidance to construction workflows; the cited guidance is not a construction-specific backup standard.
Define what “recovered” means for a construction business
A backup is useful only if the team can resume the work that matters. A drawing file restored without its references, a model without the software and libraries that open it, or a contract database without its configuration may be technically present but operationally unusable.
As an Amazon Associate I earn from qualifying purchases.
Start by agreeing with project and operations leaders which business functions must return first. Record the acceptable amount of recent work that could be recreated and the order in which projects or departments would be brought back. That decision determines backup frequency, retention, storage capacity, and the time spent testing.
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 minuteCISA’s #StopRansomware Guide says: “Maintain offline, encrypted backups of critical data, and regularly test the availability and integrity of backups in a disaster recovery scenario.” Treat that as the governing principle, then adapt the inventory and priorities to your company’s actual projects and systems.
#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 project information and its dependencies
Make the inventory business-specific. Ask project managers, estimators, field supervisors, accounting staff, and IT personnel where information is created, edited, shared, and archived. Include cloud accounts and locally attached devices, not just the main file server.
| Information or system | Examples to record | Dependencies to document |
|---|---|---|
| Current design files | CAD drawings, PDFs, specifications, markups, reference files | Authoring software, fonts, plug-ins, linked files, license access |
| Building-information models | Model files, families, textures, point clouds, exports | Modeling application version, shared libraries, templates, worksharing configuration |
| Schedules and field records | Baseline schedules, daily reports, photos, inspection logs, punch lists | Project-management platform, database, mobile synchronization, user permissions |
| Commercial records | Contracts, bids, subcontracts, change orders, pay applications, correspondence | Accounting or document-management system, search indexes, signing records, retention rules |
| Operational configuration | Server settings, scripts, templates, license files, identity configuration | Operating-system images, credentials held in a separate secure process, network dependencies |
For every item, note its owner, location, format, last known good version, change frequency, and the projects or business functions affected by its loss. Record whether it is authoritative or merely a synchronized copy. Also list dependencies that are not inside the folder: software installers, version-specific templates, source materials, databases, and system images may be needed to use the restored data. CISA’s asset-prioritization guidance supports this dependency mapping; it does not prescribe this particular construction inventory.
Keep a printed or otherwise separately stored copy of the inventory, recovery priorities, and contacts. If the only copy is in the identity system or file server that an attacker can disable, it will not help during the incident.
Recommended Free Tools
Build a backup design with separation and diversity
Use multiple copies that do not all fail in the same way. CISA guidance describes physically separate, segmented, secure copies and summarizes the familiar 3-2-1 pattern: at least three copies, on at least two types of storage, with at least one copy offline or otherwise isolated. The count is a design target, not proof of safety; three copies in one compromised account or building are still one failure domain.
| Copy | Typical role | Access separation | What to verify |
|---|---|---|---|
| Production data | Daily work on servers, workstations, and project platforms | Online and exposed to ordinary credentials | Not treated as a backup; changes and deletions must be captured elsewhere |
| Fast recovery copy | Recent file or system recovery | Separately administered account, network segmentation, or protected repository | Version history, deletion protection, and access logging |
| Offline copy | Recovery if connected systems and accounts are compromised | Disconnected between backup runs and stored securely | Readable media, encryption key availability, and a documented rotation process |
| Separate-location copy | Protection from fire, theft, flood, or site loss | Different physical location and, where practical, different administrative boundary | Geographic access, retention, and restoration logistics |
Copy diversity matters as much as copy count. If every copy uses the same administrator account, network share, cloud tenant, or automatic deletion policy, one stolen credential can remove them all. Separate administration, least-privilege access, and a recovery credential held outside routine user accounts reduce that shared failure mode.
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.
Keep an offline or disconnected copy
For locally stored project data, a removable external drive is a practical category of offline storage. It is one layer, not a complete strategy. CISA’s device-data guidance warns against leaving an external drive connected when it is not actively being used for backup because ransomware can reach a connected drive.
- Prepare the media. Use an organization-owned drive with enough capacity for the selected data, encrypt it before placing project files on it, and label it with an asset identifier rather than sensitive project details.
- Connect only for the backup window. Use a controlled, malware-checked workstation or backup host. Confirm that the destination is the intended drive and that the backup job records a completed, verified copy.
- Disconnect cleanly. Eject the drive, wait for the operating system to confirm it is safe to remove, and physically unplug it. Do not leave it attached “for convenience.”
- Store it securely. Keep it in a locked, access-controlled location protected from the same fire, theft, flood, or unauthorized access that could affect the production site. Rotate more than one drive if the business needs frequent offline runs.
- Track the rotation. Record the date, source systems, backup result, encryption status, person responsible, and storage location. A disconnected drive that no one can locate or decrypt is not a recoverable copy.
Offline does not have to mean the only copy or the most recent copy. The useful combination is a current protected copy for speed and a disconnected or otherwise isolated copy for resilience against an account-wide or network-wide attack.
Are cloud-synced files enough protection against ransomware?
No. Synchronization usually mirrors edits and deletions, so encrypted files can propagate to every synchronized device. Cloud storage can be an important recovery layer, but it is not automatically independent from production.
Review the provider’s shared-responsibility model: determine who protects the service, who protects your account and configuration, how long deleted or previous versions remain available, and how a large restoration is performed. CISA advises considering cloud-to-cloud backups, versioning or delete protection where supported, and immutable storage with care.
- Versioning: preserves earlier object or file versions so an administrator can select a pre-incident state.
- Delete protection: adds controls against accidental or malicious deletion; check whether administrators can bypass it.
- Immutable retention: prevents alteration or deletion during a defined period. Configure retention deliberately because an incorrect policy can create compliance, cost, or operational problems.
- Separate account or environment: keeps the backup administration and credentials apart from the project platform’s ordinary users.
- Cloud-to-cloud copy: provides another service boundary instead of relying on the same tenant, synchronization path, and identity provider.
Test the actual export and restore path, including permissions, shared links, metadata, large files, and any application-specific databases. A provider’s promise of durability does not establish that your team can recover a usable project environment after an attack.
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.
Encrypt backups and control who can restore them
Encrypt backup data in transit and at rest, including removable media. Limit backup administration and restoration rights to named personnel, use multifactor authentication where the service supports it, and separate backup credentials from ordinary domain or project-platform credentials. Log changes to schedules, retention, immutability, and deletion permissions.
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 →Plan key recovery before an emergency. Document where encryption keys or recovery passphrases are held, who can authorize their use, and how a second authorized person can gain access if the primary administrator is unavailable. Do not store the only key inside the encrypted backup or on the same compromised identity system.
Use least privilege: project users may need to read or edit working files, while only a small recovery group should be able to delete backup sets, change retention, or restore entire systems. Review access when employees, contractors, or projects change.
Choose a backup cadence and retention policy
Set frequency from the rate at which project information changes and the amount of work the business can afford to recreate. A team editing models and field records throughout the day may need more frequent capture than an archive that changes monthly. The policy should cover both the interval between backups and how many historical versions are retained.
CISA’s LockBit advisory summarizes daily or weekly backup and restoration “at the minimum” in that advisory context. It is not a universal construction rule. Use it as a floor for discussion, then set a shorter interval where a day of lost changes would create unacceptable rework, delay, or contractual exposure.
Rank #4
- Easily store and access 4TB of 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
- 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.
- Define which sources are backed up continuously, daily, weekly, or at project milestones.
- Retain enough versions to cover late discovery of corruption; ransomware may remain unnoticed for days.
- Keep long-term project records according to contractual, legal, and accounting requirements, separately from the short-term recovery window.
- Make sure the retention policy includes linked files, databases, permissions, and configuration—not only the visible documents.
- Review capacity and cost as model sizes, photo libraries, and project counts grow.
Test restoration, not merely backup completion
A successful job log proves that a process ran; it does not prove that the required files are intact, complete, or usable. CISA recommends regularly testing backup availability and integrity and testing backup procedures.
- Select representative data. Include a current drawing with external references, a model, a schedule export, a contract or change record, field photos, and any database or configuration needed to use them.
- Restore to an isolated test location. Do not overwrite production. Use a clean workstation or test environment with no connection to potentially compromised systems.
- Validate completeness. Compare file counts, sizes, timestamps, hashes where appropriate, version history, permissions, and linked references with the source inventory.
- Open the files in the required software. Confirm that the expected application version, templates, libraries, fonts, and plug-ins are available and that the model or drawing renders correctly.
- Exercise the workflow. Have a project user perform a realistic task: open a model, publish a drawing, search a change record, export a schedule, or retrieve a field photo. Technical readability alone is not enough.
- Measure the result. Record how long each step took, what data was missing, which permissions failed, and whether the recovery team could find the encryption keys and instructions.
- Correct and retest. Update the backup selection, dependency list, credentials, or runbook, then repeat the scenario until the result is dependable.
Test after major platform, software, storage, or identity changes as well as on a regular schedule chosen by the business. CISA requires regular testing but does not set one interval that fits every construction company.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Restore after an attack in a clean, prioritized environment
Do not reconnect a possibly compromised server, workstation, or shared drive merely to retrieve files. Coordinate with the incident-response lead and preserve evidence according to the organization’s response plan. Restoration should begin only in systems that have been assessed and made clean.
- Contain and assess. Isolate affected devices and accounts, confirm the scope, and identify the last known good backup. Treat unusual encryption, mass renaming, disabled security tools, or unexplained deletions as possible indicators of compromise.
- Establish a clean recovery area. Use rebuilt or verified systems, fresh administrative credentials, current security updates, and network segmentation. Keep restored data separate from systems that have not been cleared.
- Retrieve the protected copy. Use the offline, immutable, or separately administered copy selected by the incident team. Verify its date, integrity, and encryption before importing it.
- Restore the highest-priority dependencies first. Bring back identity and access controls, required applications, databases, templates, license services, and configuration needed to open critical project data. A folder-only restore may fail if these dependencies are absent.
- Restore priority project information. Start with projects and functions whose interruption creates the greatest safety, contractual, financial, or operational impact. Validate drawings, models, schedules, records, and links with project users.
- Reintroduce ordinary access gradually. Keep permissions narrow while validating the environment. Monitor for reinfection, unexpected encryption, or anomalous account activity before reconnecting broader teams.
- Document gaps and decisions. Record what was restored, from which version, what could not be recovered, and which manual reconstruction is required. Feed those findings back into the inventory and next restoration test.
Prioritization is company-specific. CISA recommends restoring according to critical services and avoiding reinfection of clean systems; it does not define a universal order for construction projects.
Compare backup approaches by recovery properties
| Approach | Access separation | Recovery speed and scope | Restore confidence | Operational fit and risks |
|---|---|---|---|---|
| Connected file copy | Low; usually reachable by the same users and malware | Fast for individual files when the network is healthy; weak against account-wide compromise | Low unless regularly opened and validated | Simple for small teams, but synchronized corruption and deletion can spread |
| Separately administered online backup | Higher; separate credentials, network segment, or repository | Often efficient for file-level recovery; larger system restores depend on export and rebuild procedures | Depends on versioning, retention, and realistic tests | Convenient for frequent changes; requires careful identity and service-responsibility review |
| Immutable or delete-protected storage | High during the retention period if configured correctly | Can support dependable point-in-time recovery; large restores still require bandwidth and clean infrastructure | Strong against tampering, but only a test proves usability | Retention mistakes can create compliance, cost, or deletion constraints |
| Offline removable media | High while disconnected | Good for selected files; slower and more manual for large environments | Requires periodic media, key, and application tests | Practical for local data and disaster isolation; a single drive is not enough |
| Separate-location copy | High for a site-level disaster when administration is also separated | Protects broad data sets but may take longer to retrieve or transfer | Must be exercised from the alternate location or service | Addresses fire, theft, and flood as well as cyberattack; logistics and access must be maintained |
Choose a combination based on project-data volume, change frequency, retention obligations, access controls, expected outage tolerance, and the provider’s actual responsibilities. No approach earns a “recoverable” label until a representative restoration has worked.
Common failure modes and fixes
- Only the shared drive is copied. Add project platforms, workstations with local data, cloud accounts, databases, configuration, and software dependencies to the inventory.
- The backup drive stays attached. Disconnect it between runs and document who stores and rotates it.
- Cloud synchronization is mistaken for backup. Enable and test historical versions, deletion protection, or an independent cloud-to-cloud copy where the service supports them.
- Every copy uses the same administrator account. Separate backup administration, enforce multifactor authentication, and protect recovery credentials outside the ordinary identity system.
- Jobs complete but files will not open. Restore to a clean test environment and include application versions, templates, libraries, licenses, and linked references.
- Retention is too short. Extend historical versions to cover delayed discovery of corruption and match contractual or legal requirements.
- No one knows the restoration order. Publish priorities, owners, contacts, and dependencies outside the affected systems.
- Restoration begins on an unclean network. Rebuild or verify the environment first, then import protected data while monitoring for reinfection.
A maintainable operating runbook
Turn the design into a short, owned procedure that a substitute administrator can follow:
- Review the inventory when a project, platform, software version, or storage location changes.
- Run scheduled backups and record source coverage, completion, errors, and verification results.
- Rotate the offline copy, disconnect it, and log its secure storage location.
- Review backup-account access, encryption-key availability, retention, versioning, and deletion protection.
- Perform a representative restoration test and have a project user validate the result.
- Update the recovery runbook, priorities, contacts, and dependency list after every test or incident.
Keep the runbook, inventory, and contact list available in a form that remains accessible if normal email, file shares, identity services, or project platforms are unavailable. The goal is not simply to possess backup data; it is to give the business a tested path from an attack to a usable, trustworthy project workspace.
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.
