These ConfD jobs control the management of the database. For more information on these jobs, see the table below:
|Adds the specified nodes as reserve nodes for the given database. The nodes must already be added to the cluster and configured accordingly.
|This job aborts a running database backup.
|This job adds a backup schedule to the given storage volume with the given level and expiration time.
|This job changes the expiration time of the given backup.
|This job deletes all unusable backups for the given database. An unusable backup is a backup which cannot be read or used anymore, for example a level 1 backup without a corresponding level 0 backup.
|This job returns a list of available backups for the given database.
|This job modifies the given backup schedule with new parameters. The database must be running to run this job.
|This job returns the progress of the currently-running backup for a given database.
|This job removes the given backup schedule.
|This job starts a backup of the given database to the given archive volume with given level and expiration time. The database must be running in order to write a backup.
|This job deletes the specified backup(s).
|This job changes the configuration of a database. The database must be offline to change its configuration.
|Sets parameters for DB Kerberos authentication.
|Creates a new database. A database with this name or UUID must not already exist.
|This job deletes a database. The database being deleted must already exist.
|This job increases the number of active database nodes. The database must be stopped to run this job. The nodes to be added must be added already as reserve nodes. Afterwards, the database is started with the new nodes automatically.
|Returns a dictionary with the main database and volume parameters.
|This job returns the name of all created databases.
|This job removes the specified nodes as reserve nodes from the given database. The specified nodes must already be added as reserve nodes.
|This job resets the database. After performing this operation, the database will be empty and all data (including metadata) is deleted. The database must be offline to perform a reset.
|This job restores the given database from the given backup. The backup must meet certain prerequisites defined in documentation, such as originating from a database with the same number of nodes. The database must be offline to perform a restore.
|This job resumes the suspended nodes in the given database.
|This job adds a database snapshot schedule for the given database. The database must be configured with a snapshot_sync_volume, which is used for the schedule.
|This job returns a list of available snapshots for the given database.
|This job modifies the given snapshot schedule with new parameters. The database must be running to run this job.
|This job removes the given snapshot schedule.
|This job starts a database snapshot with the given expiration time. The database must be running to run this job.
|This job deletes the given database snapshots.
|Starts the database. The database must already exist and must not be running.
|This job returns the current state of the given database. Some common states are 'Running' (meaning the database is online), 'Setup' (meaning the database is offline), 'Startup' (meaning the database is starting up), and 'Shutdown' (meaning the database is shutting down).
|Stops a running database. The database nodes will remain online and available.
|This job suspends the given nodes in the given database. Suspending a node means that the node is marked as unavailable, even though it continues to run. This can be used to perform maintenance on a node. If this is done to an active node while the database is running, the database will shutdown and restart with a reserve node instead (if configured).