Configure Object Storage and Cloud Destinations

Follow this procedure to view a list of currently configured Lattus Object Storage destinations.

1. On the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab. Information for any previously configured Lattus Object Storage destination is shown as entries that have Quantum Lattus listed as the Provider. For each configured destination, the page displays the Name, Provider, Appliance State (online or offline), Controller State, I/O Path State, Manager host address, Containers count, Controllers count, I/O Paths count, and File Count.

3. Select the Lattus Object Storage destination whose information you want to view.

4. Click View....

5. When you are finished viewing destination information, click Done.

Follow this procedure to add a new Lattus Object Storage destination.

Note: If you plan to use HTTPS, you must create or import a security certificate prior to creating a Lattus Object Storage Destination. This applies to each Lattus controller configured for HTTPS. If you only intend to use HTTP, certificates are not needed.

To create or import a Lattus Object Storage security certificate, see Tools > Object Storage CertificatesTools > Object Storage Certificates. To manage SSL certificates, click Object Storage Certificates on the Tools menu. For additional information, see Basic Secure Sockets Layer (SSL) Guidelines, which outlines some standard information about using private and public certificates.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

4. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new Lattus Object Storage destination.
   Provider	Select Quantum Lattus from the Provider list.
   Manager Host	Enter the host address for the Lattus Object Storage manager host.
   Manager Port	Enter a decimal integer to specify the port number of the Lattus Object Storage manager GUI interface. The default port number is 80.
   Manager Protocol	Select the http or https protocol. Note: If you plan to use HTTPS, you must create or import a security certificate prior to creating a Lattus Object Storage Destination. This applies to each Lattus controller configured for HTTPS. If you only intend to use HTTP, certificates are not needed. To create or import a Lattus Object Storage security certificate, see Tools > Object Storage CertificatesTools > Object Storage Certificates. To manage SSL certificates, click Object Storage Certificates on the Tools menu. For additional information, see Basic Secure Sockets Layer (SSL) Guidelines, which outlines some standard information about using private and public certificates.
   Authentication	Select if authentication is required for this configuration.
   User Name	Select a global user name to be used for namespace permission for this configuration. This parameter is mandatory if Authentication is set to “Enabled”.
   Password	Select a global password to be used for namespace permissions for this configuration. This parameter is mandatory if Authentication is set to “Enabled”.

5. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

6. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to an I/O Path that is associated with a specific Object Storage API. The available values for provider Quantum Lattus are AXR and S3.
   URL Style	There are two ways to format the URL: PATH VHOST This parameter defines which style of URL to use. The recommended option is VHOST.
   Object Access Protocol	Select the protocol to be used for Object Storage object access. By default, the protocol is set to http. Note: If you plan to use HTTPS, you must create or import a security certificate prior to creating a Lattus Object Storage Destination. This applies to each Lattus controller configured for HTTPS. If you only intend to use HTTP, certificates are not needed. To create or import a Lattus Object Storage security certificate, see Tools > Object Storage CertificatesTools > Object Storage Certificates. To manage SSL certificates, click Object Storage Certificates on the Tools menu. For additional information, see Basic Secure Sockets Layer (SSL) Guidelines, which outlines some standard information about using private and public certificates.
   Host[:Port]	Enter the connection endpoint address that contains the host name or IP address. If needed, add the optional port number separated by a colon ":". If the port number is not specified, the default (80 for http, 443 for https) is assumed. Connection endpoints must be unique.

7. In the Containers section:

   1. On the Container Selection list, click Scan or Manual. This parameter gives you the option to either scan the available container or enter the container name manually.

      • If you select Scan and a user name and password are required, either use the credential specified for the manager host, or check the Use different credentials box and enter the username and password. You are then presented with a pre-populated list of available containers.
      • If you select Manual, you are presented with a text box to manually enter the name of the container. To view or add Object Storage buckets, on the Tools menu, click Object Storage Buckets.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Select (if using Scan mode) or enter (if using Manual mode) the appropriate container for this configuration.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. The available values for provider Quantum Lattus are AXR and S3.
      Storage Class	Leave this as none, as it is not applicable to Lattus media.
      Signing Type	For Lattus S3 media, use the default value of V2. This parameter is not applicable to AXR media.
      Authentication Type	Specify the authentication type for the container being configured. An authentication type is required for Lattus S3 media, but not for AXR. The available values for provider Quantum Lattus are NONE and STANDARD. The STANDARD type authenticates with a user name and password for Object Storage access.
      User Name	Enter a user name to be used to access this container. This parameter is mandatory if Authentication is set to “Enabled”. This selection overrides the global permissions settings.
      Password	Enter a password to be used to access the container. This parameter is mandatory if Authentication is set to “Enabled”. This selection overrides the global permissions settings.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If left at System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details
      Batch Delete	Specify whether the object storage server supports batch delete operation. Batch delete is a feature that Amazon AWS S3 supports to allow multiple objects to be deleted in one http request. This is enabled by default for AWS S3. Some other S3-compatible object storage vendors also support it.

      Note:  If no data has been written to a controller, I/O path, or container, you can click Delete to remove the item, and then click Apply to save the changes.

8. (Optional) Repeat Step 7 to add additional containers to the same Lattus Object Storage Destination.

9. Click Apply to save your changes, or Cancel to exit without saving.

10. (Optional) Repeat Step 3 through Step 9 to add additional Lattus Object Storage destinations.

Note:  All containers on Lattus-M share the same I/O paths and storage capacity. There is no advantage to be gained by defining multiple containers for the same policy class and copy number. Storage Manager selects the first available container that meets the policy class criteria for the store operation.

Follow this procedure to edit an existing Lattus Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the Lattus Object Storage destination whose information you want to edit.

4. Click Edit....

5. To edit a field, type directly in the field (for example, type a new name and IP address for an I/O path), or select another option from the drop-down list.

   Note: To return to the last saved configuration for a controller, I/O path, or namespace, click Reset.

6. Click Apply to save your changes, or Cancel to exit without saving.

7. When a confirmation message appears, click Yes to proceed, or No to abort.

8. After a message informs you that the Lattus Object Storage destination was successfully modified, click OK.

Follow this procedure to delete an existing Lattus Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the Lattus Object Storage destination you want to delete.

4. Click Delete.

5. When a confirmation message appears, click Yes to proceed with the deletion or No to abort.

6. After a message informs you that the Object Storage destination was successfully deleted, click OK.

Follow this procedure to launch the Lattus Object Storage Manager GUI application.

Note: Enable pop-up windows in your browser settings. If you block pop-up windows, you might miss important information for a web page. For example, the Launch Manager might use a pop-up window to request your login credentials.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the Lattus Object Storage destination.

4. Click Launch Manager. A new browser window appears and displays the Object Storage Manager GUI application login page. If you entered a User Name and Password when you created the selected Lattus Object Storage destination, those credentials are used as your login.

A Multi-Geo (multiple geographic) Lattus configuration consists of three sites configured under the same durability policy. With this configuration, it is likely that WAN (Wide Area Network) communication with remote sites will be slower due to higher latency in the WAN link. If you have significantly higher latency to the remote Lattus sites, Quantum recommends that you configure only the I/O Paths to the local controller be “Online”.

You can configure Object Storage I/O Paths to be offline in the Tools > Storage Manager > Storage Components screen. To do so, select the remote Object Storage I/O Paths that you want to set as offline and then click the Offline button (see Change the Current State of Object Storage Destinations, Controllers, and I/O Paths). You can also use the fschstate(1) command for this.

If the local Lattus controller is down, but the remote sites are still up, you may want to change the local I/O Paths to the “Offline” state, and changethe remote I/O Paths to the “Online” state to continue using Lattus.

With Lattus 3.5.1, you can convert AXR namespaces to S3 buckets and make them accessible through the S3 interface. StorNext provides the capability to convert the media type from AXR to S3.

Convert One or More AXR Namespaces to S3 Buckets

1. Using the StorNext MDC (CLI only), follow the steps below.

   Note: Ensure that no store/retrieve operations are occurring on the same AXR namespace that you plan to convert. If there are any store/retrieve operations occurring on this namespace, wait for the operation to complete.

   1. Execute the command fsobjcfg and retrieve the media ID of the AXR namespace to be converted.

   2. Stop TSM.

2. Refer to the documentation in the "Converting an AXR Namespace to an S3 Bucket" section in the Lattus Service Reference Guide (Part Number 6-67798-xx). Log into the Lattus controller to perform the conversion.

3. After the Lattus conversion is complete, execute the following commands using the StorNext MDC CLI:

   1. Add an S3 connection endpoint using the StorNext GUI or the fsobjcfg command as shown below. At least one S3 I/O path is needed to access the S3 buckets under the same appliance:

      #/usr/adic/TSM/exec/fsobjcfg -a -o iopath_alias -i connection_endpoint -e http -t S3 -n controller_node_alias

   2. Change the AXR namespace name and media type, using the NameSpace value from Step 2 and the Media-ID value from Step 1a:

      # fsobjcfg -m -b NameSpace -t S3 -U <S3_bucket_username> -P <S3_bucket_passwpord> -X -f <Media-ID>

   3. Modify the file /usr/adic/TSM/config/filesize.config and change LATTUS to S3 for the media ID corresponding to the converted namespace. Alternatively, you can achieve the same result using the StorNext GUI by changing the file system policy's steering information from Lattus to S3.

      Note: To use the StorNext GUI, TSM should be available.

   4. Start TSM.

   5. Verify that the store and retrieve operations are working as expected with the converted media type.

   6. Use the command fsfileinfo -u to verify that the object URL reflects (S3) for every file stored before or after the conversion.

• Hitachi Content Platform (HCP) version 8.0.0.1 and above supports multipart upload. To enable HCP software for multipart upload, you must configure MAPI and Cloud Optimized by selecting Optimized for cloud protocol only on the Namespace in HCP. For details, see the HCP documentation.
• HCP does not support chunked upload with V4 signing. When you configure HCP buckets/containers with StorNext, you must use V2 signing.

Follow this procedure to view a list of currently configured S3 CompatibleObject Storage destinations.

1. On the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab. Information for any previously configured S3 Compatible Object Storage destinations is shown as entries that have S3 Compatible listed as the Provider.

   For each configured destination, the screen displays the Name, Provider, Appliance State (Online or Offline), Controller State, I/O Path State, Manager host address, Containers count, Controllers count, I/O Paths count, and File Count.

3. Select the S3 Compatible Object Storage destination whose information you want to view.
4. Click View....
5. When you are finished viewing the destination information, click Done.

Follow this procedure to add a new S3 Compatible Object Storage destination.

1. Ensure that the Object Storage buckets that you are configuring with Storage Manager have been created on your Object Storage system, and that you know the names, connection endpoint, Access Key Id, and Secret Access Key to your buckets.

   Important Considerations

   If you plan to use HTTPS, you may have to create or import a security certificate prior to creating an S3 Compatible Object Storage destination.

   Follow the documentation from your S3 Object Storage system's vendor to set this up on your Object Storage system. To create or import an Object Storage security certificate, see Object Storage Certificates. Also, see HTTPS Default CA ROOT Certificate File or Path for additional information on how to configure your customized CA PEM files on your StorNext system.

   For the ActiveScale P100/X100, if the controllers already have HTTPS enabled and a certificate configured, you can install the certificate on your MDC in the certificate repository. Verify that the certificate has an S3 domain name (configured using the ActiveScale Admin GUI) for the Common Name and that the Subject Alternative Name specifies the IP addresses of each controller.

   If the certificate does not already exist, you must create a self-signed wildcard certificate with a private key in order to enable TLS/SSL (HTTPS) on each controller. Use the Tools > Object Storage Certificates menu of the StorNext GUI to create the certificate. The ActiveScale S3 domain name must be specified for the Common Name. For example, if the S3 domain is myorg.com, the Common Name should be set to *.myorg.com. For the Subject Alternative Name field, use the ActiveScale S3 domain name for the DNS Name and include IP addresses for all controller nodes. Once all fields have been entered, click Apply to create private and public certificate files.

   The private certificate file must be downloaded and installed on the ActiveScale P100/X100. Select the newly created certificate, click Download, and then click the Private Self-Signed Certificate link to download the certificate with private key. This file contains a private key followed by the certificate. The ActiveScale P100/X100 Administration Guide requires the certificate *.pem file have the public certificate listed first, followed by the private key. Use an editing tool to swap the order of the certificate and private key. Once the file has been updated, use menu Configuration > Security > Certificate > S3 SSL Certificate of the ActiveScale GUI to import the certificate file.

   Note: The new certificate replaces a previously configured certificate.

   After you configure the private certificate, download the public certificate and install it on your MDC. Return to the Tools > Object Storage Certificate menu of the StorNext GUI and select the newly created certificate. Click Download and then select Public Certificate File to download the public certificate file. Quantum recommends you place the certificate in the default CA Root Certificate file or repository. See HTTPS Default CA ROOT Certificate File or Path for additional details. If you previously used the certificate repository, /usr/cvfs/config/ssl, you can continue to use it for the new certificate file by following these steps:

   1. Remove the old certificate file.
   2. Install the new certificate file.

   3. Execute c_rehash on your default certificate repository:

      # /opt/quantum/openssl/bin/c_rehash /usr/cvfs/config/ssl

   4. Set the TSM system parameter FS_OBJSTORAGE_CAPATH to the certificate repository and restart the TSM:

      # echo "FS_OBJSTORAGE_CAPATH=/usr/cvfs/config/ssl;" >> /usr/adic/TSM/config/fs_sysparm_override

      Alternatively, configure the parameter using StorNext GUI (see Tools > Storage Manager > System Parameters).

   After you configure the certificate, you can verify the certificate HTTPS endpoints using the openssl tool. See Certificate Verification for an HTTPS Endpoint.

