BEFORE YOU BEGIN
Check before you begin
In this guide NAS is a filesystem source mounted by an administrator. Validate NFS/SMB access, service identity and mount scope for the installed release; do not assume vendor snapshot, NDMP or whole-volume recovery support.
Live verification limit: Firefox lab control could not reliably read page content; no NAS/S3 policy or restore screen was captured in this inspection. Steps are based on local Storage Policy templates and RustFS engine documentation. Another workflow’s screenshot was not substituted; no policy, bucket, mount, backup or restore was created. The installed release and end-to-end data acceptance require separate validation.
- Source/destination storage identity, release and data scope
- Access, TLS, service identity and capacity
- Full/incremental chain, catalog and retention
- Isolated acceptance destination, hashes and metadata checks
011. Define the source role and data scope
Record NAS identity, share/export, protocol, mount path and protected folders. In a small test folder, record names, sizes and SHA-256 values. Protecting NAS as a source and using NAS as a repository destination are different operations.
Expected resultThe relevant scope and acceptance evidence are recorded.
022. Verify access and the actual destination
Verify that the NAS mount points to the expected export/share and the service identity can read sample files. Do not mistake an empty local folder for the source after mount loss. Resolve SMB credentials, NFS UID/GID, permissions and networking before policy work; this guide does not execute mount commands.
Expected resultThe relevant scope and acceptance evidence are recorded.
033. Select the Storage Policy source and destination
Review Policy & Storage under Home → Policies → Storage Policy → Create Storage Backup Policy. Compare Policy Name, Source storage and Backup destination identities. Source and destination cannot be the same. The inspected template blocks RustFS-to-RustFS policy copy as unsupported; do not hide this limitation by selecting a different destination.
Expected resultThe relevant scope and acceptance evidence are recorded.
044. Explicitly select paths in Source Content
Verify Source mount; select only test files/folders in Storage tree and inspect the selected-path summary. Separately assess symlinks, nested mounts, very large trees and inaccessible folders; an empty list is not successful selection.
Expected resultThe relevant scope and acceptance evidence are recorded.
055. Plan preflight, scheduling and capacity
Validate the engine/scheduler release. The local engine document checks mounts, selected paths, storage and repository access using --validate-policy. The documented scheduler selects Full without a base and Incremental with an active catalog; do not generalize to every release. Validate weekly/monthly day behavior against the installed UI/release. Do not start a second concurrent job for the same policy.
Expected resultThe relevant scope and acceptance evidence are recorded.
066. Accept Full and incremental catalog results
In an approved small test, compare task results, storageJobs catalog records and repository output. A notification or exit_code=0 alone is not content acceptance. Record Full and dependent incremental identities and check access to the entire required chain. Do not treat the 18 September RustFS development acceptance as production acceptance of the current installation.
Expected resultThe relevant scope and acceptance evidence are recorded.
077. Complete restore and metadata testing
Use the separate NAS restore guide to verify file count, sizes, SHA-256 and access as the service identity in a controlled test. Test ACL, owner, timestamps, xattr and links separately where required; restored content does not establish NAS snapshot/NDMP acceptance.
Expected resultThe relevant scope and acceptance evidence are recorded.
COMMON QUESTIONS
Does S3 compatibility guarantee all recovery features?
No. Endpoint, release, source type, metadata, versioning, retention and destination behavior require separate validation. Repository acceptance is not general bucket-source backup acceptance.