Provider guide

Back Up a Mac to Tigris

Tigris is S3-compatible object storage. Azivault can use a Tigris bucket as an encrypted backup destination by pointing the plan at the Tigris S3 endpoint.

When this setup makes sense

Users who want globally distributed S3-compatible object storage and a simple endpoint-based setup.

What to enter in Azivault

In Azivault, choose Create New Plan, select the source folder, then go to Storage. Set Destination type to S3 compatible.

• Bucket name: the bucket dedicated to the Azivault repository.
• Region: Tigris documents region auto for S3-compatible SDK and CLI configuration.
• Custom endpoint: Tigris documents its S3 endpoint as https://t3.storage.dev.
• Use path-style requests: Azivault turns this on by default when a custom endpoint is present, unless you manually change the toggle.
• Access key ID and secret access key: Create a Tigris access key and secret key, then enter them as the S3 access key and secret in Azivault.
• Session token: optional. Use it only if the provider issued one for the credentials.

Setup checklist

1. Create a Tigris bucket for Azivault.
2. Create and save a Tigris access key pair.
3. Use endpoint https://t3.storage.dev and region auto.
4. Run Azivault's storage test, then perform a restore check after the first backup.
5. Click Test in Azivault and wait for a healthy result before adding the plan.
6. Finish the schedule and recovery password steps, then add the plan.

What the storage test verifies

Azivault's S3 test is a real read/write check. It writes a small object under .azivault-health-check/, confirms the object exists, lists that prefix, reads the object back, and deletes it. If the test fails, review the bucket, region, endpoint URL, credentials, path-style setting, and network access.

Restore and disaster recovery

Existing backups remain restorable even if a subscription expires, but you still need the repository data, provider access, and the Azivault recovery password or synced Keychain key. For S3-compatible storage, plan how you would hydrate or copy the remote repository objects to a local folder, then import that repository folder into Azivault for restore browsing.

Tigris backup risks

• Object lock support: Tigris is S3-compatible, but S3-compatible does not automatically mean every AWS retention feature is present. If object immutability is required, verify current Tigris support before treating it as ransomware protection.
• Lifecycle rules: Do not assume AWS lifecycle policy behavior unless Tigris documents and enables the rule type you plan to use. Repository cleanup should be tested with real restore checks, not only with bucket listings.
• Egress costs: Tigris pricing and routing can change as the service evolves. Record the current restore-cost model before relying on it for large emergency recovery.
• Regional durability: Tigris emphasizes globally distributed object storage and an auto region in S3 client configuration. Confirm whether that placement model satisfies any data residency, latency, or independent-copy requirement you have.
• Access key scope: Use an access key dedicated to the backup bucket and rotate it deliberately. After rotation, update Azivault before the next scheduled run.
• Restore gotchas: Use the documented endpoint and auto region when recovering from another Mac. If a generic S3 client defaults to an AWS region or AWS endpoint, it can fail even when the Tigris credentials are valid.

Provider notes

• Keep the Tigris console login, access keys, and Azivault recovery password recoverable after Mac loss.
• If you rotate Tigris access keys, update the Azivault plan credentials before the next scheduled run.

Provider details can change. Check Tigris S3-compatible setup docs 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 Tigris?

Yes. Azivault can use Tigris as an S3-compatible backup destination with the bucket, region, endpoint, and access credentials described on this page.

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 the provider account, storage credentials, and Azivault recovery password available. For remote S3-compatible repositories, hydrate or copy the repository objects to a local repository folder before importing it into Azivault.