Chatee ahora con Soporte
Chat con el soporte

QoreStor 7.0.0 - User Guide

Introducing QoreStor Setting up your QoreStor system Configuring QoreStor settings Managing containers Managing local storage Managing cloud storage Managing replications Managing Users Managing QoreStor Remotely Monitoring the QoreStor system Support, maintenance, and troubleshooting

Deleting a cloud tier

Before deleting a cloud tier, review the details below:

  • The metadata for the files replicated to cloud will be removed locally. This makes those cloud-replicated files unrecoverable.
  • Data in the cloud bucket has to be deleted manually.
  • Cloud policy settings on the source containers are unaffected.

Deleting a cloud tier from the GUI

To delete a cloud tier, complete the following steps.

  1. In the navigation menu, click Cloud Storage to expand the menu, then click Cloud Tier.
  2. Click Delete.
  3. When prompted to confirm, click Delete.
  4. In the Passphrase field, enter the passphrase used for Cloud Tier encryption. This provides validation that the person deleting the cloud tier has the appropriate authorization.
  5. Review the containers linked to the cloud tier and confirm that data in these containers can be deleted. Any containers with managed replication configured must be deleted manually before the cloud tier can be deleted.
  6. Click Delete.

Deleting a cloud tier from the CLI

  1. Access the QoreStor CLI. Refer to Using the QoreStor command line for more information.
  2. Delete your cloud tier using the command below. Refer to the QoreStor Command Line Reference Guide for more information. 
    cloud_tier --delete
  3. At the prompt, enter y for yes and press [Enter].

Configuring an Archive Tier

Archive tiers can be configured via the UI or via the cloud_tier command in the QoreStor CLI. Before configuring an archive tier, ensure the following requirements are met:

  • Your cloud storage must be configured prior to configuring an archive tier.
  • Archive tier is not supported when QoreStor is installed in Cloud Optimized mode, Object Direct Small mode, or Demo mode.
  • Permissions for your cloud storage must be correctly configured. Refer to Required permissions to restore from Archive Tier for more information.
  • Only RDA, VTL, and Object containers can be configured to tier data to Archive Tier.

NOTE: QoreStor's archive tier functionality relies on Amazon S3 Glacier and/or Amazon S3 Glacier Deep Archive storage. Before configuring an archive tier, your cloud archive storage must be properly configured. Please refer to the Amazon S3 documents below for more information:

Required permissions to restore from Archive Tier

In order for Qorestor to be able to perform batch operations for restoring objects to Amazon S3 storage from Amazon S3 Glacier or Amazon S3 Glacier Deep Archive storage , you must configure an AWS IAM policy with the required permissions listed below and attach the policy to your AWS account used to access the for accessing AWS S3 storage.

 

In order for QoreStor to be able to perform batch operations on your S3 storage, you must configure an S3 IAM role with the required permissions and batch operation policy and use that role when creating your archive tier. The permissions required are:

  • Create Job
  • Pass Role
  • The permissions defined in the "Initiate S3 Glacier restore" policy described in the Amazon S3 document Granting permissions for Amazon S3 Batch Operations
    • s3:RestoreObject
    • s3:GetObject
    • s3:GetObjectVersion
    • s3:GetBucketLocation
    • s3:PutObject
    • s3:GetBucketLocation

NOTE: Permission verification is done when restoring an object from S3.

Adding an archive tier

To add an archive tier

  1. In the navigation menu, click Cloud Storage to expand the menu, then click Archive Tier.
  2. In the Archive Tier pane, click Configure to add a cloud tier.
  3. In the archive provider drop-down, select AWS S3.
  4. Provide the name for your S3 bucket.
  5. Enter your Connection String using one of the two methods below:
    • Default - this option will compile your connection string into the correct format using the inputs below.
      • Access key - The access key is typically 20 upper-case English characters
      • Secret key - The secret key is generated automatically by AWS. It is typically 40 characters, including mixed upper and lower-case and special symbols.
      • Region - The region specifies the Amazon-specific region in which you want to deploy your backup solution. Your region name can be obtained from https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
    • Custom - this option allows you to enter your connection string with additional parameters.
      • Your connection string uses the following syntax:
        "accesskey=<ABDCEWERS>;secretkey=< >; loglevel=warn; region=<aws-region>;"

        Please note the following:

        1. The access key is typically 20 upper-case English characters
        2. The secret key is generated automatically by AWS. It is typically 40 characters, including mixed upper and lower-case and special symbols.
        3. The region specifies the Amazon-specific region in which you want to deploy your backup solution. Your region name can be obtained from https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

        An example of a connection string with this syntax follows. Logically, each connection string is unique.

        accesskey=AKIARERFUCFODHFJUCWK;secretkey=p+8/T+o5WeZkX11QbuPazHX1IdWbwgFplxuVlO8J;loglevel=warn;region=eu-central-1;
  6. To apply encryption, in the Archive Tier Encryption section enter the following:

    • Passphrase — the passphrase is user-defined and is used to generate a passphrase key that encrypts the file in which the content encryption keys are kept. The passphrase is a human readable key, which can be up to 255 bytes in length. It is mandatory to define a passphrase to enable encryption.

      IMPORTANT: It is mandatory to define a passphrase to enable encryption. If the passphrase is compromised or lost, the administrator should change it immediately so that the content encryption keys do not become vulnerable. If this passphrase is lost or forgotten, data in the cloud will be unrecoverable.

    • Confirm Passphrase — re-enter the passphrase used above.

  7. In the Archive Tier Options section, enter the following:
    • Archive Retention in Warm Cloud - When restore operation succeeds, a temporary copy of the Glacier object is created in standard S3 storage. This setting specifies the number of days this temporary copy is held in S3 before it is deleted. Valid values are any integral values from 1 through 365.

    • Archive Role ARN - S3 must have permissions to perform batch operations on behalf of the user. An IAM role must be created that has "Create Job", "Pass Role" and other permissions to access the buckets as well as perform the batch operations. The account admin is expected to create such roles.

      NOTE: For more information on required permissions and S3 batch operations, refer to Required permissions to restore from Archive Tier and the AWS documents Granting permissions for Amazon S3 Batch Operations and The basics: S3 Batch Operations.

    • Archive Service Name- Select between S3-Glacier or S3 Deep Archive.
  8. Click Configure. A Cloud Storage Group will be created.
  9. To enable replication to the cloud, you must link a local container to the cloud using the procedures in Adding a Cloud Tiering policy.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación