Safe Archive Destination Errors: Space, Permissions, and Quotas
A destination-focused checklist for local drives, NAS shares, S3-compatible storage, and Google Drive when an archive cannot continue.
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
Fix the destination first, then resume the existing job. Check the storage path, write access, free space, saved credentials, or Google quota depending on the destination type. Completed files are skipped on resume.
Local drives and NAS shares
For a local destination, confirm the drive is mounted, the path still exists, and the account running the app can create a small test file. For a NAS or network share, check the connection, available space, and whether the share was mounted under the same user session that started the archive.
- Reconnect an external drive or network share before pressing resume.
- Check free space for the remaining archive, including files still to be copied.
- Confirm the destination is writable without changing the source folder.
- Do not remove the archive job or report while diagnosing the problem.
If space runs out, Safe Archive does not treat an unfinished temporary write as a completed file. Free room or choose a larger destination, then resume.
S3-compatible destinations
For S3, B2, R2, Wasabi, or MinIO, check the bucket, prefix, endpoint, region, and permissions together. A correct access key with the wrong endpoint can look like a credentials problem, while a valid bucket with no write permission can look like a destination failure.
- Confirm the endpoint is correct for the provider and region.
- Check that the credentials can write to the selected bucket and prefix.
- Confirm the destination account still has access to the bucket.
- Reconnect or re-enter credentials when the saved keychain entry is unavailable.
S3 credentials are stored through the operating system keychain rather than in the job report. The credential storage guide explains that boundary separately.
Google Drive destinations
A Google quota error is usually temporary. Wait before retrying, then resume the same job. If the account connection was revoked or cannot refresh, reconnect the account first. The archive engine keeps the failure distinct so a quota pause is not mistaken for data loss.
Do not respond to a temporary quota pause by starting several duplicate archive jobs. One resumed job has the journal needed to skip work that already arrived.
Resume after the destination is healthy
Once the destination is available, resume from the desktop job list or rerun the same CLI command. Read the report after completion and confirm the failure count, skipped count, and converted count match the handoff you intend to deliver.
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.
Frequently asked questions
What should I do when the destination runs out of space?
Free space or choose a larger destination, then resume the same archive job. Safe Archive writes files through temporary partial files, so an incomplete file is not treated as a completed archive item.
How do I fix a destination permission error?
Confirm that the drive or network share is connected and that the account running FolderManifest can create and write files there. Fix access first, then resume instead of starting a duplicate job.
What does a Google quota error mean?
Google is temporarily limiting the account or request rate. Nothing is lost and nothing is treated as a completed partial file; wait for the limit to clear and resume the archive.