2. If you have not already done so, on the Configuration menu, click Storage Destinations.
3. Click the Object Storage tab.

4. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

5. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new S3 Compatible Object Storage destination.
   Provider	Select S3 Compatible from the Provider list.
   Manager Host	Enter the host address for the S3 Compatible Object Storage manager host.
   Manager Port	Enter a decimal integer to specify the port number of the S3 Compatible Object Storage Host's port. The default port number is 80.
   Manager Protocol	Select the HTTP or HTTPS protocol. Note: If you plan to use HTTPS, you may have to create or import a security certificate prior to creating an S3 Compatible Object Storage destination. Follow the documentation from your S3 Object Storage system's vendor to set this up on your Object Storage system. Also, see HTTPS Default CA ROOT Certificate File or Path for additional information on how to configure your customized CA PEM files on your StorNext system.
   Authentication	This parameter does not apply to the S3 Compatible Object Storage Destination. Leave it at the default, Disabled.
   User Name	This parameter does not apply to the S3 Compatible Object Storage Destination. Leave it at the default, blank.
   Password	This parameter does not apply to the S3 Compatible Object Storage Destination. Leave it at the default, blank.

6. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

7. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. Select S3COMPAT from the drop-down list.
   URL Style	There are two ways to format the URL: PATH VHOST This parameter defines which style of URL to use. The recommended option is VHOST.
   Object Access Protocol	Select the protocol to be used for S3 Compatible Object Storage object access. By default, the protocol is set to http.
   Host[:Port]	Enter the connection endpoint address that contains the host name or IP address, with the optional port number separated by a colon ":". If the port number is not specified, the default (80 for http, 443 for https) is assumed. Connection endpoints must be unique.

   Note: If you are configuring a Scality RING object storage configuration, see Special Considerations for a Scality RING Object Storage Configuration.

   Note: For ActiveScale P100/X100, you can use the controller's IP address to configure the I/O path. If you use the FQDN, then the domain name must match the S3 domain as configured in the ActiveScale P100/X100 S3 domains. Only the PATH URL style is supported.

8. In the Containers section, perform one of the following:
   1. In the Container Selection list, click Scan or Manual. This parameter gives you the option to either scan the available container or enter the container name manually.
      • If you select Scan, check the Use different credentials box and enter the username (the Access Key ID) and password (the Secret Access Key). You are then presented with a pre-populated list of available containers when you add a container.
      • If you select Manual, you are presented with a text box to manually enter the name of the container. To view or add Object Storage buckets, on the Tools menu, click Object Storage Buckets.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Select (Scan mode), or enter (Manual mode) the name of your Object Storage bucket.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Select S3COMPAT from the drop-down list.
      Storage Class	Specify the storage class of your S3 bucket's life-cycle property. Most configurations use the default standard storage class. Note: Always verify the value matches the value configured for the S3 bucket itself. Available values include: standard: AWS S3 Standard storage class. standard_ia: AWS S3 Standard Infrequent Access storage class. Objects are available for quick access but there is a retrieval fee for the objects. glacier: AWS S3 Glacier Flexible Retrieval storage class using standard retrievals to access data within 3-5 hours. glacier_exp: AWS S3 Glacier Flexible Retrieval storage class using expedited retrievals to access data within 1-5 minutes. glacier_bulk: AWS S3 Glacier Flexible Retrieval storage class using bulk retrievals to access data within a day. glacier_deep: AWS S3 Glacier Deep Archive storage class using standard retrievals to access data within 12 hours from Glacier Deep Archive storage. glacier_deep_bulk: AWS S3 Glacier Deep Archive storage class using bulk retrievals to access data within 48 hours from S3 Glacier Deep Archive storage. Note: See the provider documentation for detailed information on supported storage classes, including cost and retrieval times.
      Signing Type	Specify the signing type for the requests sent to the S3 Compatible Object Storage server. Available values include V2 and V4. To use V4, the server must support V4 signing for both AWS full payload and chunked uploading. Note: When configuring the signing type for containers from the Scality RING Object Storage system, set this parameter at V2, until Scality supports V4 chunked uploading.
      Authentication Type	Specify the authentication type for the container being configured. An authentication type is required for all S3 Compatible media. Use the default value of STANDARD, which authenticates with an Access Key ID and Secret Access Key.
      User Name	Enter the Access Key Id for this container.
      Password	Enter the Secret Access Key for this container.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If you leave this as System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details.
      Batch Delete	Note: You must first determine if the batch delete operation is supported on your object storage server. Refer to your object storage server provider. This parameter offers "multiple object delete" functionality that allows IDs of multiple objects to be placed in one HTTP request, so that all of the listed objects can be deleted with one request. To enable this functionality, click the check box.

      Note: If no data has been written to a controller, I/O path, or container, click Delete to remove the item, and then click Apply to save the changes.

9. (Optional) Repeat Step 8 to add more containers to the same S3 Compatible Object Storage Destination.

10. Click Apply to save your changes, or Cancel to exit without saving.

11. (Optional) Repeat Step 4 through Step 10 to add additional S3 Compatible Object Storage Destinations.

Special Considerations for a Scality RING Object Storage Configuration

Use the Host name to configure the I/O Path for the Scality RING Object Storage system.

