The Q-Cloud Protect appliance provides data replication capabilities that you can use as an integral part of a disaster recovery plan.
Replication allows you to copy data from a DXi appliance or OpenStorage (OST) server to your Q-Cloud Protect appliance at scheduled intervals (or manually as needed). Q-Cloud Protect protects this replicated data in AWS S3 storage.
In the event of a disaster in which the original data is lost, you can quickly recover the replicated data on the Q-Cloud Protect appliance. As soon as the original system is available again, you can restore all data back to it from the cloud appliance. This recovery allows your business to efficiently resume normal operations.
You can perform the following tasks from the Replication page:
Understanding Data Replication
During data replication, data is sent from one system (the source) to another system (the target), such as from your central office on-site DXi appliance to the Q-Cloud Protect appliance.
Sources send replicated data, and targets receive replicated data. The Q-Cloud Protect appliance can receive data from 1 source, and replicate data back to a single target. Although the cloud appliance is mainly used as a target for replicated data, it can serve as a source in failback recovery scenarios.
Replication works only with deduplicated and compressed data. Therefore, the amount of data transmitted between systems during replication is greatly reduced as compared to the original amount of data stored on the source.
In addition, a data block on the source is transmitted only if the target does not already have a copy of that block. You have the option to encrypt data before it is transmitted.
The Q-Cloud Protect appliance can perform the following types of replication.
Replication occurs when a NAS share or VTL partition on a source DXi appliance is configured to point to the cloud appliance as the target system. Similarly, the cloud appliance must be configured to accept data from the source system.
To optimize the replication process, deduplicated data is continuously sent in the background from the source system to the target system. However, a snapshot that preserves the file structure of your data is sent to the target system only when a scheduled or manual replication job occurs. A snapshot contains all of the information that is necessary to recreate data stored on the source system just as it was at the point in time when the snapshot was created.
Caution: A saved snapshot is necessary to recover your data at a later time. For this reason, it is not enough to simply enable replication. You must also configure a replication schedule (recommended) or perform manual replication on a regular basis to send snapshots of the source data to the target system.
If the source system ever becomes unavailable, you can recover the data protected by the cloud appliance using a snapshot. After you recover the data on the cloud appliance, is available for failback recovery. When the source system becomes available again, you can perform a failback operation to restore the data to its original location.
Like replication, Directory/File or Cartridge Based Replication sends data from a NAS share or VTL partition on a source DXi appliance to the cloud appliance, where it is protected. However, Directory/File or Cartridge Based Replication differs in a number of important ways:
- Both replication and Directory/File or Cartridge Based Replication must be enabled for the share or partition.
A unique Sync ID is used to associate the replicated share or partition on the source system with the share or partition that will receive the replicated data on the target system.
You do not need to schedule or manually perform Directory/File or Cartridge Based Replication through the virtual console. Instead, replication is triggered when a file is closed or a period of time after it is modified (NAS shares), or when a tape cartridge is unmounted (VTL partitions).
- For CIFS shares, a file is replicated immediately after it is closed. For NFS shares, a file is replicated after it has been idle (not accessed) for several minutes.
- To optimize the replication process, deduplicated data is continuously sent in the background from the source system to the target system. Any remaining data is sent (along with metadata) at the time a file is closed or a tape cartridge is unmounted.
After files or cartridges are replicated using Directory/File or Cartridge Based Replication, they are automatically recovered on the target system and are immediately available for use. There is no need to first recover the share or partition to access its data.
- Deletions are automatically propagated from the source system to the target system in order to free up space on the target.
If you delete a share configured for Directory/File Based Replication on the source DXi appliance, the share is not automatically deleted on the cloud appliance. If you do not want to retain the share on the cloud appliance, you can manually delete it.
- You can manually initiate a synchronization from the source system at any time. Synchronizing ensures that the contents of the source are exactly the same as the target.
Caution: Cartridge barcodes for all source systems that are replicating to the same target must be unique.
The Q-Cloud Protect appliance can duplicate the data on an LSU (logical storage unit) to another location using the OST optimized duplication (OST replication) feature supported by Veritas NetBackup and Backup Exec with DXi Accent enabled.
For information about configuring and using OST optimized duplication, see Configure OST.
Concurrent Optimized Duplication, Automatic Image Replication, and NetBackup Accelerator are not supported by Q-Cloud Protect.