Primary Storage node definition

[htees]

quick question on OAM and storage node definition. If we have an application defined in our CRT table setup to send docs to a specific storage node and that node is now overwhelmed by access requests from that and other applications also defined there, is setting up a new storage node definition the thing to do? I.E. 85 applications are sending data to a particular ZORP /storage node but we want to break out 15 of them to another ZORP/storage node.

Will creating a new CRT entry pointing to a different storage node affect retrievals?

[Nolan]

If you have a CRT table, are you not using the report specification exit to set the collection name?  By updating the CRT table and adding the new collection name to the existing storage node you should be able to have many different collection names used and only one storage node.  We have one storage node and 1000s of collection names with different oam groups.

Not sure what ZORP is so maybe my response is not helpful.

[htees]

Let me see if I can break it down further......we have the ONE primary Storage set named as OAM. Within that we have hundreds of collections /primary storage nodes defined. If we have two that are defined for the same application, does the newest now start getting the content stored?

Thanks for the help!

[Nolan]

You can't have two for the same application. 
If you are set on adding a new storage node,
- You will need to then create new AGs to point to the storage node
- New applications to point to the new ag
- Update your folders to have the old and new ags mapped correctly
- All the CRT rows that have the old ags and app names would need to be updated.

Then it would flow to the new Storage Node for all new archives.    We have over 4000 collection names in our main storage node and don't have any problems.  Not sure why you need a new storage node unless you are changing the media (OAM,TSM,Cache)

If you are set up using the Report Specification Exit, you can update the collection names and add the new names to the existing storage node.  The CRT table is only read during the report specification exit not at retrieval.  We have done this for cases where we needed to change retention on a particular report.

Hopefully, the latter suggestion is what you are looking for.