[KB8592] Migrate the ESET Inspect Server SQL database to a different SQL Server

Issue

• Prerequisites
• Network and file transfer requirements
• Placeholder replacement
• Migrate the ESET Inspect Server database to a different Microsoft SQL Server instance or version using the command line

Solution

Prerequisites

• Both the source and target Microsoft SQL Server instances must be installed
• The target Microsoft SQL Server instance must be the same version or later as the source Microsoft SQL Server instance; downgrading is not supported

Network and file transfer requirements

• If the source and target machines are on different networks, you must manually transfer the backup file to the target machine
• If the source and target machines are on the same network, you can run the migration commands from either the source or target machine (ensure ping connectivity works)
• If you run commands across the network:
  
  
  • Ensure that TCP/IP communication is enabled for the target Microsoft SQL Server
  • Ensure the firewall on the source machine allows inbound/outbound communication on the Microsoft SQL Server port (the default port is TCP 1433, unless a different port was selected during ESET Inspect Server installation process)

Placeholder replacement

In the commands, replace the placeholders as follows:

• SRCHOST → hostname or IP address of the source Microsoft SQL Server
• SRCSA → username of the Microsoft SQL Server account on the source Microsoft SQL Server (typically sa)
• SRCEEIDBNAME → name of the source ESET Inspect Server database (default: eidb)
• TARGETHOST → hostname or IP address of the target Microsoft SQL Server
• TARGETSA → username of the Microsoft SQL Server account on the target Microsoft SQL Server (typically sa)

Migrate the ESET Inspect Server database to a different Microsoft SQL Server instance or version using the command line

To migrate the ESET Inspect Server Microsoft SQL database to a different Microsoft SQL Server instance or version using the command line, follow the steps below:

1. Stop the ESET Inspect Server service.

2. Create a full backup of the source ESET Inspect Server database. In Command Prompt, run:

   SQLCMD -U SRCSA -S SRCHOST -Q "BACKUP DATABASE SRCEEIDBNAME TO DISK = N'C:\USERS\public\BACKUPFILE.bak'"

   Manual transfer of the backup file

   The command creates the ESET Inspect Server database backup file (BACKUPFILE.bak) in C:\USERS\public. If the source and target Microsoft SQL servers are on different machines and not on the same network, you must manually transfer the backup file to the target machine before restoring the ESET Inspect Server database.

3. Restore the ESET Inspect database on the target Microsoft SQL Server. In Command Prompt, run:

   SQLCMD -U TARGETSA -S TARGETHOST -Q "RESTORE DATABASE SRCEEIDBNAME FROM DISK = N'C:\USERS\public\BACKUPFILE.bak'"
   

   If the location of the backup file is not C:\USERS\public\BACKUPFILE.bak, replace it in the command with the actual location of the backup file.

4. Finish the migration based on your setup:

   • If the target Microsoft SQL Server uses the same hostname/IP address and database name as the source, restart the ESET Inspect Server service.

   • If the target Microsoft SQL Server hostname/IP address, port, or database name differs from the source, run the ESET Inspect Server installer in the Repair / Change mode. Keep all settings unchanged, but update the Microsoft SQL database connection details (hostname/IP address, port, database name).