How to archive a folder to S3, B2, or R2 and verify it
A practical guide to copying a folder to S3-compatible storage, keeping the archive report with the data, and checking the result before you close the job.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
Choose an S3-compatible destination, make the archive copy-only, and keep the report in the same destination as the archived data. The report gives you a per-file status and SHA-256 value, so the cloud bucket is more than a second location with a matching folder name.
1. Choose the S3-compatible destination
Safe Archive can copy to AWS S3, Backblaze B2, Cloudflare R2, Wasabi, or MinIO. The storage choice depends on the account, region, retention policy, and endpoint you already manage. The archive workflow is the same: select the bucket, provide the endpoint when the service needs one, and keep the destination details with the job record.
- Use AWS S3 when the archive belongs in an existing AWS account and policy.
- Use B2, R2, Wasabi, or MinIO when their storage, network, or deployment model fits the project.
- Choose a prefix or bucket reserved for the archive so the report is easy to find later.
- Confirm the archive account can write objects and read the result for review.
2. Prepare a copy that can be reviewed
Write down the source folder, the expected date or project scope, the destination bucket, and the person who approved the copy. This context matters when a bucket contains several dated archives and the original source is no longer available.
Run the archive from the Safe Archive tab or the CLI. Safe Archive hashes each copied file with SHA-256 and writes _archive-report.html and _archive-report.csv into the destination. The source remains unchanged throughout the run.
Keep the report with the archive. It records the result for someone who was not watching the transfer.
3. Verify the cloud archive before signoff
Open the HTML report and check the summary first. Then review the failed and skipped sections, followed by the per-file rows. A clean-looking bucket does not answer whether a file was blocked, missing, or converted during the run.
- Confirm the report is in the intended bucket and archive prefix.
- Check the total files and bytes against the expected source scope.
- Review every failed or skipped item and record the decision.
- Keep the HTML report for people and the CSV report for follow-up checks.
For a quick spot check, use the SHA-256 checksum calculator on a downloaded test file and compare it with the corresponding report row. The full archive report remains the source of truth for the complete run.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
4. Repeat the archive without starting over
If the network drops or a file cannot be read, the report names the exception and the command returns a partial result. Run the same archive again after fixing the problem. Files already recorded as complete are skipped, so the retry focuses on the unfinished work.
That makes the workflow useful for large handoffs and scheduled archive jobs. You get a dated copy in the bucket, a report beside it, and a clear list of anything that still needs attention.
Frequently asked questions
Can I use Backblaze B2 or Cloudflare R2 instead of AWS S3?
Yes. Safe Archive supports S3-compatible destinations including AWS, Backblaze B2, Cloudflare R2, Wasabi, and MinIO. B2, R2, Wasabi, and MinIO use their endpoint with the bucket settings.
How do I prove that the cloud archive is complete?
Open the _archive-report.html file in the destination and review the per-file status and SHA-256 values. The CSV report gives you a row-by-row version for further review or record keeping.
Does archiving to S3 delete the local source?
No. Safe Archive is copy-only. It leaves the source unchanged, so you can review the cloud archive before taking any separate retention or deletion action.
What happens if the upload stops partway through?
The archive report names files that could not be copied. Run the same archive again to resume; files already recorded as complete are skipped and the failed work is retried.