VeloceDB snapshots can be written to a local folder or to S3, GCS, or Azure object storage. The documented ways to start a backup are the Control Center interface and the POST /api/v1/backup API endpoint. The available product information does not specify scheduling, retention, or restore procedures.
Choose a snapshot destination
For a local backup, VeloceDB can write snapshots to a folder. For object storage, the documented options are Amazon S3, Google Cloud Storage (GCS), and Azure object storage.
The sources identify these destinations but do not describe how to configure credentials, choose a folder path or bucket, or set destination-specific options. Check the product documentation for those details before planning a backup process.
Start a backup through the Control Center or API
VeloceDB lists two backup entry points:
- Control Center: Use the interface to initiate a backup.
- API: Send a request to
POST /api/v1/backup.
The available information does not specify the request body, authentication requirements, response format, or whether the two paths expose the same options.
What the backup information does not cover
The product information describes snapshot destinations and ways to initiate backup operations. It does not state whether backups can be scheduled, how long snapshots are retained, how to restore one, or what backup guarantees apply. Those details should be confirmed before relying on snapshots for recovery planning.
This documented workflow is relevant to teams using VeloceDB that need snapshots in a local folder or supported object storage. For planning, confirm the required setup and recovery details in the product documentation before choosing a destination.