Configure and validate backup storage

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

The Storage tab supports managed local storage and S3-compatible storage. Destination configuration and validation are separate from successful backup, verification and restore operations. Remote storage credentials stay on the server and are referenced by name rather than entered as values in the page.

Purpose

Choose an approved destination that can retain encrypted recovery points and support the required verification and recovery process.

Prerequisites

• Permission to manage destinations or recovery-operator authorization.

• A storage owner, approved retention policy and sufficient capacity.

• For S3-compatible storage, an approved HTTPS endpoint and server-side credential environment reference.

Procedure

1. Open Administration > Backup & Recovery > Storage. Review existing destinations and their Validation and Capacity values.

2. To add managed local storage, enter Name, select Managed local storage and provide a Relative path beneath the configured backup storage root. Choose Save destination.

3. For S3-compatible storage, select that kind and enter HTTPS endpoint, Region, Bucket, optional Prefix and Credential environment reference. Have the deployment operator provision the referenced credential securely before validation.

4. Choose Validate for the destination and review the returned status. Correct connectivity, access, capacity or TLS issues before using it in a schedule.

5. Select the destination for a manual backup. Confirm artifact creation, then independently verify the uploaded/materialized artifact and complete an isolated restore test.

6. Document whether the destination survives loss of the application host. If it is local to the same host, arrange an independently approved off-host recovery strategy and separate key custody.

Expected result

The destination is validated and has a demonstrated recovery-point cycle, with a clear retention and custody owner.

Important notes

• Managed local paths are relative to the configured backup root. Traversal, symlink escapes and unsuitable locations are rejected.

• S3 TLS verification is required for normal use. The application uses a server-side secret reference; do not paste access keys into article examples or database JSON.

• S3-compatible behavior was qualified against an isolated fixture. An actual provider account, permissions, lifecycle and recovery process need their own validation.

• Azure, GCS, SFTP and managed database/PITR schema kinds are not connected implementations in this release.

Troubleshooting

• If a local destination is rejected, check its relative path, write access and available capacity within the managed root.

• If S3 validation fails, have the operator check endpoint reachability, TLS, bucket access and the exact configured secret reference.

• If upload succeeds but later verification fails, preserve the artifact and review its identity/hash and retrieval permissions. Escalate without sending credential values.

Related articles

• Prepare backup access keys and storage

• Create an encrypted recovery point

• Verify a recovery point independently

• Manage recovery point retention