Converse agora com nosso suporte
Chat com o suporte

QoreStor 7.1.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 Understanding system operation scheduling Configuring share-level security for CIFS shares Configuring Secure Connect Enabling MultiConnect 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

Manually restoring datastores from Amazon S3 Glacier

Performing a disaster recovery from an archive tier, involves restoring all datastores to standard Amazon S3 storage, which includes generating the manifest of objects in the cloud bucket used for archive tier and then initiating a Batch Restore from the console.

NOTE: Before performing a recovery, confirm the status of various objects and ensure that they are in warm storage for the duration the readback of data is planned.

To manually restore datastores from Amazon S3 Glacier

  1. Sign in to the AWS Management Console and open the Amazon S3 Console at https://console.aws.amazon.com/s3.
  2. Under Buckets, select the name of the bucket for which you want to configure Amazon S3 inventory.
  3. Click Management.
  4. Under Inventory configurations, click Create inventory configuration.
  5. For Inventory configuration name, enter a name.
  6. Set the Inventory scope by entering the following details:
    • For prefix, enter s3://<cloud_bucket_name>/cds.
    • For object versions, select Current versions only.
  7. Select the following options:
    Table 9: Manifest options
    Option Selection
    Report details Select the location of the AWS account to which you want to save the reports. For example, This account.
    Destination Complete one of the following options:
    • Select the destination bucket where you want to save the reports, or
    • Select a different prefix under the same bucket. For example, s3://<cloud_bucket_name>/manifest.

    NOTE: The destination bucket must be in the same AWS Region as the bucket for which you are setting up the inventory.

    Destination bucket Here you can see the Destination bucket permissions added to the destination bucket policy which allows Amazon S3 to place data in that bucket. For more information, see Creating a destination bucket policy in the documentation for Amazon S3.
    Frequency Select Daily.

    NOTE: The first report may take 24 to 48 hours to generate.

    Output format Select CSV.
    Status Select Enable.
    Server-side encryption Select Disable.
    Additional Fields Do not select any options, as they are not included in the Batch Job submission.

    The manifest file generates.

  8. To initiate the Batch Job for restoring datastores, complete the following steps: 
    1. Navigate to AWS S3 bucket > Management > Inventory Configurations.
    2. Select the latest manifest file.
    3. In the AWS console, to initiate the batch job, click Create Job from Manifest option in AWS console.

Managing replications

In the QoreStor GUI, you can set up and manage data replication operations. Such replication operations include, creating new replication relationships, managing or deleting existing replication relationships, starting and stopping replication, and displaying current replication statistics.

Guidelines and prerequisites for replication

Refer to the following important notes and guidelines for understanding and using replication in QoreStor.

  • TCP Port Configuration—If you plan to perform replication operations across a firewall, the replication service requires that the following fixed TCP ports be configured to support replication operations:
    • port 9904
    • port 9911
    • port 9915
    • port 9916
  • DMAs and Domain Relationships — To allow replication storage information to be viewed by a corresponding data management application (DMA), the target QoreStor system must reside in the same domain as the source QoreStor system in the replication relationship.
  • Replication Limits — Refer to the QoreStor Interoperability Guide for details about the supported system limits for replication. For a definition of connections and streams, see Streams and connections.
  • Version Checking — The QoreStor software includes version checking that limits replication only between other QoreStor systems that run the same system software version. If versions are incompatible, the administrator will be notified by an event, and replication will not continue.
  • Storage Capacity and Number of Source Systems — Be aware that the storage capacity of the target QoreStor system is directly affected by the number of source systems writing to its containers, and also by the amount being written by each of these source systems.
  • Bandwidth limiting — Refer to the replication command in the QoreStor Command Line Reference Guide for information regarding limiting bandwidth consumption for replication.
  • MTU Setting — Primary and secondary replication targets should have the same network maximum transmission unit (MTU) setting.

Adding replication relationships

When configuring replication for object containers, replication must be added from the source system. Also once replication is added for Object container, the replica container is not accessible. Once replication is deleted then the replica becomes accessible over S3 to the clients.

NOTE: For DR-to-QoreStor replication, configure replication from QoreStor.

To add a new replication relationship, complete the following steps.

  1. In the navigation menu, click Replications.
  2. Click Add Replication.
  3. To define the Source Container, select the Local or Remote option.
    • If you select Local, select the local container from the drop-down list.
    • If you select Remote, configure the following settings:
      • Username—enter the username for the remote system.
      • Password—enter the password for the remote system.
      • Remote Machine—enter the domain name of the remote system.
      • Click Retrieve Containers.
      • Select Remote Container—Select the remote container from the drop-down list.
  4. For Encryption, select one of the following encryption options to encrypt the data as it is replicated: None, AES 128–bit, or AES 256–bit.
  5. Under Target Container, define the target replica container by configuring the following settings.
    • Username—enter the username for the remote system.

      NOTE: The credentials used need to be either the admin or administrator account.

    • Password—enter the password for the remote system.
    • Remote Machine—enter the domain name of the remote system.
    • Click Retrieve Remote Containers.
    • Select the remote container from the drop-down list.
  6. Click Next.
  7. Review the summary and click Finish.

NOTE: For information about starting and stopping replication, see the topic, Starting and stopping replication. For information about scheduling system operations such as replication, see Understanding system operation scheduling.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação