QoreStor's cloud tiering feature enables QoreStor data to be quickly and easily accelerated to the cloud tier. Using your existing data management applications (DMAs) and any supported protocol, files can be written to a QoreStor container and replicated to your cloud tieraccording to easily defined policies.
QoreStor provides a policy engine that allows you to set idle time and on-premises retention criteria to be used in identifying which files are most suited for replication to the cloud. Policies are defined at the container level and apply to all files within that container. Using the QoreStor Cloud Policy, you can replicate files based on:
In addition, there is an On-Prem Retention Age policy that allows you to specify how long a copy of a file is kept after it has been replicated to the cloud tier. Once a file has been replicated, the file on the QoreStor server becomes a stub, meaning it exists in the namespace but the data exists only in the cloud tier. Once a file has been stubbed and moved to the cloud tier, that file can no longer be edited.
With these policy options, you are able to configure cloud tier replication to meet one of three use cases:
Any data that is transferred from the QoreStor instance by the cloud tier is encrypted with zero knowledge encryption. The encryption keys are solely owned by you. If the encryption keys are placed in the cloud tier, a passphrase is used to encrypt those keys and that passphrase is only known to you. For added security, QoreStor obfuscates metadata names such as blockmap and data store objects that are stored in the cloud tier.
When configured with a Cloud Tier, QoreStor provides the ability to capture QoreStor configuration information as well as storage group and container data. With this information, it is possible to re-create a lost or failed QoreStor server using the data in the cloud.
The disaster recovery process utilizes the QoreStor DRSNAP file, which is a disaster recovery reference file stored in the cloud and encrypted with the same passphrase used to encrypt the encryption keys for the cloud tier. The DRSNAP file is created when a cloud tier is created, and is updated each time a container is created or when the cloud tier passphrase is changed. The DRSNAP file contains:
In the event of QoreStor server failure, a recovery can be initiated on a new, licensed QoreStor server to restore the previous configuration. At a high-level, a recovery will go through the following steps:
|
IMPORTANT: The required passphrase is the passphrase used when created the cloud tier. Without the cloud tier passphrase, recovery is impossible. |
Refer to Performing a recovery from the cloud for more information.
QoreStor supports the following file system protocols. The Rapid Data Access (RDA) protocols below provide a logical disk interface that can be used with network storage devices to store data and support data storage operation.
The Common Internet File System (CIFS) remote file access protocol is supported by QoreStor, and is also known as a Server Message Block (SMB). SMB occurs more commonly than the Network File System (NFS) protocol on systems that run the Microsoft Windows operating system. CIFS allows programs to request files or services on remote computers.
CIFS also uses the client-server programming model, whereby the client requests access to a file or passes a message to a program running on the server. Servers review all requested actions and return a response. CIFS is a public (or open) variation of the SMB that was originally developed and used by Microsoft.
|
NOTE: QoreStor currently supports version 2.0 and 3.0 of the Server Message Block (SMB). |
|
NOTE: For complete details on CIFS feature restrictions, see the QoreStor Interoperability Guide, at support.quest.com/qorestor. |
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center