Use this feature to migrate configurations from a retired Diagnostic Server to a new Diagnostic Server installation. For example, while evaluating Spotlight Cloud you may have created a temporary Diagnostic Server. On deciding to install Spotlight Cloud in your production environment you may want to copy the configurations created during the evaluation period to the new location.
The following configurations are imported
- Configure alarms
- Alarm actions
- Configure fragmentation checks
- Configure error log
- Configuration templates
Historical monitoring data captured through the previous Diagnostic Server is not transferrable.
The Diagnostic Server mail server configuration is not migratable and therefore alarm actions using the email action will require the setting to be reconfigured after migration. See configure the Diagnostics Server.
The Diagnostic Server initiating the import process must have access via UNC path to the Diagnostic Server to be imported. The owner of the Diagnostic Server initiating the import process must have sufficient permission to access the share folder of the Diagnostic Server to be imported. A local system or group managed service account has insufficient privileges.
The Diagnostic Server to be imported must be a Spotlight Cloud Diagnostic Server. This feature cannot be used to import a Diagnostic Server from another Spotlight product like Spotlight Enterprise.
The source Diagnostic Server version must be current. If on import you see an error that the Diagnostic Server versions are different then reconnect the source Diagnostic Server to the internet so it can receive updates and try again.
The import feature is best implemented with a prompt turnover. A running Diagnostic Server is auto-updated roughly every two weeks. It is not a good idea to shut down the source Diagnostic Server, wait a month, and then import. Note that the Spotlight Cloud auto-update mechanism is not customer controlled.
Step through the import process
Open the destination Spotlight Cloud Diagnostic Server application
You will find the application on the desktop of the computer where Spotlight Cloud is installed. Double click on the desktop icon.
Sign in with your Quest account.
The configuration panel opens. Click Diagnostic server.
Enter UNC path of the source Diagnostic Server (Agent folder)
The folder is typically of the form:
\\yourhost\c$\Program Files\Quest Software\Cloud Diagnostic Server\Agent
Make sure this folder’s location is accessible to the Diagnostic Server you are importing into.
The owner of the Diagnostic Server initiating the import process must have sufficient permission to access the share folder of the Diagnostic Server to be imported. A local system or group managed service account has insufficient privileges.
If the folder is stored locally use the form c:\Program Files\Quest Software\Cloud Diagnostic Server\Agent
Each of the imported configurations (connections, templates, alarm actions) will be given a status: success, ignore, error.
Import finished - success
Spotlight Cloud will begin monitoring the imported connections right away. If both Diagnostic Servers are operational then they will both be monitoring the same connections. You may want to stop the source Diagnostic Server: Stop the Spotlight Cloud Diagnostic Server.
Connections monitored by the destination Diagnostic Server will not have access to historical monitoring data collected by the source Diagnostic Server.
Disabled connections are enabled on import if the Spotlight Cloud subscription is sufficient.
Alarm actions related to email, PagerDuty and SNMP trap require that the Diagnostic Server is appropriately configured: configure the Diagnostics Server.
Import finished - ignore
Configurations are not overridden. If you are re-importing a Diagnostic Server then configurations already successfully imported will not be overridden. If any configuration has the same name on both Diagnostic Servers for whatever reason then that configuration will not be overridden.
Import finished - error
Does the error message provide you with sufficient information to resolve the error? Correct and try again.
If the problem persists or the error is an exception then contact support.