Skip to main content
Code42 Support

Destination Is Offline

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

This article explains how to interpret and respond to the following alert.

The table below displays where the alert appears and where it can be configured.

Alert Text Location
"Destination is offline: destination name" Delivered by email and to the Alerts Overview of the administration console
"Destination is offline" Settings > Notifications of the administration console

Severity

Critical
This alert indicates a problem that could seriously affect your Code42 environment's security, result in data loss, or make the service unavailable.

Cause

Destinations can go offline for a number of reasons:

  • A storage server within the destination could be offline
  • An administrator may have set the storage servers within a destination to offline status
  • Network issues may be interfering with communication between the master server and storage servers
  • DNS issues
  • Hardware failure

Many of the possible causes of an offline destination reside outside the Code42 environment. Verify that your hardware and network are operating normally.

Potential effects

  • Users unable to back up
  • Users unable to restore

Before you begin

You should have a good understanding of how destinations fit into the Code42 environment storage hierarchy, and how destinations are managed.

Recommended solution

To resolve this alert:

Step 1: Ping and telnet tests

  1. Verify that the storage servers are online and reachable from the master server by pinging the servers from the master server command line. If the ping test fails, verify:
    • The storage server is powered on
    • Datacenter power is up
    • Datacenter networking is up
    • The storage server has not suffered a software or hardware failure
  2. Telnet from the master server to the necessary ports 4282, 4283, 4286, 4287, and 4288 of the storage servers . If the telnet test fails:
    1. Verify that the Code42 server process is running on the storage servers.
    2. Restart the Code42 server process.

Step 2: Check primary and secondary network addresses of master server

If the network addresses of the master server as configured in the administration console have changed to incorrect values, storage servers could lose the ability to communicate with the master server.

  1. Go to Settings > Server.
  2. Check primary and secondary network addresses.
  3. Change incorrect values to correct values for IP address or FQDN (fully qualified domain name).

Step 3: Check network settings of Code42 servers

Changes to the network configuration of the operating systems of the master server or storage servers could also prevent communication within a destination. Verify the network interface settings for all involved Code42 servers.

Step 4: Verify that all Storage servers are online

Verify that all storage servers in the destination are online:

  1. Navigate to Storage > Destinations in the administration console.
  2. Select the destination.
  3. Select each storage server under the destination and confirm that it is online. If a storage server is offline, follow the steps for resolving the Server offline alert.
    You can verify a storage server's online status by viewing the indicator under Online icon Online:
    • Online indicator A solid circle indicates online.
    • Offline indicator An open circle indicates offline.

Server offline indicator

Acknowledge the alert

The alert will continue to appear on the Alerts Overview in the administration console until you acknowledge the alert. To acknowledge the alert, go to Alerts, select the alerts you want to acknowledge, and choose Acknowledge from the action menu.

External resources

  • Wikipedia article on the ping network utility
  • Wikipedia article on the telnet network utility