Sicherung

BEST PRACTICE: Snapshot Backup via Third-Party Software with Online DB via PROQUIET

In this variant of the backup, a third-party software (e.g. Veeam or BackupExec) is used for the backup. The database continues to run during the backup process and the application is permanently available to the users.

In the backup software, before backing up the entire machine via snapshot, or the entire moveIT directory via file backup, the database must be switched to "pause" mode via pre-script.

To do this, the database must be set to quiet mode and thus paused. This works via the script "QuietDB_Enable.bat", which is located in the directory "...\ClientTools\DBADmin".

Script

The script works with relative paths and must therefore also be executed from the directory "...\ClientTools\DBAdmin". If adjustments are made to the file, it must be renamed because it may be overwritten during updates.

After executing this command, a snapshot of the entire machine can be created or the entire installation directory can be backed up.

In order to restart the database after the backup, the quiet command must be deactivated again in the post script of the backup job so that the database is up and running again. This works via the script "QuitDB_Disable.bat", which is located in the directory "...\ClientTools\DBAdmin".

Advantages:

• Easy to set up

• Easy to restore

• can be carried out during ongoing operation

• Database cache is preserved

 Disadvantages:

• Application is paused during the backup period and cannot be used

Full backup via third-party software with Offline DB

In this variant of the backup, a third-party software (e.g. Veem or BackupExec) is used for the backup. The database is stopped for the backup process and the application is no longer available. 

In the backup software, before backing up the entire machine via snapshot, or the entire moveIT directory via file backup, the database(s) must be terminated via pre-script. 

To do this, for example, the following service moveITDBControl must be terminated. This works with the following command line command:

net stop moveitdbcontrol

After executing this command, a snapshot of the entire machine can be created or the entire installation directory can be backed up. It is recommended to install a delay of about one minute after executing the command, so that the database can be shut down cleanly. 

To restart the database after the backup, the moveITDBControl service must be restarted in the post script of the backup job, using the following command line command:

Net Start MoveItDbControl 

Advantages:

• Easy to set up

• Easy to restore

 Disadvantages:

• Database is shut down and the application cannot be used during the backup period

• Database cache is lost

Online Backup

An online backup of the database is a backup of the database in a running state. This creates a dump of the database.

This works via the script "online_DB_backup.ps1", which is located in "... ClientToolsDBAdmin".

In addition, there are some example scripts that can be found in this directory:

Example_BackupDB_day.bat

• The tag is appended to the file name of the backup dump. So you can jump back 7 days in the backup.

Example_BackupDB_zip.bat

• Here, the dump is zipped after the backup to save window plate capacity.

Example_BackupDB_day_zip.bat

• After the backup, the dump is zipped to save hard disk space and the tag is appended to the file name of the ZIP file. So you can jump here 7 days in backup.

The script works with relative paths and must therefore also be executed from the directory "...\ClientTools\DBAdmin". If adjustments are made to the file, it must be renamed because it may be overwritten during updates.

An explanation of the setting of the script can be found in the script. It should be noted that in this form of backup, only a dump of the database is created. A restore purely with the dump would not be 100% complete. This backup variant is only recommended as a supplement to a full backup.

Advantages

• Can be carried out during operation with only slight performance drops during backup

Disadvantages

• "Only" a dump of the database is created

• Restore can take a while, because a basic installation has to be done, then a restore of the DB and then all master data have to be imported again.

ATTENTION: IS ONLY RECOMMENDED AS A SUPPLEMENT TO A FULL BACKUP!