SRB Sketch

Components

• HPSS
• SRB server on ds009.sdsc.edu
• MCAT enabled SRB server on orion.sdsc.edu
• Oracle based MCAT
• "lca_ds" DataStar user account

Step to Implementation

1. Create "lca_ds" user acount
2. Instantiate SRB server on ds009, running as "lca_ds"
3. Instantiate MCAT enabled SRB server on orion
4. Create MCAT in Oracle database

"lca_ds"

The "lca_ds" user account. in the uic221 group, will serve two purposes: a route into HPSS; a user to run an SRB server under. The "lca_ds" user will have its own space in HPSS, and (since it's a member of the group), it can be granted read access to other file in HPSS. The space in HPSS under the "lca_ds" will be the default directory for files placed in the archive through the SRB. This space can also be the final holding area for "permanent" archives, like the catalogs coming over from Illinois.

SRB on ds009

In order to provide rapid access to the data in HPSS, there will be an SRB server running on ds009. This will likely end up as our default SRB host, i.e., the one that we'll connect to. This server will talk to the server on orion, and all interactions between the servers regarding metadata, usernames, etc., should be transparent to us.

SRB on orion.sdsc.edu

This is the SRB server that will access the MCAT (metadata catalog). It registers objects in the SRB, and modifies metadata, either for a client or another SRB server.

MCAT (Oracle Database)

The MCAT stores the metadata for the archive. Once the MCAT enabled SRB server is up, the MCAT will be created by it

Routes into the SRB

hsi put, then Sregister

Sput