9 docs tagged with "database"

We recommended that you regularly create a backup of your Deploy server.

To support high availability (HA), you can configure Deploy in clustered active/hot-standby mode. In this mode, only one Deploy node is active at one time, while the hot standby node is ready to become active if needed.

Deploy allows you to store the repository in a relational database instead of on the filesystem. If you use an external database, then you can set up failover handling by creating multiple instances of Deploy that will use the same external database.

Deploy uses a database to store all data such as configuration items (CIs), deployment packages, logging, etc. Deploy can use the filesystem or a database for binary artifacts (deployment packages) and CIs and CI history.

The Deploy Database plugin supports deployment of SQL files and folders to a database client. The plugin is designed according to the principles described in Evolutionary Database Design. The plugin supports:

The Database plugin uses the Deploy rules system to provide improved rollback support for SQL scripts.

When you upgrade to Deploy 8.0.x from an earlier version, the data stored in Deploy must be converted from the JackRabbit (JCR) format to SQL format.

You can configure Deploy to store and retrieve artifacts in two local storage repository formats:

Digital.ai Deploy 10.2.0 introduces a new way of managing plugins. Once you upgrade your Digital.ai Deploy to 10.2.0 or higher version there is no more manually copying of plugin files. Everything is handled by Digital.ai Deploy GUI and internal API. Plugins are now being stored in the database as a central location to remove manual manipulation of files across the cluster.