If you are not using an IP address as an endpoint to Scality, the default Host name endpoint for Scality is to emulate Amazon AWS S3 (for example, s3.amazonaws.com). This configuration is provided in the config.json file on the Scality host. Using any other host name as an endpoint (for example, my-scality.host.com) does not work, even if the name resolves to the correct IP address. If you do this, Scality will reject the request with the error message HTTP/1.1 400 Bad Request.

If you want to use the hostname configured by default on Scality, you can configure your server to use s3.amazonaws.com as the endpoint. However, also ensure that the name resolves to the IP address of your Scality host.

If your Scality host's IP address is 10.65.191.2, you can resolve s3.amazonaws.com by having the following entry in your /etc/hosts file:

10.65.191.2 s3.amazonaws.com

If you want to use a DNS name that is not the default on Scality, modify the config.json file on the scality host:

# cat config.json | grep my-scality
"localregion": ["my-scality.host.com"]

You must also have an entry in your /etc/hosts file that resolves this DNS name correctly:

10.65.191.2 my-scality.host.com

Quantum recommends that you consult Scality for further guidance.

Follow this procedure to edit an existing S3 Compatible Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the S3 Compatible Object Storage destination whose information you want to edit.

4. Click Edit....

5. To edit a field, type directly in the field (for example, type a new name and IP address for an I/O path), or select another option from the drop-down list.

   Note: To return to the last saved configuration for a controller, I/O path, or namespace, click Reset.

6. Click Apply to save your changes, or Cancel to exit without saving.

7. When a confirmation message appears, click Yes to proceed, or No to abort.

8. After a message informs you that the S3 Compatible Object Storage destination was successfully modified, click OK.

Follow this procedure to delete an existing S3 Compatible Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the S3 Compatible Object Storage destination you want to delete.

4. Click Delete.

5. When a confirmation message appears, click Yes to proceed with the deletion or No to abort.

6. After a message informs you that the Object Storage destination was successfully deleted, click OK.

A Multi-Geo (multiple geographic) P100/X100 configuration consists of three sites configured under the same durability policy.

The Object Storage Destination for a multi-geo configuration should have all controllers and IO paths configured, using either the StorNext GUI or fsobjcfg command. With this type of configuration, it is likely that WAN (Wide Area Network) communications with remote sites are slower due to the higher latency in the WAN link.

Note: If you have significantly higher latency to the remote sites, Quantum recommends you disable the links.

You can configure Object Storage I/O Paths to be offline in the Tools > Storage Manager > Storage Components page. To do so, select the remote Object Storage I/O Paths that you want to set as offline and then click the Offline button (see Change the Current State of Object Storage Destinations, Controllers, and I/O Paths). You can also use the fschstate(1) command for this.

Note: If the local P100/X100 controller is down, but the remote sites are still operational, disable the local I/O paths and set the remote I/O paths to the Online state to continue using the P100/X100.

To protect your data, Quantum recommends you use the HTTPS protocol for the data transfer. SeeAdd a New S3 Compatible Object Storage Destination for more details on how to configure a certificate.

1. Data ingested from editorial stations using SMB, NFS, or StorNext protocols.

2. Two (2) copies of each ingested files are stored after policy based time to Amazon S3 and/or Amazon S3 Glacier Flexible Retrieval. The default policy is five (5) minutes.

3. Archived files are truncated to reclaim space after policy based duration and when they meet their protection and last accessed policies.

4. Clients accessing archived files initiate a transparent restore from the archive tier using a StorNext API or by access file directly from the file system.

The Storage Manager media and policy configuration must be compatible with the Amazon Web Services configuration for the corresponding S3 bucket. This is important, particularly when enabling encryption or configuring the S3 Glacier Flexible Retrieval storage class.

If an S3 Glacier Flexible Retrieval life-cycle policy has been defined on AWS for a bucket, the S3 Glacier Flexible Retrieval storage class must be specified when configuring the media in the Storage Manager. If the storage class is not set to S3 Glacier Flexible Retrieval, data migrated to S3 Glacier Flexible Retrieval cannot be retrieved.

Storage Manager supports both server-side encryption with S3-managed keys and server-side encryption with KMS-managed keys. The encryption type is configured in the storage policy. The Storage Manager policy should be consistent with the AWS bucket properties.

If Storage Manager encryption is not enabled and AWS bucket encryption is enabled but not mandatory, the data will be encrypted. However, if mandatory encryption is configured on the AWS bucket, store requests will fail unless encryption has been configured in the Storage Manager policy. The media will then be write-protected to prevent further unauthorized access. The Storage Manager encryption type will override the AWS bucket encryption property in the event that the two differ.

By default, Storage Manager supports access to AWS buckets using the region endpoints listed in the file /usr/cvfs/config/awsregions.json.template. If you require access to a bucket created in a region not listed in this file, or require the use of a regional Security Token Service endpoint not listed in this file, you can modify this file to allow access.

For each new endpoint that you want, add an entry in the following format, where both region-value and endpoint-value are JSON strings:

   {
           "region":region-value,
           "endpoint":endpoint-value
   }

Note: Buckets in the newly specified region will not be accessible through Storage Manager until after the next Storage Manager restart.

Follow this procedure to view a list of currently configured AWS Object Storage destinations.

1. On the Configuration menu, click Storage Destinations.
2. Click the Object Storage tab. Information for any previously configured AWS Object Storage destinations is shown as entries that have AWS listed as the Provider. For each configured destination, the screen displays the Name, Provider, Appliance State (Online or Offline), Controller State, I/O Path State, Manager host address, Containers count, Controllers count, I/O Paths count, and File Count.
3. Select the AWS Object Storage destination whose information you want to view.
4. Click View....
5. When you are finished viewing the destination information, click Done.

Before configuring the AWS Object Storage Destinations with Storage Manager for AWS STANDARD authentication, complete the following steps, which apply to both AWS public cloud and GovCloud:

• Have your AWS IAM Access Key Id and Secret Access Key ready.
• Ensure that the S3 buckets that you are configuring with Storage Manager have been created with AWS, and that you know the names and the AWS region endpoints of your buckets.

Follow the procedure below to add a new AWS Object Storage destination that uses STANDARD authentication.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.
2. Click the Object Storage tab.

3. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

4. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new AWS Object Storage destination
   Provider	Select AWS from the Provider list.
   Manager Host	Enter s3.amazonaws.com for the AWS Object Storage Manager Host's address.
   Manager Port	Enter 443 for the AWS Object Storage Manager Host's port.
   Manager Protocol	Select HTTPS.
   Authentication Type	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, Disabled.
   User Name	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.
   Password	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.

5. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

6. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. Select AWS from the drop-down list.
   URL Style	There are two ways to format the URL: PATH VHOST This parameter defines which style of URL to use. The recommended option is VHOST.
   Object Access Protocol	Specify the network protocol to be used for the host. Select HTTPS from the drop-down list.
   Host[:Port]	Enter the AWS region endpoint for your S3 bucket. For example: s3-us-west-2.amazonaws.com for an S3 bucket created in the US West (Oregon) region s3.amazonaws.com for an S3 bucket created in the US East (N. Virginia) region s3-us-gov-west-1.amazonaws.com for an S3 bucket created in AWS GovCloud

7. In the Containers section, perform the following:
   1. Leave the Container Selection at the default, Manual.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Enter the name of your S3 bucket.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Select AWS from the drop-down list.
      Storage Class	Specify the storage class of your S3 bucket's life-cycle property. Always make sure that this value matches the value configured for the S3 bucket itself. Available values include: standard: AWS S3 Standard storage class. standard_ia: AWS S3 Standard Infrequent Access storage class. Objects are available for quick access but there is a retrieval fee for the objects. glacier: AWS S3 Glacier Flexible Retrieval storage class using standard retrievals to access data within 3-5 hours. glacier_exp: AWS S3 Glacier Flexible Retrieval storage class using expedited retrievals to access data within 1-5 minutes. glacier_bulk: AWS S3 Glacier Flexible Retrieval storage class using bulk retrievals to access data within a day. glacier_deep: AWS S3 Glacier Deep Archive storage class using standard retrievals to access data within 12 hours from Glacier Deep Archive storage. glacier_deep_bulk: AWS S3 Glacier Deep Archive storage class using bulk retrievals to access data within 48 hours from S3 Glacier Deep Archive storage. Most configurations use the default standard storage class. Note: The cost of retrieval from an S3 Glacier Flexible Retrieval storage class varies by retrieval time, with the quickest retrieval type having the highest cost. See Amazon S3 pricing.
      Signing Type	Specify the signing type for the requests sent to the AWS Object Storage server. Available values include V2 and V4 (default).
      Authentication Type	Specify the authentication type for the container being configured. Available values include: STANDARD STS_PUBLIC STS_GOVCLOUD CAP Select the default of STANDARD, because you are configuring the container to use STANDARD authentication.
      User Name	Enter the Access Key Id for this container.
      Password	Enter the Secret Access Key for this container.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If left at System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details.
      Batch Delete	Note: You must first determine if the batch delete operation is supported on your object storage server. Refer to your object storage server provider. This parameter offers "multiple object delete" functionality that allows IDs of multiple objects to be placed in one HTTP request, so that all of the listed objects can be deleted with one request. To enable this functionality, click the check box.

      Note: If no data has been written to a controller, I/O path, or container, click Delete to remove the item, and then click Apply to save the changes.

8. (Optional) Repeat Step 7 to add more containers to the same AWS Object Storage Destination.

9. Click Apply to save your changes, or Cancel to exit without saving.

10. (Optional) Repeat Step 3 through Step 9 to add additional AWS Object Storage Destinations.

Before configuring the AWS Object Storage Destinations with Storage Manager for AWS STS authentication, complete the following steps, which apply to both AWS public cloud and GovCloud

1. Have your AWS IAM Access Key Id and Secret Access Key ready.
2. Ensure that the S3 buckets to be configured in Storage Manager exist, and that you know both the name and the AWS region for each.

3. Ensure that the IAM roles and their managed policies have been defined for your S3 buckets with AWS, and that you know the roles' Amazon Resource Names (ARNs). Below is an example of a role's managed policy that Storage Manager recommends.

                                               
                                               
   {
   	"Version": "2012-10-17",
   	"Statement": [
   		{
   			"Effect": "Allow",
   			"Action": "s3:ListAllMyBuckets",
   			"Resource": "arn:aws:s3:::*"
   		},
   		{
   			"Effect": "Allow",
   			"Action": [
   				"s3:ListBucket",
   				"s3:GetBucketLocation"
   			],
   			"Resource": "arn:aws:s3:::joe-bucket"
   		},
   		{
   			"Effect": "Allow",
   			"Action": [
   				"s3:GetObject",
   				"s3:PutObject",
   				"s3:DeleteObject",
   				"s3:AbortMultipartUpload"
   				"s3:RestoreObject"
   			],
   			"Resource": "arn:aws:s3:::joe-bucket/*"
   		}
   	]
   }

Note: The Action "s3:RestoreObject" is only required if you are using an S3 Glacier Flexible Retrieval storage class for your S3 bucket's life-cycle property.

Follow this procedure to add a new AWS Object Storage destination that uses STS authentication.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.
2. Click the Object Storage tab.

3. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

4. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new AWS Object Storage destination.
   Provider	Select AWS from the Provider list.
   Manager Host	Enter s3.amazonaws.com for the AWS Object Storage Manager Host's address.
   Manager Port	Enter 443 for the AWS Object Storage Manager Host's port.
   Manager Protocol	Select HTTPS.
   Authentication Type	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, Disabled.
   User Name	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.
   Password	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.

5. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

6. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. Select AWS from the drop-down list.
   URL Style	There are two ways to format the URL: PATH VHOST This parameter defines which style of URL to use. The recommended option is VHOST.
   Object Access Protocol	Specify the network protocol to be used for the host. Select HTTPS from the drop-down list.
   Host[:Port]	Enter the AWS region endpoint for your S3 bucket. For example: s3-us-west-2.amazonaws.com for an S3 bucket created in the US West (Oregon) region s3.amazonaws.com for an S3 bucket created in the US East (N. Virginia) region s3-us-gov-west-1.amazonaws.com for an S3 bucket created in AWS GovCloud

