Skip to main content
ExLibris
Back
Rosetta
Ex Libris Knowledge Center

Configuring Storage Groups

  1. Last updated
  2. Save as PDF

Configuring Storage Groups

Administrators work with storage groups using the Storage Groups List page.
rcCfgStrgGrpList.gifStorage Groups List page
To access the Storage Groups List page, on the Administration page go to Repository Configuration > Storage Rules and Definitions > Storage Definitions for the Permanent Repository.
The following actions (on the following pages) can be performed on the Storage Group List page:

Adding a Storage Group

Administrators can add a new storage group in order to aggregate similar types of data, such as metadata or intellectual entities (IEs). When creating a storage group, Administrators must add at least one storage to save the storage group in the Rosetta system.
Administrators can add as many storage groups as are needed. When adding a storage group, Administrators perform the following actions:
  1. Define general information about a storage group
  2. Add at least one storage to the storage group
To add a new storage group:
  1. On the Storage Group List page (see Configuring Storage Groups), click Add Storage Group. The Storage Group Edit page opens.
rcCfgAddStrgGrp.png
Storage Group Edit Page
  1. In the General Information pane, complete the fields as described in the following table:
    Storage Group General Information Fields
Field Description
Name The name of the storage group.
Description The description of the storage group.
Policy Type

The criteria that determine which storage is used. The following options are available:

  • Random policy - Randomly select a storage that has adequate space available.
  • Orderly policy - Use the first storage (based on the storage order) that has adequate space available.
  1. In the Storages pane, select your storage plug-in.
rcStoragePlugins4.png
Storage Plug-ins

The following options are available:

  1. S3 Storage Plugin
    A storage solution based on the Amazon S3 cloud service. In this situation, Rosetta can be connected to the cloud and the Permanent repository is located on Amazon servers.
rcStrgPlgnS3.png
S3StoragePlugin

With this storage plug-in, the following parameters are used:

  • Endpoint – the URL of the entry point of the AWS Web service
  • Bucket name – This is the term used by Amazon for describing the location of the files in their cloud.
  • Secret Access Key – The access key for the bucket.
  • Access Key ID – The key ID.
  • Maximum waiting time – The time Rosetta will wait for response from Amazon when retrieving files. When the time elapses, Rosetta displays a message to the user that the file is not accessible.
  1. NFS Pair Tree Storage Plug-in
    An NFS plug-in in which the directory structure inside the file system is based on the files’ fixity value and not dates.
rcStrgPlgnNFSPairTree.png
NFSPairTreeStoragePlug-in

In the pair tree storage, files are located in a folder that is created based on an MD5 hash of their PID. This increases the speed and efficiency when search algorithms are used to retrieve files.

This plug-in can be used to implement different logic for folders’ naming conventions.
  1. NFS Storage Plugin
    The original out-of-the-box plug-in provided by Rosetta. Files are stored conventionally, based on their date of upload.
rcStrgPlgnNFSstrgPlgn.png
NFSStoragePlugin

Parameters for the NFS storage plug-in are described below.
Storage Parameters for NFS Storage

Field Description
Storage Parameter Name The name of the storage parameter.
Root Directory

The root directory of the storage.

e:\storage1\data\2008\06\10.
Directory Prefix

The directory prefix that is part of the directory name. For example, if the directory prefix is file$, the system creates the following directories:

  • e:\storage1\data\2008\06\10\file$1
  • e:\storage1\data\2008\06\10\file$2
  • e:\storage1\data\2008\06\10\file$3
    The directory prefix is suffixed with a sequential counter.
Files Per Directory The maximum number of files that can be saved in the storage. When the maximum number of files that can be saved in the directory is reached, the system creates a new directory.
Storage Max Size (MB) The total amount of data that can be saved in the storage.
Storage Block Size

The storage block size is used for an exact calculation of the available disk space.

It is strongly recommended that you leave this field at its default value.
Files Handling Method

