![]() ![]() Your Comet Server will automatically create subdirectories to store the data for each new Storage Vault. When setting up a Storage Vault for an account, simply assign it a Storage Template. This method can be configured at the Storage Role location on your Comet Server's Settings page. ![]() If your Comet Server is hosted in the same region as the cloud storage account, this may or may not have zero-rated bandwidth cost. Cloud storage credentials won't be exposed to the client using this method. The backup data will pass through the Comet Server first and then the server will upload the data to the cloud storage provider (in memory). Video tutorial Utilizing cloud storage at the Comet Server level generated per-user credentials with separate buckets. Comet will manage the data within the cloud provider's bucket, and generate unique sub-directory level access keys per Storage Vault to minimize the impact this could have if the credentials are acquired.ĭirect-to-cloud also applies for custom Storage Vaults ensure credentials are exclusive to the user, i.e. This means that you only have to setup your cloud provider details once, and then request Storage Vaults when required. It's possible to use the direct-to-cloud method as a Storage Template. The cloud storage credentials will be exposed even though the information is hidden in the Comet Backup client GUI, the customer could still discover it by network analysis or with a software debugger. The backup data will go directly from the desktop client to the cloud storage provider. Utilizing cloud storage at the client level (direct-to-cloud) It is recommended to setup cloud storage at the client level for better performance. The cloud storage provider can be configured at the Comet Server level, or at the client level. Utilizing Cloud Storage with Comet Ĭomet supports any S3-compatible cloud storage provider. These virtual storage locations may combine aspects of physical storage locations in order to offer additional features. local disk, an SFTP server, or Amazon S3), Comet also has a number of virtual storage locations available. Virtual storage locations Īs well as physical storage locations (e.g. The latter may be more efficient and avoids double-handling the bandwidth. The former allows you to leverage cloud resources while still providing a completely opaque front to your customers. This means that you can use any of the supported storage locations as a data location for a Storage Role Comet Server or, you can configure a Storage Vault in Comet Backup to enable backing up to any of the supported storage locations. There is a unified storage model across both Comet Server and the Comet Backup client. The information applies to both (A) configuring a data storage location in Comet Server, and (B) configuring a Storage Vault location for a Comet Backup user (either locally in the Comet desktop client, or remotely via the Comet Server web interface). This document describes the storage locations available in Comet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |