This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup. Register for class.

Applying a configuration backup causes some devices to fail

Table of contents

Overview

When you download a configuration backup, some devices fail. However, you can telnet to the NCM server and testing through NCM is successful.

When this issue occurs, the following entries display in session traces:

TimerTick: Login Timeout

Connected! The current connection has timed out.

Environment

NCM 7.6 and older

Cause

NCM exceeds the 45 second Telnet/SSH Connection Timeout limit before establishing a valid connection with the server.

Resolution

Gather session traces to confirm the errors.

Open the Orion Web Console.

Click Settings > All Settings > NCM settings.

Under Advanced, click Advanced settings.

Select the Enable Session Tracing checkbox, and then click Submit.

If you are running this NCM download/command through the Orion Web Console, go to the next step. If you are using the 32-bit Windows application on the server to download a configuration, close and re-open the NCM application for this setting to take effect.

After you reproduce the error, uncheck the Enable Session Tracing checkbox in Advanced Settings, and then click Submit.

Review the trace and debug file. The session traces are stored at:C:\ProgramData\Solarwinds\Logs\Orion\NCM\Session-Trace

Verify that the IP addresses of each failed device and confirm the issue.