Select one method from the three available:

  • Copy the files from their previous location (Deposit or Operational) to this storage (Operational or Permanent) so that two copies of the processed files exist in the system.
  • Move the files from their previous location (Deposit or Operational) to this storage (Operational or Permanent) so that only one copy of the file exists in the system.
  • Soft Link for Operational storage definitions, useful for handling large files, thus avoiding copying and moving them twice.
    Because derivative copy files are not moved and copied to the Permanent repository, they must be moved and copied from the Deposit file system to the Operational repository. Otherwise, if soft-copied, they might get lost when the Deposit file system is cleaned. Therefore, an out-of-the-box rule has been added that makes sure that these files are always copied.
    Move policy should only be used where operational and permanent storage are on the same mount; otherwise, there is no performance advantage (since streams are always removed from operational after SIP reaches permanent).
  1. Net App Storage Plugin
    The NetApp plug-in is a storage solution by NetApp, Inc., that integrates with the Rosetta storage system.
rcStrgPlgnNetApp.png
NetApp Plug-in

The NetApp application manages the storage of files in a combination of tapes and disks. Rosetta interacts only with the management layer, which stores and retrieves files for Rosetta.

  1. Google Storage
    The Google plug-in is a storage solution by Google, that integrates with the Rosetta storage system.
Google storage is supported for permanent only.
google_storage.png
Google Storage Plug-In

The following are the parameters of the Google Storage Plug-in:
Storage Parameters for NFS Storage

Field Description
Bucket name The name of the directory in Google in which the files are stored.
Service account key file content The authentication key
  1. ​Click Add Storage.
  2. The Storage Edit page for the storage plug-in you chose opens.
  3. In the General Information - Storage pane, enter a name and description for the storage.
  4. In the Storage Parameters pane, complete the fields as described in the relevant section above. (For NetApp parameters, see the documentation for the NetApp storage plug-in.)
  5. Click Save. The new storage is displayed on the Storage Group Edit page.
The storage is not added to the Rosetta system until you click Save on the Storage Group Edit page (see Step 8).
  1. To add more storages, repeat Step 3 - Step 6.
  2. On the Storage Group Edit page, click Save.
The storage group and its related storages are saved in the Rosetta system.

Re-Ordering the List of Storages in a Storage Group

To define a storage that must be used for a specific content object, the Rosetta system compares the parameters of the storage with the content object parameters (such as file size), using the policy type.
Storages are analyzed in the same order that they are displayed on the List of Delivery Rules page. The Rosetta system uses the first storage found that matches the parameters of the content object.
An Administrator can re-order storages to change their priority.
To re-order the list of storages:
  1. On the Storage Groups List page

rcRepoStorgRlsDefnts.gif

Storage Group Edit page
  1. In the Storages pane, use the up and down arrows to change a storage’s priority.
  2. Click Save.
The Rosetta system now analyzes the storages in the updated order.

Updating a Storage Group

Administrators can update a storage group to add more storages, modify the existing storages, or change the descriptive information of the storage group.
To update a storage group:
  1. On the Storage Group List page (see Configuring Storage Groups), locate the group you want to update and click Update. The Storage Group Edit page opens.
  2. Modify the fields you want to update and click Save.
The storage group is updated in the Rosetta system.

Deleting a Storage in a Storage Group

Administrators can delete a storage in a storage group.
The Rosetta system does not enable Administrators to delete a storage that contains data.
To delete a storage in a storage group:
  1. On the Storage Group List page (see Configuring Storage Groups), locate the storage group with which you want to work and click Update. The Storage Group Edit page opens.
  2. In the Storages pane, locate the storage you want to delete and click Delete. The confirmation page opens.
  3. Click OK.
The storage is deleted from the Rosetta system.

Deleting a Storage Group

Administrators can delete a storage group.
The Rosetta system does not enable Administrators to delete a storage group that contains at least one storage item.
To delete a storage group:
  1. On the Storage Group List page (see Configuring Storage Groups), locate the group you want to delete and click Delete. The confirmation page opens.
  2. Click OK.
The storage group is deleted from the Rosetta system.
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
  2. Tags
    This page has no tags.