Chat now with support
Chat with Support

QoreStor 7.5.2 - User Guide

Introducing QoreStor Accessing QoreStor Configuring QoreStor settings
Licensing QoreStor Configuring SAML Configuring an SSL Certificate for your QoreStor System Configuring Active Directory settings Securing QoreStor server root logins Enabling FIPS 140-2 support Understanding system operation scheduling Configuring Secure Connect Enabling MultiConnect Bandwidth throttling Configuring and using Rapid NFS and Rapid CIFS Configuring and using VTL Configuring and Using Encryption at Rest Configuring and using the Recycle Bin Configuring Cloud Reader Configuring RDA immutability
Managing containers Managing local storage Managing cloud storage Managing replications Managing users Monitoring the QoreStor system Managing QoreStor remotely Support, maintenance, and troubleshooting Security recommendations guide About us

Adding a Cloud Tier through the GUI

IMPORTANT: Your cloud storage must be configured prior to completing this procedure.

The procedures for adding a cloud tier differ slightly based on the cloud storage provider. Review the procedure for your cloud storage provider:

Adding a Microsoft Azure cloud tier

To add a Microsoft Azure cloud storage group, complete the following steps:

  1. In the navigation menu, click Cloud Storage to expand the menu, then click Cloud Tier.
  2. Click Configure.
  3. In the Cloud Provider drop-down, select Azure Blob.
  4. Provide a container name. This is the name of your existing Azure container.
  5. Enter your Cloud Connection String.

    NOTE: The Connection String can be found in your Azure portal under Storage Accounts >Access keys > Connection string.

  6. Enable Cloud Locking : Select this option to achieve immutability of data tiered to the cloud.

    NOTE:Cloud Locking works with RDA, EDM, Object containers only. Data that is set as immutable on the local storage is also set as immutable when tiered to the cloud.

    Enabling locking at the Cloud Tier is required so the containers that are tiering data to this Cloud Tier can choose to enable locking as part of their cloud tiering policy.

  7. To apply encryption, in the Cloud 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.
  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.

Adding an Amazon S3 cloud tier

To add a cloud storage group, complete the following steps

  1. In the navigation menu, click Cloud Storage to expand the menu, then click Cloud Tier.
  2. In the Cloud pane, click Configure to add a cloud tier.
  3. In the Cloud 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. You can obtain your region code 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. You can obtain your region code 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. Enable Cloud Locking: Select this option to achieve immutability of data tiered to the cloud.

    NOTE:Cloud Locking works with RDA, EDM and Object containers only. Data that is set as immutable on the local storage is also set as immutable when tiered to the cloud.

    Enabling locking at the Cloud Tier is required so the containers that are tiering data to this Cloud Tier can choose to enable locking as part of their cloud tiering policy.

    AWS storage classes can be chosen from the following:

    • S3 Standard
    • S3 Intelligent-Tiering
    • S3 Standard-Infrequent Access
    • S3 One Zone-Infrequent Access
    • S3 Glacier Instant Retrieval

    Please note, apart from S3 Standard, other storage classes provide further cost savings for data that is infrequently accessed.

  7. To apply encryption, in the Cloud TierEncryption 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.

  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.

Adding a Wasabi S3 cloud tier

To add a cloud storage group, complete the following steps:

  1. In the navigation menu, click Cloud Storage to expand the menu, then click Cloud Tier.
  2. In the Cloud pane, click Configure to add a cloud tier.
  3. In the Cloud Provider drop-down, select Wasabi S3.
  4. Provide a container name. This is the existing name of your container in your cloud platform.
  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 Wasabi. It is typically 40 characters, including mixed upper and lower-case and special symbols.
      • Region - The region specifies the Wasabi-specific region in which you want to deploy your backup solution. You can obtain your region code from https://wasabi.com/help/docs/.
      • Endpoint - If you are using VPC endpoints, enter the correct endpoint information.
    • 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;endpoint= https://s3.<region>.wasabisys.com;"

      • Wasabi S3 endpoint based on region can be obtained from the following URL:
        https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabis-different-storage-regions

        Please note the following:

        1. The access key is typically 20 upper-case English characters
        2. The secret key is generated automatically by Wasabi. It is typically 40 characters, including mixed upper and lower-case and special symbols.
        3. The region specifies the Wasabi-specific region in which you want to deploy your backup solution. You can obtain your region code from https://wasabi.com/help/docs/.

        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. Enable Cloud Locking: Select this option to achieve immutability of data tiered to the cloud.

    NOTE:Cloud Locking works with RDA, EDM and Object containers only. Data that is set as immutable on the local storage is also set as immutable when tiered to the cloud.

    Enabling locking at the Cloud Tier is required so the containers that are tiering data to this Cloud Tier can choose to enable locking as part of their cloud tiering policy.

  7. To apply encryption, select Encryption and 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.
  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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating