How do I migrate / move my EventSentry installation and PostgreSQL database to a new server?

Moving EventSentry and the Web Reports:

1) Export your current EventSentry settings from the Management Console toolbar by clicking Home > Export. Then transfer this file to your new server.

Edit the file in a text editor such as Notepad and do CTRL+H (find and replace) and enter this as the Find value:

name of your old server

Then enter this as the Replace value:

name of your new server

Be sure to replace the examples in bold with the real values of your old server name and your new server name. Click "replace all" and save the changes.

2) Run the EventSentry installer on the new server. You can download the latest installer by logging into your licensing account at https://store.netikus.net/account and clicking "downloads" on the left. While signed in, you can also click "license keys" on the left and download your license file in case the installer asks you to provide your license. While running through the setup wizard, be sure to make a note of the database user passwords you set as you will need these later. When the installer is finished and it opens the EventSentry console, click Home > Import and choose the file from step 1.

3) Open the Windows Services Manager (start > run > services.msc) on the old server and locate the EventSentry Heartbeat Monitor service. Double-click it and open the "Log on" tab. Make note of which account this service is running under, and ensure that the same account is running the EventSentry Heartbeat Monitor service on your new server.

Checking the Heartbeat service's logon settings.

5) Copy any custom MIB files that were added to EventSentry (usually in the "C:\Program Files\EventSentry\mibs" folder) to the new server.

6) Copy the configuration backup files from "C:\Program Files\EventSentry\Backups" to the new server.

7) Copy any other custom files that may have been added to the "resources" or "scripts" sub directories to the new server.

8) Copy the Web Reports users, reports, jobs, and settings from your old server by copying the entire C:\Program Files\EventSentry\WebReports\conf folder. After stopping the "EventSentry Web Reports" service on the new server, paste and overwrite the folder into the same location on the new server. Make sure you copy and paste C:\Program Files\EventSentry\WebReports\confAND NOT the "C:\Program Files\EventSentry\WebReports\web\conf" folder. Start the Web Reports service again once completed.

Copying your Web Reports settings.

9) Stop the EventSentry Heartbeat service on the old server and leave it stopped so that you do not end up with duplicate heartbeat data and alerts.

10) On the new server use the EventSentry console toolbar to click Home > Collector, and update the name or IP in the hostname line to match the name or IP of your new server. The new name may already be shown if it was replaced in step (1) earlier.

Updating your collector settings.

Pushing your configuration and restarting your agents.

11) Open your database action, which by default is under Actions > Primary Database, and click the "Create" button. Make sure these settings are pointing to either your newly installed database on the new server (if you plan on starting over with a new database) or the old database on the old server (if you plan on using the old database until you migrate it over). Then click OK and click the Test button to ensure you get a successful test.

12) Open Web Reports and click Settings > Profile Editor. Scroll down to the "Database Connection" settings. Again, make sure this is pointed to either your newly installed database on the new server (if you plan on starting over with a new database) or the old database on the old server (if you plan on using the old database until you migrate it over). Click the "Test Connection" button to ensure that the test is successful. Finally, scroll to the bottom of the page and click Submit to save the changes.

13) If applicable, set all of your Syslog, SNMP trap, and Netflow senders to forward to the new server instead of the old server. If you're not sure which devices were already sending Syslog or SNMP Traps you can check in the web reports under Features > Syslog, Features > SNMP Traps, or Features > Netflow you can search the past few days and review the list of senders to see which senders need to have their destination settings updated.

Checking Web Reports for Syslog senders

14a) If the remote agents are reachable from the management console and can be restarted remotely
Save your changes then click the "restart" button on the collector page to restart the collector. Then use the toolbar to click Groups > Push Configuration > Go and then click Groups > Manage (dropdown) > Restart Agents > Go.

14b) If the remote agents are NOT reachable from the management console
If the remote agents cannot be reached from the management console, then the updated collector host name will need to be deployed from the original or "old" collector to which the agents are still connected to. After the original collector is stopped, the agents will attempt to reconnect to the new collector. In this scenario, follow the steps below: and then deploy the configuration (Save or Save & Deploy depending on your settings).

• Specify the hostname of the new collector in the collector dialog
• Deploy the configuration (Save or Save & Deploy depending on your settings)
• Click on the Home button in the ribbon and note down the Configuration Revision on the top right corner
• In the web reports, navigate to Tools -> Collector Status -> Connections and make sure that all remote agents report this configuration revision
• Stop the EventSentry Collector service on the old server

Moving the PostgreSQL database:

1) On your new EventSentry server, open the EventSentry Management Console to Home > Services, and click the Stop buttons next to each service EXCEPT for the database service.

Stopping the EventSentry services.

2) When not using the collector, stop all of your agents by clicking Groups > Manage (dropdown) > Stop Agents > Go.

3) From the old server, back up the database using this KB article https://www.eventsentry.com/kb/235. Move your resulting backup file to the new server and use the restore instructions from the same article to load the database onto the new server. When restoring, if you already have a database named "EventSentry" on your new server, you can adjust the database name in the commands to something new.

4) Copy C:\Program Files\EventSentry\data14\postgresql.conf and C:\Program Files\EventSentry\data14\postgresql_eventsentry.conf from the old server to the new server, overwriting the copy on the new server. Restart the "EventSentry Database v14" service on the new server when you are finished. All the rest of the steps will be on the new server.

5) Select your database action in the EventSentry console and click the Create or Edit button in the upper right corner of the settings. Change the server, database name, and/or port settings as needed to point to the database you just restored in step 3 then click OK. Then click the Test button to ensure that the test is successful.

Changing your Primary Database settings.

6) Save your new settings from Home > Save.

7) Undo step 1 by clicking the Start buttons instead of the Stop buttons in the Home > Services page. When not using the collector, start all your agents with Groups > Manage (dropdown) > Start Agents > Go.

8) Open Web Reports and click Settings > Profile Editor. Edit the server name or IP in the Database Connection settings to the name or IP of your new server. Click the "Test Connection" button to ensure that the test is successful. Finally, scroll to the bottom of the page and click Submit to save the changes.

Changing your Web Reports settings.

If you have any questions or any issues arise during migration, please feel free to open a support ticket at support@netikus.net and we will be happy to help.