To make a full backup of KMP knowledge base, you need to backup:

1. All KMP files.
2. KMP database.

How to backup your knowledge base? (MySQL)

How to backup your knowledge base? (MSSQL)

We recommend to make backups on the file and database level rather than backing up from KMP user interface.

First of all, remember that KMP stores some data (most of it) in its database and some data (attachments and images) as files. This means that, to make a full backup which you could use to recover your knowledge base at any moment, you need to backup all KMP files and KMP database.

Backup

Backing Up The Database

You can use MSSQL server default backup method.

Alternatively, you can backup the database from KMP user interface at Administration > Database Backup.

Backing Up The Files

There is nothing sophisticated about backing up KMP files - simply copy ALL KMP files to a secure location.

Restore

Restoring The Database

If you backed it up using MSSQL tools, you can restore it using MSSQL tools as well.

If you backed it up via KMP user interface, follow these steps:

1. Drop all tables from the KMP database (i.e. delete all tables to empty the database).
2. Upload the database from backup. This can be done with the help of restore.php script, which is attached to the article.
   To use this script, upload it to the main KMP directory and open it in your browser
   
   Then select the latest dump from the list and click "Restore".
   It may take up to an hour depending on the size of your database.
   If any error occurs, send us the log file: /admin/tmp/restore.log

Restoring The Files

There are two required steps:

1. Delete all files of current KMP instance.
2. Copy files through from the back-up.

We recommend to make backups on the file and database level rather than backing up from KMP user interface.

First of all, remember that KMP stores some data (most of it) in its database and some data (attachments and images) as files. This means that, to make a full backup which you could use to recover your knowledge base at any moment, you need to backup all KMP files and KMP database.

Backup

Backing Up The Files

There is nothing sophisticated about backing up KMP files - simply copy ALL KMP files to a secure location.

Backing Up The Database

The best way (i.e. easiest, fastest, and error-free) to do this is to use MySQL command "mysqldump". These command is available if you have SSH access to the MySQL server (if it is Linux server) or if you have RDP access or direct access (if it is Windows). This article explains how to backup and restore database via command line.

If you do not have access to the command line on the server, you can dump the database using phpMyAdmin or any other tool that is usually provided by ISP for database management. 

Restore

Restoring The Files

There are two required steps:

1. Delete all files of current KMP instance.
2. Copy files through from the back-up.

Restoring The Database

There are two required steps:

1. Drop all tables from the KMP database (i.e. delete all tables to empty the database).
2. Upload the database from backup.

The best way (i.e. easiest, fastest, and error-free) to upload the database is to use MySQL command "mysql". These command is available if you have SSH access to the MySQL server (if it is Linux) or if you have RDP access or direct access (if it is Windows). This article explains how to backup and restore database via command line.

If you do not have access to the command line on the server, you can restore the database using phpMyAdmin or any other tool that is usually provided by ISP for database management.To restore a large database dump you would probably need the BigDump tool. It is the only known PHP script that is capable of uploading large (more than 10Mb) database dumps.

Before restoring the database, open it in a database administration tool, e.g. phpMyAdmin or HeidiSQL and drop all tables from this database (i.e. select all tables and click "Drop Tables" button, which means "delete tables").

Then use this command to restore the database (if needed):