Prepare a managed server
Use Install and persist data for a working binary or container configuration. For a managed deployment, record the executable version, explicit configuration path, data volume, operating-system account, and startup command in the service definition.
Storage and listeners
Give the server account access to the complete data directory and keep the directory on persistent storage. Configure client listeners for the required network and keep administrative endpoints restricted to operators. Multi-tenant deployments need the authentication-capable package and provisioned credentials; see Security Model.
Startup and health
Start the server through the deployment’s process manager. Wait for /health/ready on the configured admin listener before routing traffic. /health/live checks process liveness and /health/startup reports startup progress.
curl --fail-with-body http://127.0.0.1:9190/health/readyUse your configured admin address when it differs from this example. Inspect the startup log if readiness remains unsuccessful.
Accept a deployment
Follow Verify an installation to verify authentication, query execution, writes, and restart recovery. Establish a backup and restore procedure before the application begins relying on the database.
For routine restarts, see Start, stop, and restart. For cluster configurations, read HA deployment status and configuration first.