Backblaze Business Backup Recovery Testing: Retention, Drives, and Large Restores

• Validate what Computer Backup can actually protect because operating-system files, applications, network shares, NAS devices, Time Machine data, and other exclusions can create silent recovery gaps.
• Choose thirty-day, one-year, or forever Version History against business recovery requirements and understand that an increase cannot resurrect versions already removed.
• Track external-drive attachment and backup state independently, and never delete the source merely because files appear in the Backblaze web console.
• Restore representative local and external-drive files every month, verify contents and metadata, and preserve evidence that names the source, restore point, method, result, and reviewer.
• Select web ZIP, Save Files to B2, Restore App, or USB drive paths by size, time, network, temporary space, security, and operational constraints before a major incident.

Choose Version History from a written recovery requirement. The default thirty-day setting retains modified or deleted versions for thirty days. One-year history extends that period to 365 days, and forever history retains versions indefinitely while the option and account remain in good standing, with applicable storage charges for older modified or deleted data. Record the approved setting per population, effective date, cost owner, required legal holds, and earliest recovery date that the chosen configuration can satisfy.

Understand prospective changes. Increasing from thirty days to one year or forever protects versions from the time the setting is enabled, it cannot restore file versions that were already cleared. Decreasing retention immediately limits recoverable history to the new shorter period. Require change approval, show the data-loss consequence, export evidence of the prior setting, and complete any urgent restore before reduction. A dashboard setting is a policy decision because it changes which historical states exist during a future incident.

Track external drives with their own calendar and evidence. Backblaze recommends keeping them attached when possible and reconnecting them at least once within thirty days, alert emails can occur after fourteen, twenty-one, and twenty-eight days. Extended Version History can preserve older drive content for the selected period, but a long-disconnected drive may need a new upload and requires rolling the restore view back to when it was connected. Record serial or asset identity without exposing sensitive filenames, attachment date, scan completion, last backup, and next due date.

• Approve Version History against the longest required recovery interval, cost, legal, privacy, and operational obligations.
• Treat retention increases as prospective and complete necessary restores before any decrease shortens available history.
• Maintain an external-drive register with owner, endpoint, selected state, last attachment, scan result, backup result, and due date.
• Never use Computer Backup as an archive by deleting source data after upload, regardless of the visible online listing.

Build a rotating sample that represents the business instead of repeatedly restoring one tiny document. Include a current local file, an earlier version, a deleted item that should still be in history, a selected external-drive file, a large item, a path with meaningful permissions or metadata, and one excluded record expected to be absent. Use synthetic or low-sensitivity samples where possible, but keep file types, sizes, applications, and drive relationships realistic enough to expose operational failures.

Start the test from the same authority and device path expected during an incident. A managed administrator may restore for a member only when group and Enterprise Control settings permit it, a decentralized user may use their own account, a centralized population may depend on IT. If a private encryption passphrase is enabled, retrieve it under the approved custody process. Select the correct computer and restore point, deliver the result to an isolated destination, scan it, and compare hash, size, content, timestamps, and application readability with the expected sample.

Retain evidence without copying sensitive content into the ticket. Record test date, requester, approver, source endpoint, drive class, selected restore point, version-history setting, method, file types and sizes, start and finish time, destination, passphrase-custody participants, integrity result, metadata result, application-open result, exceptions, remediation owner, and independent reviewer. Delete test copies according to policy. Trend failures by cause so recurring locked files, disconnected drives, stale clients, or insufficient space become managed problems.

• Rotate samples across local, historical, deleted, external-drive, large-file, metadata-sensitive, and deliberately excluded cases.
• Use the real member or administrator authority path and exercise private-passphrase custody when the backup requires it.
• Verify file integrity, size, metadata, permissions, malware-scan result, and application readability at a controlled destination.
• Keep secret values and recovered sensitive contents out of evidence while preserving enough metadata to reproduce the test.

No. Computer Backup automatically selects supported local data, but it excludes operating-system files, applications, caches, temporary data, network shares, NAS devices, Time Machine data, and other documented items. Build a coverage matrix and use separate methods for workloads that require system, application-consistent, server, or NAS recovery.

No. Backblaze says files in use by another program cannot be backed up at that moment. Test locally stored email, accounting databases, creative projects, and similar data with the application safely closed or quiesced, then verify the file’s backup and restore result rather than assuming later capture.

The default is thirty days for modified or deleted file versions. Supported clients can use one-year or forever history. Select the setting from written recovery requirements, record its effective date and cost owner, and verify older and deleted samples within the actual configured window.

No. An increase applies from the time it is enabled and cannot resurrect versions that were previously cleared. Complete urgent restores before a retention change, preserve configuration evidence, and never represent a newly enabled one-year or forever setting as historical protection that existed earlier.

Current Backblaze web-console guidance limits a free ZIP restore to 500 GB and allows no more than twenty active ZIP downloads. Test the Backblaze Downloader, destination capacity, bandwidth, security controls, and elapsed time before depending on that path for a business recovery deadline.

Depending on size and constraints, use the standalone Restore App, save restored files to Backblaze B2 up to the documented 10 TB limit, or request a USB hard drive up to the documented 8 TB limit. Evaluate cost, authentication, passphrase custody, temporary space, delivery, and recovery time.

Retain the approved requester, source computer and drive class, restore point, retention setting, method, file types and sizes, timing, destination, custody participants, integrity and metadata checks, malware scan, application-open result, exceptions, remediation owner, and reviewer. Do not store private passphrases or sensitive recovered contents in the ticket.