Backing up the blueprint design server#
To back up the blueprint design server, back up its database and the folders in which it stores blueprints and configuration files.
Note: Always back up the database and folders at the same time. Using a backup of the database and folders from different times can cause problems when you restore the backup.
-
Stop the blueprint design server and the cloud discovery service.
See Stopping the blueprint designer, cloud discovery service, and engine.
-
Create a full backup of the database.
For instructions on backing up the database, see the documentation for your database.
-
Copy the repository and workspace folders to a secure backup location.
By default, these folders are in the following locations:
- /opt/ibm-ucd-patterns/repositories
- /opt/ibm-ucd-patterns/workspace
- Copy the server configuration files to a secure backup location.
The default location of these files is /opt/ibm-ucd-patterns/conf.
-
If you imported certificates, back them up.
By default, certificates are stored in the /opt/ibm-ucd-patterns/java/jre/lib/security/cacerts file.
-
If you installed patches, back them up.
The default location of these patches is /opt/ibm-ucd-patterns/patches.
-
If you customized the cloud discovery service configuration file, back that file up.
The location of the cloud discovery service configuration file is in the system variable CLOUDDISCOVERYSERVICE_SETTINGS_FILE. If this system variable is not set, the cloud discovery service is using a default configuration file and there is no need to back up the service.
-
Start the blueprint design server and cloud discovery service.
See Starting the blueprint designer, cloud discovery service, and engine
To restore UrbanCodeā¢ Deploy from a backup, see Restoring a backup.