Backing up the embedded PostgreSQL database
This topic describes how to back up the embedded PostgreSQL database by using the database backup script.
You can back up the database while the product is running. We recommend scheduling the backup during non-peak times. You also might want to store the backup files on a remote disk. Also, you can use the Windows or Linux scheduler to schedule regular backups of the product database.
Do the following:
- On the application server, navigate to the BCAN_HOME\tools directory.
Use the following command to back up the application database:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
The backup file is written to the BCAN_DATA\dbbackup directory.
After you back up
After you have backed up the database, do the following:
- Navigate to the BCAN_DATA directory and make a copy of the keystore.bcfks file.
- Note down the password for the keystore.bcfks file:
- (Windows) Open the Registry, and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\enatomcat\Parameters\Java. Double-click Options in the right pane. The
-Djavax.net.ssl.keyStorePassword property contains the password. - (Linux) Navigate to the /etc/systemd/system directory and open the enatomcat.service file. The -Djavax.net.ssl.keyStorePassword property contains the password.
- (Windows) Open the Registry, and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\enatomcat\Parameters\Java. Double-click Options in the right pane. The
- Move the copy of keystore.bcfks and bcan.dump to a secure location. These files and password will be required for the database restore process.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*