Chat now with support
Chat with Support

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

Deploying Cloud Reader

Install QoreStorr with similar mode as the QoreStor that is writing data to the cloud tier bucket. Use the minimal required CPU, memory, and storage as per the Quest QoreStor Interoperability Guide.

After you complete the installation, change the mode by providing the cloud connection details. For details about the maintenance --disaster_recovery and --quick_ro_recovery commands, see the Quest QoreStor Command Line Reference Guide. To refresh the data at any time later, repeat the same command. The existing data is replaced with the file space from cloud bucket.

Example command:

maintenance --disaster_recovery --cloud_string "DefaultEndpointsProtocol=https;AccountName=qorestortest;AccountKey=8Tt7/ysHSGSBSW7FG1Vr2+27xgccskbUWf9GLlGEPeMHYfmVxl+fTg1XYpA==;" --container_name cloud_container1 --cloud_provider_type AZURE --passphrase qqq --logfile /tmp/t1 --quick_ro_recovery yes

Quest recommends that the cloud reader QoreStor instance be in the cloud, but it also works from on-premises.

NOTE: The QoreStor UI does not support initiating Cloud Reader mode. After you deploy Cloud Reader and it is operational, you can use the QoreStor UI for monitoring and configuration changes.

Refreshing data in Cloud Reader

When you run the maintenance command with the --quick_ro_recovery, the QoreStor instance only sees what was in cloud bucket at the time the command was done. Later backup data can become expired from the primary QoreStor instance and the Cloud Tier, and new backup data uploads. To see the new file space view, run the same maintenance command. It erases the current view and retrieves the latest view from the cloud.

Configuring RDA immutability

This topic introduces the RDA immutability feature and related concepts and tasks. Refer to the subsequent topics and procedures in this section for more information.

Understanding RDA immutabilty

RDA immutability provides protection from overwrites and deletes on backup files. This technology is present by default for RDS containers, but not all backups are protected by default. Backup applications sending data using the RDA protocol to QoreStor define whether the backup data should be immutable and the time period the data will remain immutable. After you set immutability on the backup data, you cannot modify or delete the backup data from the RDA container until the immutable time period expires. For the current list of supported backup applications that take advantage of this technology, see the Quest QoreStor Interoperability Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating