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.
Introducing QoreStor
Understanding the QoreStor documentation
Other information you may need
Source code availability
QoreStor data storage concepts
Accessing QoreStor
Data deduplication and compression
Encryption at rest
Streams and connections
Recycle Bin
Quotas
Secure connect
Replication
Performance Tier
Cloud Tier replication
Archive tier
Object interface (S3-compatible)
Object Direct Storage
Cloud Reader mode
Continuous data protection
Disaster Recovery from the cloud
MSP Mode
Partial File System Checker_OFSCK
Supported file system protocols
CIFS
NFS
Rapid NFS and Rapid CIFS benefits
Rapid NFS and Rapid CIFS
RDA with Quest's NetVault and vRanger
RDA with OST for QoreStor
NDMP
iSCSI
Hardened Repository with Veeam
Anomaly Detection
QoreStor processes
Networking requirements
Configurations required when using proxy servers
Logging onto the system GUI for the first time
Using the QoreStor UI
Using the QoreStor command line interface
Using the QoreStor REST API
Understanding RDA immutabilty
Understanding EDM immutability
Configuring QoreStor settings
Licensing QoreStor
Configuring SAML
Configuring an SSL Certificate for your QoreStor System
Configuring Active Directory settings
Securing QoreStor server root logins
Enabling FIPS 140-2 support
Understanding system operation scheduling
Configuring Secure Connect
Managing containers
Enabling Secure Connect for OST and RDA plug-ins prior to 4.1.0.265
Managing Secure Connect with OST or RDA plug-in 4.1.0.265 or later
Adding certificates for Secure Connect
Enabling MultiConnect
Bandwidth throttling
Adding a throttling schedule from UI
View-Edit a throttling schedule
Removing a throttling schedule from UI
Configuring and using Rapid NFS and Rapid CIFS
Rapid NFS and Rapid CIFS benefits
Best practices: Rapid NFS
Best practices: Rapid CIFS
Installing the Rapid NFS plug-in
Installing the Rapid CIFS plug-in
Uninstalling the Rapid NFS plug-in
Uninstalling the Rapid CIFS plug-in
Configuring and using VTL
Understanding VTL
Terminology
Supported virtual tape library access protocols
VTL and DR Series specifications
Guidelines for configuring VTL
Configuring and Using Encryption at Rest
Understanding Encryption at Rest
Encryption at Rest Terminology
Encryption at rest and QoreStor considerations
Understanding the encryption process
Configuring and using the Recycle Bin
Understanding Recycle Bin
Terminology
Guidelines for configuring Recycle Bin
Configuring Recycle Bin
Purging Recycle Bin files
Restoring files from Recycle Bin
Managing containers with Recycle Bin enabled
Viewing Recycle Bin statistics
Configuring Cloud Reader
Configuring RDA immutability
Creating a container
Managing local storage
Creating an OST or RDS connection type container
Adding an NFS or CIFS connection type container
Creating an Object Container
Creating a VTL type container
Creating EDM connection type container
Viewing containers
Adding a cloud tiering policy
Adding an Archive Tiering policy
Deleting a container
Viewing storage group information
Adding a storage group
Modifying a storage group
Deleting a storage group
Configuring a Performance Tier
Configuring Object Container
Managing cloud storage
Creating an Object Container
Creating a bucket
Editing bucket settings
Changing bucket retention
Managing Object container users
Configuring additional storage
Understanding cloud and archive storage
Adding a Cloud storage group
Managing replications
Adding a Cloud Tier through the GUI
Configuring a Cloud Archive Tier
Adding a Microsoft Azure cloud tier
Adding an Amazon S3 cloud tier
Adding a Wasabi S3 cloud tier
Adding an IBM S3 cloud tier
Adding a Google S3 cloud tier
Adding Scality-Artesca-S3 cloud tier
Adding an S3 Compatible cloud tier
Adding a Backblaze S3 cloud tier
Adding a cloud tier through the command line
Creating a cloud tiering schedule
Editing a cloud tiering schedule
Deleting a cloud tier
Configuring required permissions to restore from Archive Tier
Adding an archive tier
Editing an archive tier restore mode using the command line interface
Deleting an archive tier
Creating an archive tiering schedule
Editing an archive tiering schedule
Restoring from an archive tier
Performing a disaster recovery from the cloud
Guidelines and prerequisites for replication
Adding replication relationships
Configuring replication schedules
Viewing replication information
Modifying replication relationships
Deleting replication relationships
Starting and stopping replication
Managing users
Monitoring the QoreStor system
Using the Dashboard page
Viewing QoreStor statistics by using the CLI
Monitoring system alerts
Monitoring clients
Monitoring system events
Monitoring system events
Managing QoreStor remotely
Getting started with QorePortal
Registering QoreStor with the portal
Enabling Remote Management
Viewing and using QorePortal
Support, maintenance, and troubleshooting
Using the QoreStor support options
Troubleshooting error conditions
Excluding QoreStor directories from antivirus scans
Security recommendations guide
About us
Understanding RDA immutabilty
Understanding EDM immutability
EDM (hardened repository) immutability protects backup files by preventing overwrites and deletions. Veeam sets up an immutability period for backup files that are written to a hardened repository. The files are protected since they are unchangeable during this time.
Furthermore, the same immutability period is applied if the repository is linked to the cloud, locking the backup files both on-prem and in the cloud.
Configuring QoreStor settings
Configuring the DR Series system settings
In the QoreStor GUI, you can easily view and configure system settings such as, active directory, system date and time, expansion shelf enclosures, licenses, networking, schedules for system operations, SSL certificates, storage groups, and users.
Licensing QoreStor
QoreStor offers a backend capacity licensing model to allow for simple integration with other Quest Data Protection products.
- Standalone license - QoreStor is licensed by the amount of backend capacity required. Standalone licenses are available as either perpetual licenses (with no expiration), or term licenses, which expire after a specified period of time.
Perpetual and term QoreStor licenses are additive, meaning that if you purchase a 5 TB license now, and a 10 TB license in the future, you will have 15 TB total capacity. However, all term licenses installed on a QoreStor server must share the same expiration date.
|
|
NOTE: Licenses for QoreStor are specific to the QoreStor server. When installing a license, the System ID for your QoreStor server is required. You can obtain the System ID with the command system --show | grep "System ID" |
Evaluating QoreStor
QoreStor offers two methods for evaluation:
- Default installation - If no license is installed, QoreStor defaults to a no-cost, 1 TB capacity installation supported by the QoreStor Community. This option requires no license and does not expire. If a license is applied to a server running in this mode, the free 1 TB is not added to the purchased license capacity.
- Full capacity trial - available on the Quest Software Trial site, which provides a 30-day evaluation license for up to 360 TB or 512 TB (if MSP support is enabled) and access to Quest Support. After the evaluation period has expired, the QoreStor server will operate in Manual Intervention mode until a license is applied. To use QoreStor beyond that time frame, you will need to purchase a perpetual standalone license. If a longer trial period is required, please contact Quest Sales.
If you have purchased a standalone license, you can install it using the system --license command, as described in the QoreStor Command Line Reference Guide.
|
|
NOTE: When ordering a license, the System ID for your QoreStor server is required. You can obtain the System ID with the command system --show | grep "System ID" |