You should regularly take backups of MONITOR to create backup copies. We recommend that you do daily backups if your system is constantly running.
There are many different third party backup programs on the market that are suitable for this. If you use this type of backup program, you can configure your own advanced backup settings. These programs are usually installed on a separate backup server.
There are usually client programs or "agents" for these backup programs so that a backup can be performed also on computers with other operating systems in the network, for example Linux or Mac OS.
What Should I Backup in MONITOR?
If MONITOR has been installed as a multi-user system in a network, you must backup the root directory Monwin as well as all the sub-directories, except for the Db sub-directory.
The Db directory contains database files in the sub-directories 001, 002, etc. for the respective companies. Here you also find sub-directories for test companies and historical databases for the respective company (if you have created such). These are then called 001_1, 001_2 (for company 001), 002_1, 002_2 (for company 002), etc. These sub-directories contain a database file called Monitor.db and a log file called Monitor.log. These files are locked by the database server service (database engine) while it is running.
Therefore you cannot include these database files and log files in a file backup when the database server service has been started. Instead it is the directory Dbbackup* under Monwin with the corresponding sub-directories 001, 002, etc. that should be included in the file backup.
* The Dbbackup directory incl. its sub-categories and database files does not exist when you have performed a first time installation of MONITOR. These are created by MONITOR Backup when a backup work item is run for the first time in that program. This program is included in MONITOR and is installed on the database server. Read more about MONITOR Backup under Database Copying in MONITOR.