When working with containers that have Recycle Bin enabled, take the following conditions into consideration.
Container deletion
When deleting a container that has Recycle Bin enabled, you cannot delete the container until Recycle Bin is empty. Be sure to delete or expire all backups from the container and wait for the files to expire from Recycle Bin. When Recycle Bin is empty and the container has no more files, delete the container.
Container replication
Recycle Bin can be configured on the source container only. The same configurations are automatically applied on the peer or replica container. Replication transfers all of the files in the container, including the Recycle Bin files. Restoring files from Recycle Bin is allowed on the source container only. The restored files appear on the replica container as well.
If the target container has files in Recycle Bin, then replication is not allowed. Doing so could prevent replication from being e re-added between a previously configured replication pair. Quest recommends using a new container on the target QoreStor in the same Storage Group as the replica container.
Cloud tier and archive tier
Cloud data also maintains Recycle Bin files. A retention period in a cloud is the same as an on-premises retention period for each file. Files in Recycle Bin must be restored to before they can be restored from Archive storage (Glacier) and later readback.
Disaster recovery
During disaster recovery using cloud data, the files in Recycle Bin are also made available on the recovered QoreStor. The Recycle Bin retention time for all of the files is reset to the last retention time set on the container, which means that all of the files in Recycle Bin are retained for the same number of days from the recovery time.
The number of files in Recycle Bin, their size, and estimated post compression bytes can be seen for each Recycle Bin enabled container.
To view Recycle Bin statistics
- In the QoreStor GUI, click Containers.
- Next the name of the appropriate container, click the Details menu, and then click Recycle Bin.
The available statistics for Recycle Bin display on the page.
For the usage of the stats --container command, see the Quest QoreStor Command Line Reference Guide.
This topic introduces the Cloud Reader feature and related concepts and tasks. Refer to the subsequent topics and procedures in this section for more information.
A QoreStor instance can be configured to read the backups uploaded to a Cloud Tier from a different QoreStor instance. The primary QoreStor, where the Cloud Tier bucket is configured, writes and manages the data in the bucket while another QoreStor instance in Cloud Reader mode can access the same data in Read-Only mode. Any number of Cloud Reader instances can access the cloud bucket data. The data in the cloud is only read by this Cloud Reader instance. A snapshot of the files is made available to the Cloud Reader.
Use cases for cloud reader include Testing and Development and for validating QoreStor disaster recovery.
Operations allowed
Cloud Reader mode is a restrictive mode, where only few QoreStor configuration changes are allowed. For example, new storage groups and containers cannot be created. Only the following actions are allowed:
- Adding QoreStor to Active Directory domain
- Adding Domain Group
- Password changes for the users
- Addition of license
- Diagnostics generation
|
|
NOTE: If a QoreStor instance is only used to read the data in the cloud, then no license is required to be added.
NOTE: Any new data written to the Cloud Reader instance are saved in local storage and not propagated to Cloud Tier. |
Compatibility
Only RDA protocol is supported. NetVault and BridgeHead backup solutions are supported. For the list of supported DMAs, see the QuestQoreStor Interoperability Guide.
