Storage Node Configuration

A storage node is a machine that is connected to a Backup server and one or more devices used in Backup's backup, archive, and HSM operations. Devices attached to storage nodes are called remote devices because they are not physically attached to the controlling Backup server. The storage node runs special Backup software that controls devices. The data stored on media in remote devices is tracked in the media database and online client file indexes on the controlling Backup server.

Storage nodes you add to your Backup configuration can increase the Backup server's performance, give you more flexibility in designing your network, and centralize the control of data management activities to one or a few Backup servers.

To create a storage node, install the storage node binaries from the Backup software distribution on the storage node machine. Then define the storage node's devices. The method for defining devices is described in "Remote Device Configuration ".

The storage node hostname does not need to be on the server's Administrator list unless you run jb_config and scanner on the storage node. The entry for this is root@storage_node_hostname.

For an autochanger or silo, you must manually add the storage node's hostname to the Administrator list before you define the devices with the jb_config program. When the jb_config program is completed, you can remove the storage node's hostname from the Administrators list. If you need to configure a new autochanger later, you must add the hostname before you run the jb_config program again. After you add the storage node's hostname to the Administrator list, one instance of nsrmmd starts on the storage node for each device that it controls.

Converting an Existing Backup Server to a Storage Node

Existing Solstice Backup servers can be converted to storage nodes. Converting an existing Backup server to a storage node involves:

1. Ensuring that you have a current backup copy of the current environment.

2. Updating/upgrading the server to Solstice Backup 5.1.

   Servers running the Backup Server Edition software must be upgraded to Backup Network Edition 5.1.

3. Choosing one of the servers to be the controlling (master) Backup server.

4. Configuring the new master server to use the remaining server(s) as a storage node(s). Maintain your /nsr directory on the storage nodes.

   You will need to call a Sun License Center for your storage node enabler(s). In the U.S., call 1-800-872-4786 (#3 at the prompt). For all other countries, refer to the Sun Licensing Center web page at http://www.sun.com/licensing.

5. Noting the date of the conversion as part of the recovery process.

6. Recovering data that was backed up before the date of conversion.

   To do so, convert the storage node to a Backup server by starting the nsrd process on the machine that contains the data required and inventory the jukebox or library attached to the server, if one of these automated devices is being used.

7. Converting the system back to a storage node by shutting down the nsrd process and inventorying the jukebox or library, after recovery of the data.

Do not merge the resource database, media database, and client file indexes of Backup server(s) and storage node server(s) due to potential conflicts that may arise.

From a Backup server, an administrator can view resources controlled by storage nodes associated with that Backup server. In addition, the administrator can perform all storage operations (mount, unmount, label, inventory, volumes, pools, devices, autochangers, clone, and nsrjb) for local and remote devices, as well as defining and controlling all Backup client operations.

One Backup server can control multiple storage node servers. You can establish an affinity between a client and a prioritized list of storage nodes, to ensure that a client is backed up to a preferred storage node. Such client affinity is kept in the resource database of the controlling Backup server.

Storage nodes added to your Backup configuration can increase the Backup server's performance, give you more flexibility in designing your network, and centralize the control of data management activities to one or a few Backup servers.