Skip to main content
Code42 Support

Changing An Enterprise Server's Network Address

Applies to:
  • CrashPlan PROe
This tutorial explains how to safely reconfigure your enterprise server's IP address or hostname. You may need to to change the network configuration of your enterprise server due to a physical server move, subnet adjustment, VLAN change, or other network modification. Changing any part of the network configuration of an enterprise server that is in production requires careful planning to avoid adversely affecting users and devices.

Considerations

Changing the network settings of an enterprise server without proper planning can cause problems:

  • Changing the network settings of an enterprise server without following the steps in this article can cause your CrashPlan apps to lose contact with the master server, and thus become stranded. You will then need to manually reconfigure each stranded user device in order to update the network settings for each affected CrashPlan app.
  • The recommended method of moving an enterprise server to a new IP address requires the ability to edit the entry for your enterprise server in your organization's DNS system.
There is currently a known issue related to changing the primary or secondary network address of a enterprise server. Devices do not receive updated network address settings until any setting is manually pushed from the administration console. See Updating Devices After Changing Enterprise Server Network Address for details.

Before you begin

  • Be sure you understand your network topology
  • Determine whether or not you have the permissions and authority to modify the DNS resource record for your enterprise server
  • If you have questions about the process of changing your enterprise server's IP address, contact our Customer Champions. Issues with this process are easier to prevent in advance than to repair afterward.

Method 1: Modify the DNS resource record for your Enterprise Server

We recommend this method for most environments, because it minimizes the chances to strand a CrashPlan app. You need to have access to your organization's DNS system to use this method.

Before you begin

  • This method assumes that you are already using a DNS hostname as the primary network address
  • In order to decrease the downtime for CrashPlan apps, we recommend lowering the TTL value for your enterprise server's DNS resource record well in advance of the network change.
    For example, you might change the TTL value to 15 minutes (900 seconds) a day before the change. Endpoint devices would then have an outdated DNS cache for just 15 minutes, and the CrashPlan apps would be offline for 15 minutes or less.

Steps

Step 1: Change secondary network address to new IP address (optional)

This step is recommended unless you are using the secondary network address to allow routing via a second network interface. This step will provide a fallback route to the enterprise server for your CrashPlan apps in the event that the DNS change is delayed or problematic.

In Settings > Server > Secondary network address, enter the new IP address that your enterprise server is moving to.

  • Since the FQDN still resolves to the current IP address, devices will still be able to connect to the enterprise server during the period between this change and the update to your DNS system
  • Before moving on to the next step, wait several hours (depending on your TTL settings) to allow the changes to propagate to all CrashPlan apps, as well as any store points.

Step 2: Edit DNS system to reflect new IP address

Change your enterprise server's entry in your DNS system to reflect the new IP address. The DNS entry can be set in its zone file entry (in Linux/Unix using BIND) or its entry in Active Directory (Windows).

Some things to keep in mind:

  • You should time any DNS changes so that they occur during scheduled downtime (e.g. after hours, during weekends or holidays, etc.) in order to avoid service interruptions
  • You should have a thorough understanding of how DNS works before attempting the change.

Step 3: Verify CrashPlan app connectivity

Sign to the administration console to confirm that CrashPlan apps are coming back online.

Step 4: Confirm Store point connectivity

If your Code42 environment includes one or more store points, confirm that the store points are also back online:

  1. Go to Destinations > Servers
  2. All store points should be online, as signified by a green dot in the rightmost column on the Server Overview page.

Step 5: Change ttl back to original value (if necessary)

If you changed the TTL value for your enterprise server's DNS resource record before the IP address change, change the TTL value back to its original value.

Method 2: Modifying the secondary network address

This method is recommended if you do not have access to your enterprise server's DNS entry.

Steps

Step 1: Modify secondary network address

Navigate to Settings > Server, then change the Secondary network address field to the new value for the IP address:

  • Since you haven't yet actually changed the IP address of the network interface in the operating system, you will see a red x next to the secondary network address field, rather than a green checkmark.
  • Leave the primary network address set to the value of the old IP address or the FQDN, so that CrashPlan apps and store points are still able to communicate with the enterprise server.
  • You should wait at least several hours (depending on your TTL settings) to allow the changes to propagate to all CrashPlan apps, as well as any store points.
  • CrashPlan apps that are offline between the time that you change the secondary network address and the time that you move the enterprise server to the new IP address will not receive the changes. Since you will have to manually update the network configuration for these stranded devices, you should give your CrashPlan apps as much time as possible to receive the updated network configuration.

Step 2: Move Enterprise Server to new IP address

Migrate the enterprise server to its new IP address.

  • This process varies, depending on your platform and operating system
  • If your enterprise server is actively using more than one network interface, be sure that you are changing the IP address of the correct network interface.

Step 3: Confirm CrashPlan app connectivity

Sign in to the administration console and confirm that endpoint devices regain their connections. It may take some time for all CrashPlan apps to successfully reconnect, especially in an environment with a large number of users.

Step 4: Confirm Store point connectivity

If your Code42 environment includes one or more store points, confirm that the store points are also connecting to the master server:

  1. Go to Destinations > Servers
  2. All store points should be online, as signified by a green dot in the rightmost column on the Server Overview page.

Step 4: Modify primary network address (optional)

Change the primary network address to a new value:

  • This value could be a new FQDN or alternative IP address.
  • Regardless, changing the primary network address should not strand endpoint devices at this point, because the CrashPlan apps can utilize the secondary network address if there is a problem with the primary network address.