To recover your QoreStor configuration and cloud-replicated data from the cloud, perform the steps below. Before peforming these steps, make sure you have the following:
- A functional, properly licensed QoreStor server.
- The connection string for your cloud storage account. This is different depending on your cloud provider. Refer to the appropriate section below for more information.
To perform a disaster recovery
- On your QoreStor server, run the recovery command
maintenance --disaster_recovery --cloud_string <name> --container_name <name> --cloud_provider_type <name> --passphrase <name> [--logfile <name>]
where
--cloud_string cloud connecion string.
--container_name cloud cotainer name.
--cloud_provider_type cloud provider type.
--passphrase passphrase.
--logfile log file path.
This will regenerate configuration data, initialize the QoreStor dictionary, and configure container namespace and blockmaps. When completed, you will see the message
Processing Datastores: Done
Next steps
Depending on your configuration, there may be several steps required after recovering your QoreStor server. Some actions to consider are:
- If you are using QoreStor with NetVault Backup, you will need to add the new QoreStor as target device and add the container.
- Depnding on your DMA, you may need to reconfigure DMA or client connections to reference the new QoreStor server.
- Once a disaster recovery completes, the recovered source containers will be unencrypted. Before ingesting new data into the recovered containers, you must enabled encryption on the recovered storage groups.
|
|
NOTE:The recovered containers contain only stub files. The data remains encrypted in the cloud tier. |
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.
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_vs_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.
QoreStor supports replication seeding, which provides the ability to create a local seed and place it in a remote system. The seed backup is a process on the source QoreStor system, which collects all of the unique data chunks from the containers and stores them on the target device. This is helpful if you have a new replication target to set up, the amount of data to be replicated is very large, and the network bandwidth is low.
You can seed the target replica with the source data saved on a third party device, for example, a CIFS-mounted share, attach it to the target QoreStor and then get the data into the target QoreStor. Once the seeding is complete, replication is enabled between source and target and replication re-synchronization is done to complete any pending data transfers. Thereby, continuous replication can be done, which reduces network traffic significantly, and data can be replicated and synced with the target in a short amount of time.
|
|
NOTE: The following scenarios are not supported for seeding:
- Import AND export from one share/device cannot occur at the same time.
- Import from one share/device cannot be completed from multiple locations at the same time.
- Export to a mount point can be completed only from one seed job. Multiple seed export jobs cannot send data to a single mount point.
|
You can initiate seeding using the QoreStor command line interface (CLI), and the data to be seeded is gathered in an organized manner and stored in the target devices. Refer to the QoreStor Command Line Reference Guide for more information about replication seeding support.
