Backup of dbWatch

When we think about backup of dbWatch, this involves several different parts of the software and installation:

dbWatch Server and configuration files

dbWatch Server places its configuration files and workarea in “C:\ProgramData\dbWatchControlCenter\” by default on windows (can be changed in the installation wizard)

A zip of this directory is sufficient for backing up the dbWatch Server installation.
There are no registry keys for which the dbWatch Server depends on, but if you move the zip file to a new server, it is important that on Windows you add a new service to start dbWatch.

While we do recommend our customers do a complete backup of this directory, but the most important sub catalogs are
C:\ProgramData\dbWatchControlCenter\config and C:\ProgramData\dbWatchControlCenter\crypto

dbWatch Monitor and config files

dbWatch Monitor is installed in a directory which is normally /usr/local/dbWatch/[version] on Unix/Linux and C:\Program Files (x86)\dbWatch\[version] on Windows.
A zip of this directory is sufficient for backing up the dbWatch Monitor installation. There are no registry keys that the dbWatch Monitor depends on.

While we do recommend our customers do a complete backup of the installation directory, a few configuration files are essential and unique for your installation. The most important one is monitor.xml. This contains the information about the dbWatch Servers you connect to. This is located in the dbWatch Server root directory.

dbWatch Schema in the databases

dbWatch Schema is usually called “dbwatch” and can be dumped with a command such as exp/imp on Oracle. It is also normally backed up as part of the normal database backup. In the dbWatch Schema all information on which tasks are installed, their status and historic information is kept. If you lose this, you can remove the database from dbWatch, drop the dbWatch user if it exists from the database and then add the database in dbWatch again. You will be without some historic information, but you get the database monitored by dbWatch again, and that is what is most important.

← Troubleshooting Guide / Adding MySQL Instance with Super Privilege Error →