Provider guide
Mac Backup to a NAS or TrueNAS
A NAS or TrueNAS system can be a useful local backup destination. Azivault can use a mounted network folder, and it can also use an S3-compatible service such as MinIO if you run one on the NAS.
When this setup makes sense
Users who want fast local recovery on storage they already own, with encryption handled by Azivault before data is written.
Can Azivault back up a Mac to a NAS or TrueNAS?
Yes. The simplest setup is to mount an SMB share in macOS and choose a folder on that share as the Azivault destination. If the NAS runs an S3-compatible service, Azivault can instead connect to its bucket and endpoint. A mounted share is usually simpler; S3-compatible storage is useful when you specifically operate and maintain that service.
Choose the right NAS setup
- Mounted folder: best for a normal SMB share and fast local-network restores.
- NAS-hosted S3: best when you already run an object-storage service and can recover its configuration.
- Separate offsite copy: still needed when the NAS and Mac share the same physical location.
What to enter in Azivault
In Azivault, choose Create New Plan, select the source folder, then go to Storage.
- Mounted NAS folder: set Destination type to Folder, then choose the mounted NAS or TrueNAS folder as the destination.
- NAS-hosted S3-compatible storage: set Destination type to S3 compatible, then enter the bucket, region, endpoint, access key ID, and secret access key for the object storage service.
- Use path-style requests: Azivault turns this on by default when a custom endpoint is present, unless you manually change the toggle.
- Session token: optional. Use it only if the NAS-hosted object storage service issued one for the credentials.
Setup checklist
- Decide whether the NAS will be a mounted folder destination or an S3-compatible destination.
- Make sure the destination is available when scheduled backups run.
- Keep at least one offsite copy for data you cannot afford to lose.
- Test restore browsing from another Mac or user account if this is part of disaster recovery.
- For S3-compatible NAS storage, click Test in Azivault and wait for a healthy result before adding the plan.
- Finish the schedule and recovery password steps, then add the plan.
What the storage test verifies
Folder destinations use macOS folder access rather than the S3 test
button. For a NAS-hosted S3-compatible destination, Azivault's S3 test
writes a small object under .azivault-health-check/,
confirms the object exists, lists that prefix, reads the object back,
and deletes it.
Restore and disaster recovery
Existing backups remain restorable even if a subscription expires, but you still need the repository data, NAS access, and the Azivault recovery password or synced Keychain key. For a mounted folder destination, import the repository folder directly. For NAS-hosted S3-compatible storage, hydrate or copy the remote repository objects to a local folder before importing that repository folder into Azivault.
NAS or TrueNAS backup risks
- Object lock support: Mounted SMB or AFP folder destinations do not provide S3 Object Lock semantics. If you run S3-compatible storage on TrueNAS, object lock behavior depends on that service and its bucket configuration, not on the share itself.
- Lifecycle rules: NAS snapshots, retention tasks, recycle bins, and object-store lifecycle rules can all delete or hide data on different schedules. Make sure none of them prune the Azivault repository earlier than your intended backup history.
- Egress costs: Local restores usually avoid cloud egress fees, but remote recovery over a home upload link can be slow. If the NAS is your only copy, plan how you would move data after theft, fire, or a failed enclosure.
- Regional durability: A NAS is usually one site and one administrative domain. RAID, ZFS, and snapshots help with hardware and operator mistakes, but they do not replace an offsite or cloud copy.
- Access key scope: For mounted folders, use a share account that can write only the backup destination. For NAS-hosted S3, use a bucket-scoped key instead of an administrative NAS account.
- Restore gotchas: Scheduled backups can fail when mounts disconnect, passwords rotate, the NAS sleeps, or the network path changes. Test restore browsing from a different Mac so you know which credentials and mounts are actually required.
Provider notes
- A NAS protects against Mac loss or disk failure, but not necessarily theft, fire, or site loss.
- Network sleep, disconnected mounts, and changed share credentials can interrupt scheduled backups.
Provider details can change. Check TrueNAS documentation before creating a production backup plan.
See also S3-compatible backup for macOS, offsite backup for macOS, and how to restore files from an Azivault backup.
FAQs
Can Azivault back up to NAS or TrueNAS?
Yes. Azivault can use a mounted NAS folder as a folder destination. If your NAS runs an S3-compatible service, Azivault can also use that service as an S3-compatible destination.
Are files encrypted before they reach the provider?
Yes. Azivault encrypts repository contents locally before repository objects are written to folder or S3-compatible destinations.
What does Azivault's S3 test button check?
For S3-compatible destinations, Azivault writes a small health-check object, confirms it exists, lists the health-check prefix, reads it back, and deletes it.
How do I recover if the original Mac is gone?
Keep NAS access and the Azivault recovery password available. For a folder destination, import the repository folder directly. For a NAS-hosted S3-compatible repository, hydrate or copy the repository objects to a local repository folder before importing it into Azivault.
Is a NAS backup also an offsite backup?
Usually not. A NAS on the same premises protects against Mac or disk failure, but it can be lost in the same theft, fire, flood, or power event. Keep another copy in a separate location or on offsite object storage for data you cannot replace.