Assigning a primary storage node to a secondary storage node

About this task

Note: Content Manager OnDemand no longer supports adding secondary storage nodes when you create a storage set. When updating a storage set, secondary storage nodes can only be created or assigned if the storage set already contains one or more secondary storage nodes. If you need to maintain a backup copy of data in archive storage, then IBM recommends that you configure your archive storage manager to do so.

When you assign a primary storage node to a secondary storage node, Content Manager OnDemand automatically creates a backup copy of data stored in the primary node. However, an administrator must take action before the backup copy can be used.

Before you can assign a primary storage node to a secondary storage node, you must define the secondary storage node. Adding a secondary storage node provides details.

When you define a cache-only storage node, you cannot assign the primary node to a secondary node.

To assign a primary storage node to a secondary storage node:

Procedure

  1. In the Storage Nodes list, select the primary storage node name.
  2. Select the Primary Node checkbox.
  3. Choose Update to open the Update a Primary Node window.
  4. From the Object server list, select the TCP/IP host name alias, fully-qualified host name, or IP address of the server on which the secondary storage node resides. Select *ONDEMAND, if the storage node resides on the library server.
  5. In the Storage Node list, select the secondary storage node name. After you select the secondary storage node name, Content Manager OnDemand completes the Description, Logon, Password, and Verify Password fields.
  6. Choose OK. Content Manager OnDemand lists the updated primary storage node in the Storage Set window, showing the secondary storage node name.