Plan storage and backups

Choose a storage place

Filesystem, S3 compatible, and Azure Blob adapters serve different storage needs. Use the configured destination for documents, knowledge indexes, and logs.

Model weights require a filesystem path accessible to the service. Read Prepare shared storage before joining nodes.

Keep private state separate

Local holds node caches and temporary work. Security holds protected installation and identity state. Cluster holds the shared Product data. Never share the Security root.

A new setting does not move old data

Changing a destination does not copy existing documents or indexes. Plan the migration, access checks, and recovery checkpoint before switching.

Back up Pūnaha

1. Quiesce Product writes under the maintenance plan.
2. Back up Control, Workflow, and AI at the same checkpoint using the provider's tools.
3. Include the corresponding protected installation state and required document, index, model, and log files.
4. Record Product version, provider, database versions, migration histories, and backup time.
5. Protect backup material and verify a restore.

Restore consistently

Restore the same provider and matching installation state. A database connection change does not migrate data or change engines.

Registration recovery must preserve the matching Control allowance record and node checkpoint. Clearing a counter does not create a new allowance.

Next step

Read Verify a backup and restore. Solution configuration recovery is separate from database and business data recovery.