• A new version of the Administration Server must not be lower than the current one.

• When restoring from a backup, the new database version must not be lower than the current one.
• The database and backup types must match.
• The collation settings in a previous database and a new one must match.

• A backup of the Administration Server can be restored in a newer version of Kaspersky Security Center (KSC) or a database.
• A backup of MS SQL Express can be restored in other editions of the same DBMS type.
• Virtual machine snapshots, SQL backups, and other third-party solutions cannot be used for restoring the Administration Server and DBMS.
• It is impossible to switch an existing Administration Server installation to a new DBMS address with a database copy.
• The data initialization process takes up to 15 minutes after upgrading or restoring KSC.
  During this time, the Administration Console may fail to connect and display the errors: “Failed to connect to the Administration Server” in the MMC console and “The Administration Server is temporarily unavailable” in the Web Console. If the problem persists, check the events in Kaspersky Event Log.

   

1. Review:
   • Compatibility recommendations for Kaspersky application versions
   • Requirements and limitations of the OS and database for the Administration Server version to be installed
2. Make sure that you have a distribution package for the installed version of the Administration Server and DBMS so that you can quickly revert to the previous configuration.
3. Perform data backup using the standard Administration Server tools.

4. Save the list of stand-alone and published installation packages.
5. Copy the data backup storage and the data from the Administration Server device to an external drive.
6. In case of problems with the main backup copy, or if you move the objects manually, additionally export the following items:
   • Administration Server certificate via creating a backup copy with a certificate only
   • Policy and EPP application task for endpoint protection
   • Application categories that you use
   • List of all devices from the search form
   • List of installed application management plug-ins
   • Disc encryption keys and password
   Be sure to remember the password for the encryption key file, as it cannot be reset.

1. Upgrade KSC using this guide.
   Contact Kaspersky Technical Support if the following database error occurs in the Update Installation Wizard: “Database error occurred: #1950 (˂id˃) Generic db error: ˂error_text˃”.
2. Check the functionality of the main Administration Server features when the data initialization in the database is complete.
3. Upgrade the Network Agent version, taking into account the requirements.

1. Check that the selected DBMS meet the recommendations.
2. Check if the hardware of the DBMS server and OS meets the requirements for the MS SQL version to be installed.
3. Upgrade the MS SQL edition or version using the instructions on the Microsoft website.
4. If required, increase the maximum number of stored events, taking into account the database size when upgrading from MS SQL Express to the extended edition.

1. If you need to change the DBMS type, use these instructions to make sure that moving data from the current type to a new one is supported.

2. Create a backup copy in a selected format.
3. Check that the correct type of the new DBMS is selected.
4. Install and configure the new DBMS using the database configuration recommendations: MySQL, MariaDB, PostgreSQL or Postgres Pro.

5. Remove the current version of the Administration Server from the server device and reinstall it. Another option is to disconnect the server from the network and install the Administration Server on a new device with the same network name and node IP address.
6. Perform a clean installation of the Administration Server and specify the connection settings to the new DBMS with an empty database. See the detailed guide in Online Help.
7. Use these instructions to restore the Administration Server data from the backup and wait for the background data import process to complete.
8. Re-create and publish the stand-alone application installation packages according to the list you compiled at the preliminary stage.
9. Install the plug-ins of the managed applications according to the list you compiled at the preliminary stage.
10. Update the Administration Server certificate in the Web Console connection settings using these instructions.
11. If required, install the Integration Server (VIIS) from the Security for Virtualization solution and perform the initial configuration to re-establish the connection to hypervisors.

• If you need to upgrade Windows on the server to a newer version, e.g. MS Windows Server 2016 to 2019, follow the instructions on the Microsoft website.
• If you need to migrate data to new Administration Server installations with a PostgreSQL or Postgres Pro database, use manual import of policies and tasks.
  To re-establish connection of managed devices to the Administration Server, restore only the Administration Server certificate from the backup and save the previous network settings, name and IP address of the server node.
• To switch between different KSC installations, use the task: Changing the Administration Server for client devices.
• Use the klmover utility to restore connection to uncontrolled devices, for example, after an Administration Server failure, if it is not possible to restore from a backup.
• If you need to change the Administration Server name, use these instructions.
• You can change the IP address on the active Administration Server only if you connect to the Administration Server using the name.
  • Use these instructions if you connect to the Administration Server using the IP address, but switch to using the name in the server connection address.
  • If the infrastructure does not have DNS, add an additional network card to the server with the new IP address and switch the managed devices to the new address using the task: Changing the Administration Server for client devices. Then you can delete the old network on the server.

If all the requirements have been met, preliminary works have been made, and moving the server has been performed as instructed, but one of the following errors has occurred:

• Error when recovering the database. Repeat the recovery in silent mode with the settings of log entries and import tracing.
  • "-logfile c:\klbackup-log.txt” enables logging of the import to a file.
  • "-tl 4 -tf c:\klbackup-trace.txt” enables tracing of level 4 to a file.

Example of the command:

• If you encounter other errors or issues, submit a request to Kaspersky Technical Support through Kaspersky CompanyAccount. In your request, describe your issue and include information about the database location (local or remote), type, and edition. Attach:
  • Screenshot of the issue and the text of the error that occurs
  • Configuration database file
  • GetSystemInfo report with the Include Windows Event Logs option enabled