7. In the Containers section, perform the following:
   1. Leave the Container Selection at the default, Manual.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Enter the name of your S3 bucket.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Select AWS from the drop-down list.
      Storage Class	Specify the storage class of your S3 bucket's life-cycle property. Always make sure that this value matches the value configured for the S3 bucket itself. Available values include: standard: AWS S3 Standard storage class. standard_ia: AWS S3 Standard Infrequent Access storage class. Objects are available for quick access but there is a retrieval fee for the objects. glacier: AWS S3 Glacier Flexible Retrieval storage class using standard retrievals to access data within 3-5 hours. glacier_exp: AWS S3 Glacier Flexible Retrieval storage class using expedited retrievals to access data within 1-5 minutes. glacier_bulk: AWS S3 Glacier Flexible Retrieval storage class using bulk retrievals to access data within a day. glacier_deep: AWS S3 Glacier Deep Archive storage class using standard retrievals to access data within 12 hours from Glacier Deep Archive storage. glacier_deep_bulk: AWS S3 Glacier Deep Archive storage class using bulk retrievals to access data within 48 hours from S3 Glacier Deep Archive storage. Most configurations use the default standard storage class. Note: The cost of retrieval from an S3 Glacier Flexible Retrieval storage class varies by retrieval time, with the quickest retrieval type having the highest cost. See Amazon S3 pricing.
      Signing Type	Specify the signing type for the requests sent to the AWS Object Storage server. Available values include V2 and V4 (default).
      Authentication Type	Specify the authentication type for the container being configured. Available values include: STANDARD STS_PUBLIC STS_GOVCLOUD CAP Because you are configuring your bucket to use STS authentication, select STS_PUBLIC if your bucket is in AWS public cloud. Select STS_GOVCLOUD if your bucket is in AWS GovCloud.
      Role	Specify the Amazon Resource Name (ARN) of the IAM role to assume for obtaining temporary credentials. Enter the IAM role's ARN defined to access this container.
      Role Duration	Specify the duration, in seconds, of the role session or temporary credentials. The value must be in the range 900 to 3600. A default value of 3600 seconds is used if a role duration is not specified.
      Authentication Endpoint	Specify an alternate authentication endpoint, which is used to override the default STS server for the AWS public or GovCloud region. If you choose not to specify an authentication endpoint, leave it at the default, blank.
      User Name	Enter the Access Key Id for this container.
      Password	Enter the Secret Access Key for this container.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If left at System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details.
      Batch Delete	Note: You must first determine if the batch delete operation is supported on your object storage server. Refer to your object storage server provider. This parameter offers "multiple object delete" functionality that allows IDs of multiple objects to be placed in one HTTP request, so that all of the listed objects can be deleted with one request. To enable this functionality, click the check box.

      Note: If no data has been written to a controller, I/O path, or container, click Delete to remove the item, and then click Apply to save the changes.

8. (Optional) Repeat Step 7 to add more containers to the same AWS Object Storage Destination.

9. Click Apply to save your changes, or Cancel to exit without saving.

10. (Optional) Repeat Step 3 through Step 9 to add additional AWS Object Storage Destinations.

If you use CAP authentication, complete the following steps prior to configuring an object storage destination:

1. Ensure that the S3 buckets, to be used by Storage Manager, have been created with AWS FedCloud (C2S account) and that you know the names and the AWS region endpoint of each bucket.
2. Ensure that the IAM roles and their managed policies have been defined for your S3 buckets with AWS FedCloud (C2S account). See the example of a managed policy which includes the required capabilities of the role.
3. Ensure that you have the following information:
   1. The IAM role associated with your C2S account
   2. The agency associated with your C2S account
   3. The mission associated with your C2S account
   4. Your CAP server connection endpoint.
   5. Your customized certificate authority (CA) file in PEM format.
   6. Your X.509 client certificate in PEM format, and any applicable private key file or passphrase.
4. Add the following Storage Manager system parameters to the file /usr/adic/TSM/config/fs_sysparm_override on the StorNext system to enable Storage Manager to communicate with the CAP server:

   1. FS_OBJSTORAGE_C2S_CAP_HOSTPORT identifies the connection endpoint for the CAP server and can be configured as follows:

      FS_OBJSTORAGE_C2S_CAP_HOSTPORT=cap-portal:port;

   2. FS_OBJSTORAGE_CAPATH identifies the directory in which the issuer's certificate authority (CA) can be found if it is not already included in the operating system's default trusted root certificate file.

      Note: The certificate should be in PEM format.

      For example, the certificate can be copied to /usr/cvfs/config/ssl and configured as follows:

      FS_OBJSTORAGE_CAPATH=/usr/cvfs/config/ssl;

      Note: If your customized CA PEM file contains more than one certificate, we recommend that you append the content of your customized CA PEM file to your operating system's default CA bundle, and that you DO NOT use sysparm FS_OBJSTORAGE_CAPATH to set the location of your customized CA PEM file. Alternatively, you could split your CA PEM file into multiple CA PEM files, each of which contains a single CA certificate, and use sysparm FS_OBJSTORAGE_CAPATH to set the location of your newly split single certificate CA PEM files. See HTTPS Default CA ROOT Certificate File or Path for additional information on how to configure your customized CA PEM files.

   3. FS_OBJSTORAGE_CLIENTCERT identifies the location of the X.509 client certificate installed on the system for the CAP server to authenticate.

      Note: The certificate should be in PEM format.

      For example, the client certificate can be copied to /usr/cvfs/config/ssl/client-cert-filepath, and configured as follows:

      FS_OBJSTORAGE_CLIENTCERT=/usr/cvfs/config/ssl/client-cert-filepath;

   4. FS_OBJSTORAGE_CLIENTKEY sets the location of the client private key if the client private key is kept separately from (for example, not included in) the client certificate file. This parameter can be configured as follows:

      FS_OBJSTORAGE_CLIENTKEY=/usr/cvfs/config/ssl/client-key-filename;

   5. FS_OBJSTORAGE_CLIENTKEY_PASS specifies the passphrase used to protect the client private key and can be configured as follows:

      FS_OBJSTORAGE_CLIENTKEY_PASS=passphrase;

5. Execute the following command to generate the hash for your certificates:

   /opt/quantum/openssl/bin/c_rehash /usr/cvfs/config/ssl

6. Restart TSM to allow the system parameter changes to take effect.

Note: You can also use the GUI's Tools > Storage Manager > System ParametersTools > Storage Manager > System Parameters page to set the system parameters shown above.

Add a new AWS Object Storage destination that uses CAP authentication.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.
2. Click the Object Storage tab.

3. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

4. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new AWS Object Storage destination.
   Provider	Select AWS from the Provider list.
   Manager Host	Enter s3.amazonaws.com for the AWS Object Storage Manager Host's address.
   Manager Port	Enter 443 for the AWS Object Storage Manager Host's port.
   Manager Protocol	Select HTTPS.
   Authentication Type	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, Disabled.
   User Name	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.
   Password	This parameter does not apply to AWS Object Storage Destination. Leave it at the default, blank.

5. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

6. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. Select AWS from the drop-down list.
   URL Style	There are two ways to format the URL: PATH VHOST This parameter defines which style of URL to use. The recommended option is VHOST.
   Object Access Protocol	Specify the network protocol to be used for the host. Select HTTPS from the drop-down list.
   Host[:Port]	Enter the AWS region endpoint for your S3 bucket.

7. In the Containers section, perform the following:
   1. Leave the Container Selection at the default, Manual.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Enter the name of your S3 bucket.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Select AWS from the drop-down list.
      Storage Class	Specify the storage class of your S3 bucket's life-cycle property. Always make sure that this value matches the value configured for the S3 bucket itself. Available values include: standard: AWS S3 Standard storage class. standard_ia: AWS S3 Standard Infrequent Access storage class. Objects are available for quick access but there is a retrieval fee for the objects. glacier: AWS S3 Glacier Flexible Retrieval storage class using standard retrievals to access data within 3-5 hours. glacier_exp: AWS S3 Glacier Flexible Retrieval storage class using expedited retrievals to access data within 1-5 minutes. glacier_bulk: AWS S3 Glacier Flexible Retrieval storage class using bulk retrievals to access data within a day. glacier_deep: AWS S3 Glacier Deep Archive storage class using standard retrievals to access data within 12 hours from Glacier Deep Archive storage. glacier_deep_bulk: AWS S3 Glacier Deep Archive storage class using bulk retrievals to access data within 48 hours from S3 Glacier Deep Archive storage. Most configurations use the default standard storage class. Note: The cost of retrieval from an S3 Glacier Flexible Retrieval storage class varies by retrieval time, with the quickest retrieval type having the highest cost. See Amazon S3 pricing.
      Signing Type	Specify the signing type for the requests sent to the AWS Object Storage server. Available values include V2 and V4 (default).
      Authentication Type	Specify the authentication type for the container being configured. Available values include: STANDARD STS_PUBLIC STS_GOVCLOUD CAP Select CAP, because you are configuring the container to use CAP authentication.
      Role	Specify the IAM role associated with the target C2S account for obtaining temporary credentials. Enter the IAM role associated with your C2S account to access this container.
      Role Duration	Specify the duration, in seconds, of the role session or temporary credentials. The value must be in the range 900 to 3600. A default value of 3600 seconds is used if a role duration is not specified.
      CAP Agency	Specify the CAP agency associated with the target C2S account for obtaining temporary credentials. Enter the agency associated with your C2S account for this container.
      CAP Mission	Specify the CAP mission associated with the target C2S account for obtaining temporary credentials. Enter the mission associated with your C2S account for this container.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If left at System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details.
      Batch Delete	Note: You must first determine if the batch delete operation is supported on your object storage server. Refer to your object storage server provider. This parameter offers "multiple object delete" functionality that allows IDs of multiple objects to be placed in one HTTP request, so that all of the listed objects can be deleted with one request. To enable this functionality, click the check box.

      Note: If no data has been written to a controller, I/O path, or container, click Delete to remove the item, and then click Apply to save the changes.

8. (Optional) Repeat Step 7 to add more containers to the same AWS Object Storage Destination.

9. Click Apply to save your changes, or Cancel to exit without saving.

10. (Optional) Repeat Step 3 through Step 9 to add additional AWS Object Storage Destinations.

Follow this procedure to edit an existing AWS Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the AWS Object Storage destination whose information you want to edit.

4. Click Edit....

5. To edit a field, type directly in the field (for example, type a new name and IP address for an I/O path), or select another option from the drop-down list.

   Note: To return to the last saved configuration for a controller, I/O path, or namespace, click Reset.

6. Click Apply to save your changes, or Cancel to exit without saving.

7. When a confirmation message appears, click Yes to proceed, or No to abort.

8. After a message informs you that the AWS Object Storage destination was successfully modified, click OK.

Follow this procedure to delete an existing AWS Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the AWS Object Storage destination you want to delete.

4. Click Delete.

5. When a confirmation message appears, click Yes to proceed with the deletion or No to abort.

6. After a message informs you that the Object Storage destination was successfully deleted, click OK.

Follow this procedure to view a list of currently configured Azure Object Storage destinations.

1. On the Configuration menu, click Storage Destinations.
2. Click the Object Storage tab. Information for any previously configured Azure Object Storage destinations is shown as entries that have Microsoft Azure listed as the Provider. For each configured destination, the screen displays the Name, Provider, Appliance State (Online or Offline), Controller State, I/O Path State, Manager host address, Containers count, Controllers count, I/O Paths count, and File Count.
3. Select the Azure Object Storage destination whose information you want to view.
4. Click View....
5. When you are finished viewing the destination information, click Done.

Follow this procedure to add a new Azure Object Storage destination.

1. Ensure that the Azure containers that you are configuring with Storage Manager have been created with Microsoft Azure Cloud Services, and that you know the Storage Account Name, Storage Access Key, and names of your Azure containers.
2. If you have not already done so, on the Configuration menu, click Storage Destinations.
3. Click the Object Storage tab.

4. Click New.... The page is updated and displays various configuration prerequisites. If any of these are required, click Cancel and configure them before returning to this page. Otherwise, click Continue....

5. Enter the appropriate value into the following parameters:

   Parameter	Description
   Name	Enter the name of the new Azure Object Storage destination.
   Provider	Select Microsoft Azure from the Provider list.
   Manager Host	Enter portal.azure.com for the Azure Object Storage Manager Host's address.
   Manager Port	Enter 443 for the Azure Object Storage Manager Host's port.
   Manager Protocol	Select HTTPS.
   Authentication Type	This parameter does not apply to Azure Object Storage Destination. Leave it at the default, Disabled.
   User Name	This parameter does not apply to Azure Object Storage Destination. Leave it at the default, blank.
   Password	This parameter does not apply to Azure Object Storage Destination. Leave it at the default, blank.

