Storage node

A primary storage node is where Content Manager OnDemand manages reports and resources stored in an application group. A storage node identifies the object server on which Content Manager OnDemand stores the data.

If you use TSM to manage application group data in archive storage, then each storage node that writes data to TSM-managed storage must be registered as a client node in a TSM domain. The properties of the domain determine the devices that can hold the data and how long that TSM maintains the data.

A storage set can contain one or more primary storage nodes.

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 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 the archive storage manager to do so.

Note about IBM® i servers: Add, Update, and Delete operations for storage nodes have been disabled on IBM i servers. A storage node is created, updated and deleted as the result of actions performed on the migration policy with the same name in IBM Navigator for i.

Note about migration storage nodes: You can use the administrative client to view migration storage nodes (OD/zOS V2, OD/zOS IAFC, and OD/400 Spool File Archive).