Chat now with support
Chat with Support

Metalogix Archive Manager for Exchange 8.1.1 - Media Store Administration Guide

Simple Foldering Store

 

This is the very basic store when just folders are created under the specified path.

1.In the Configuration tool on the HSM / Stores tab click the New Store button to open the MediaStore Administration wizard.

NOTE: By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.

2.To create a new media store click the New store / Create option located under the Stores list.

3.In the MediaStore Administration wizard select Simple Foldering Store as a MediaStore type and enter a name for your new MediaStore in the Name of the new MediaStore text-box. Then click Next.

 

clip0027

 

 

4.Specify the Path of the store. In the Filename prefix box determine the file names to be created. Click the button right next to the text box to add datepart to the file name. Custom text is also available. Then click Next.

 

clip0028

 

5.In the following dialog the Relative speed of the store text box represents the relative speed of this store compared to other stores.

If HSM should copy files into the cache when reading from this store, check Use HSM Cache for read operations.

Click Finish.

 

clip0029

 

6.Click Close in the MediaStore Administration.

 

Finally restart the MAM HSM Base Store operations service to apply the settings.

Having a store ready is not enough. We need at least one schema, which is basically the path to the MediaStore. This schema needs to be registered in the HSM database. For more information on specifying a schema, see the HSM Install and Config Guide.

 

 

EMC-Centera MediaStore

 

To create EMC-Centera MediaStore:

1.In the Configuration tool on the HSM / Stores tab click the New Store button to open the MediaStore Administration wizard.

 

NOTE: By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.

 

2.To create a new media store click the New store / Create option located under the Stores list.

 

3.In the MediaStore Administration wizard select EMC-Centera as a MediaStore type and enter a name for your new MediaStore in the Name of the new MediaStore text-box. Then click Next.

 

clip0030

 

4.In the Centera IP-Addresses text box insert all IP-addresses of your Centera Cluster. Use commas to separate IP-addresses.

Examples

“10.2.3.4.”

“CenteraNode_1,CenteraNode_2”

“10.2.3.4,10.6.7.8?C:\centera\rwe.pea”

“10.2.3.4,10.6.7.8?name=<username>,secret=<password>”

 

It is possible to let the Centera Connection run in its own process (Run interface in own process). That way, two different connections to Centera won't affect each other. If a connection is broken, the whole connection (running in its own process) can be restarted, without the need to restart HSM.

Embedded Blobs - Normally if the Centera stores a file it creates two files internally (one CDF file which contains the meta-data and a second file for the data itself). This means that each file increments the file-count on the Centera by two. If you store lots of small files, the Centera can run out of “file-count” before it runs out of disk space. With these settings the data up to the set size is embedded in the meta-data file. (Internally this is a XML file and the data is saved as a base 64 encoded data)

If Open connection to Centera only as needed (Lazy open) is checked, the connection to the Centera is opened at the very latest moment possible. This is done by the Centera SDK itself and is a setting recommended by EMC.

Click Next.

 

clip0031

 

5.In the following dialog the Relative speed of the store text box represents the relative speed of this store compared to other stores.

If HSM should copy files into the cache when reading from this store, check Use HSM Cache for read operations.

Click Finish.

 

clip0032

 

6.Click Close in the MediaStore Administration.

 

Finally restart the MAM HSM Base Store operations service to apply the settings.

Having a store ready is not enough. We need at least one schema, which is basically the path to the MediaStore. This schema needs to be registered in the HSM database. For more information on specifying a schema, see the HSM Install and Config Guide.

 

 

IBM-Tivoli MediaStore

 

To create IBM-Tivoli MediaStore:

1.In the Configuration tool on the HSM / Stores tab click the New Store button to open the MediaStore Administration wizard.

NOTE: By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.

 

 

clip0033

 

2.In the MediaStore Administration wizard select IBM-Tivoli as a MediaStore type and enter a name for your new MediaStore in the Name of the new MediaStore text-box. Then click Next.

 

clip0034

3.Specify your settings: Config File - enter the path of the config-file. Log Directory - enter the directory where HSM should do its logging for TSM. API Directory - enter the path where the API (32-bit) is installed. Finally enter the name of the User to be used for connecting and its Password.

clip0035

 

4.In the Management Class text box define where it is saved in Tivoli Storage Manager (“TSM”)

(more info

http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.hcpt1/hcsm1b3025.htm).

Node - defines where the data is stored.

Properties - any property supported by TSM can be entered here, the only setting which is mandatory for HSM is the “enable archive retention protection” if data retention is used.

 

Check Disable Data Retention check box if:

- you do not have a license (e.g. if you just store on a tape and do not need that protection)

- the installation of TSM does not support Data Retention Mode

NOTE: If a TSM system requires data-retention (e.g. DR550), do NOT check this check box.

 

It is possible to let the IBM-Tivoli Connection run in its own process (Run interface in own process). That way, two different connections to Tivoli won't affect each other. If a connection is broken, the whole connection (running in its own process) can be restarted, without the need to restart HSM.

clip0065

If HSM uses more Tivoli Storage Managers, each storage configuration must contain TCPSERVERADDRESS option to specify TSM sever address  (e.g. -TCPSERVERADDRESS=TSM1)

 

clip0036

5.In the following dialog the Relative speed of the store text box represents the relative speed of this store compared to other stores.

If HSM should copy files into the cache when reading from this store, check Use HSM Cache for read operations.

Click Finish.

clip0032

 

6.Click Close in the MediaStore Administration. The MediaStore is ready.

 

Finally restart the MAM HSM Base Store operations service to apply the settings.

Having a store ready is not enough. We need at least one schema, which is basically the path to the MediaStore. This schema needs to be registered in the HSM database. For more information on specifying a schema, see the HSM Install and Config Guide.

 

 

 

HP Riss MediaStore

 

To create HP Riss MediaStore:

1.In the Configuration tool on the HSM / Stores tab click the New Store button to open the MediaStore Administration wizard.

NOTE: By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.

2.In the MediaStore Administration wizard select HP Riss as a MediaStore type and enter a name for your new MediaStore in the Name of the new MediaStore text-box. Then click Next.

 

clip0038

 

3.Enter your SMTP Server name, HTTP Server name, Domain and Repository in the relevant text boxes.

NOTE: For testing without a real HP-Riss use a local path as SMTP Server.

 

clip0039

 

4.If HSM should copy files into the cache when reading from this store, check Use HSM Cache for read operations. Relative speed of the store text box represents the relative speed of this store compared to other stores.

Click Finish.

 

clip0032

 

5.Click Close in the MediaStore Administration. The MediaStore is ready.

 

Finally restart the MAM HSM Base Store operations service to apply the settings.

Having a store ready is not enough. We need at least one schema, which is basically the path to the MediaStore. This schema needs to be registered in the HSM database. For more information on specifying a schema, see the HSM Install and Config Guide.

 

 

 

 

Related Documents