These instructions provide a way of moving monitored connections from one Spotlight Diagnostic Server to another. You may need to split a large Spotlight Diagnostic Server deployment into multiple deployments prior to federation. You would like to know how to do that without manually recreating all connections and configurations.
Edit me

Backup your current Spotlight Diagnostic Server deployment

Backup all Spotlight configuration and saved collection data.

For these instructions we recommend you backup the entire Spotlight Diagnostic Server installation folder.

C:\Program Files\Quest Software\Diagnostic Server\

Remember to also backup the Playback Database and Spotlight Statistics Repository.

Install a new Spotlight Diagnostic Server

If you intend to federate this Spotlight Diagnostic Server with your current Spotlight Diagnostic Server deployment then:

  • The new Spotlight Diagnostic Server should be running the same Spotlight Enterprise version as your current Spotlight Enterprise deployment.
  • Configure a separate Playback Database and Spotlight Statistics Repository for the new Spotlight Diagnostic Server.
  • Open TCP Port 40403 on the new Spotlight Diagnostic Server.
  • Regarding the credentials used to run this Spotlight Diagnostic Server: following Federation this Spotlight Diagnostic Server will authenticate with the Configuration server (the current Spotlight Diagnostic Server deployment) using Windows authentication over TCP port 40403. The Windows account that this Spotlight Diagnostic Server is running under must be valid in the domain of the Configuration server (the current Spotlight Diagnostic Server deployment). Note that Spotlight Diagnostic Server running under the built in Windows accounts (local system or network service) cannot be federated.

Copy monitored connection entity files to the new Spotlight Diagnostic Server

This will migrate monitored connections to the new Spotlight Diagnostic Server. Data for monitored connections is stored in the Spotlight Diagnostic Server installation folder

C:\Program Files\Quest Software\Diagnostic Server\Agent\conf\Monitored_Entity\
  • Select the files for those monitored entities you want to monitor on the new Spotlight Diagnostic Server.
  • Copy those files to the new Spotlight Diagnostic Server \Agent\conf\Monitored_Entity folder.
  • DO NOT copy the _agent.xml file.

Setup the mail server on the new Spotlight Diagnostic server

See Configure the Diagnostic Server’s mail server.

The email alarm actions on the two Spotlight Diagnostic Servers execute independently.

Restart the new Spotlight Diagnostic Server

See Start and stop the Spotlight Diagnostic Server.

  • Verify this new Spotlight Diagnostic Server is monitoring connections as expected.
  • You will see the alarm actions showing ‘uncompleted’. This is expected.

Remove moved monitored entity files from the original Spotlight Diagnostic Server

In a federation, each monitored connection is only monitored by one Spotlight Diagnostic Server. So once you have migrated the connections to the new Spotlight Diagnostic Server and checked that everything is working as expected, remove those Monitored_Entity files from the original Spotlight Diagnostic Server Monitored_Entity folder.

Restart the original Spotlight Diagnostic Server

See Start and stop the Spotlight Diagnostic Server.

Federate the two Spotlight Diagnostic Servers