6. In the Controllers section, click Add and then specify the following to add a controller:

   Parameter	Description
   Name	Enter the name of the controller. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Max Streams	This option defines the maximum number of object storage data transfers that you can execute in parallel. One stream is used for each object storage store or retrieve request and for each object storage source or destination on a copy request. If the number of active object storage requests exceeds Max Streams, then the requests are queued until a stream is available. By default, the maximum number of streams is 48. To change this, select the desired value from the Max Streams drop-down list. Caution: If you set the value too high, then the Storage Manager might consume too much transport bandwidth and negatively impact other applications using the network. You must decide what percentage of the network bandwidth you should reserve for the Storage Manager and set the stream count such that the cumulative stream rate does not exceed this value.
   Read Streams	This option specifies the subset of Max Streams to use for file retrieves. This value must be in the range 0 to Max Streams. The number of retrieves can exceed this count but the reserved streams cannot be used for non-retrieve requests. Note: If the Read Streams value is equal to the maximum stream count, streams are not made available for store requests. By default, streams are not reserved specifically for retrieves.

7. In the I/O Paths section, click Add and then specify the following to add an I/O path:

   Parameter	Description
   Name	Enter the name of the I/O path. Note: The name can be any string of 256 characters or less and is case sensitive. The name cannot already be used by another component.
   Controller Name	Select the name of the controller associated with the new I/O path.
   Media Type	Specify the object storage media type assigned to a namespace that is associated with a specific Object Storage API. Select Azure from the drop-down list.
   URL Style	Leave the URL style at the default, PATH.
   Object Access Protocol	Specify the network protocol to be used for the host. Select HTTPS from the drop-down list.
   Host[:Port]	Enter blob.core.windows.net for the I/O path’s connection endpoint to your Azure containers.

8. In the Containers section, perform one of the following:
   1. In the Container Selection list, click Scan or Manual. This parameter gives you the option to either scan the available container or enter the container name manually.
      • If you select Scan, check the Use different credentials box and enter the username (the Azure Storage Account Name) and a password (the Azure Storage Access Key). The page displays a pre-populated list of available containers when you add container.
      • If you select Manual, the page displays a text box where you can manually enter the name of the container.

   2. Click Add and then specify the following to add a container:

      Parameter	Description
      Container	Select (Scan mode) or enter (Manual mode) the name of your Azure container.
      Media ID	Enter the StorNext Media ID associated with the selected container. Note: The ID can be any string of 16 characters or less and is case sensitive. It must be unique among all configured media IDs.
      Media Type	Select Azure from the drop-down list.
      Storage Class	Specify the storage class for the Azure Object Storage media. Select azure_block_blob or azure_block_blob_archive. Note: If you have an Azure life-cycle policy configured to use the archive tier or you want StorNext to use the archive tier, then use the azure_block_blob_archive storage class. If you use the azure_block_blob storage class, then you cannot retrieve an object from the archive tier.
      Signing Type	Specify the signing type for the requests sent to the Azure Object Storage server. Leave it at the default, azure.
      Authentication Type	Specify the authentication type for the container being configured. Use the default value of STANDARD, which authenticates with the Storage Account Name and Storage Access Key.
      Account Name	Enter the Azure Storage Account Name for this container.
      Key	Enter the Azure Storage Access Key for this container.
      Copy Number	Select the copy number (1-4) assigned to the container. The copy number can be changed if no data has been written to the media.
      Policy Class	Specify the policy class that has exclusive use of the container being configured. If left at System Blank, no policy class association is set for the container, and the container can be used by all policy classes. To configure this parameter, select one of the pre-defined policy classes from the drop-down list for the Policy Class option. See How to Route File Copies to a Specific Object Storage Namespace for additional details.
      Batch Delete	Note: You must first determine if the batch delete operation is supported on your object storage server. Refer to your object storage server provider. Note: Azure does not support Batch Delete.

      Note: If no data has been written to a controller, I/O path, or container, click Delete to remove the item, and then click Apply to save the changes.

      Note: Beginning with StorNext 6.2, the storage class azure_append_blob is no longer supported. Buckets previously configured with this storage class are upgraded to use the azure_block_blob storage class. Objects which have been stored as append blobs are not updated but you can still retrieve them. New objects are stored as block blobs.

      Note: You must rehydrate the data written to the azure_block_blob_archive storage class before the data can be read. This tier feature only applies to Azure Blob storage and General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts do not support tiering. For more information, see the Azure documentation on Blob storage tiers.

9. (Optional) Repeat Step 8 to add more containers to the same Azure Object Storage Destinations.
10. Click Apply to save your changes, or Cancel to exit without saving.
11. (Optional) Repeat Step 4 through Step 10 to add additional Azure Object Storage Destinations.

Follow this procedure to edit an existing Azure Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the Azure Object Storage destination whose information you want to edit.

4. Click Edit....

5. To edit a field, type directly in the field (for example, type a new name and IP address for an I/O path), or select another option from the drop-down list.

   Note: To return to the last saved configuration for a controller, I/O path, or namespace, click Reset.

6. Click Apply to save your changes, or Cancel to exit without saving.

7. When a confirmation message appears, click Yes to proceed, or No to abort.

8. After a message informs you that the Azure Object Storage destination was successfully modified, click OK.

Follow this procedure to delete an existing Azure Object Storage destination.

1. If you have not already done so, on the Configuration menu, click Storage Destinations.

2. Click the Object Storage tab.

3. Select the Azure Object Storage destination you want to delete.

4. Click Delete.

5. When a confirmation message appears, click Yes to proceed with the deletion or No to abort.

6. After a message informs you that the Object Storage destination was successfully deleted, click OK.

Azure storage offers different storage tiers. This allows you to store blob object data in a cost-effective manner. The available tiers include:

• Hot storage which is optimized for frequently accessed data.
• Cool storage which is optimized for infrequently accessed data.
• Archive storage which is optimized for rarely accessed data.

Note: This tier feature only applies to Azure Blob storage and General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts do not support tiering.

You can use the fsazure command to report or change the tier state of an Azure Block Blob. If you change from Archive tier to Hot tier or Cool tier, then you cause asynchronous rehydration.

See to the fsazure man page for additional information on the fsazure command, command syntax usage, and examples.

The following is the usage output when you execute the fsazure -h command:

USAGE: fsazure  -h
       fsazure  -u <url> [-U username -P password]
                [-a serverAuth] [-C certfile | -R certpath]
                -o objectId -n container
                -s | S tier

   url               - full and complete object url
   username/password - Username/password for the bucket|container
   serverAuth        - Server authentication 0-None, 1-peer only, 2-peer and host.
   certfile          - The full path to the certificate file
   certpath          - The full path to the location of the certificates
   objectId          - The object identifer
   container         - The Azure container
   -s                - Show object tier and state
   -S                - Set object tier Cool, Hot or Archive