Find videos, customer case studies, datasheets, whitepapers and more to learn how Commvault can help you make your data work for you.
This document will outline in detail Commvaultâ€™s launch of the new cloud solution sets, extending existing functionality into easily sellable, re-usable architecture patterns that allow protection to the cloud, disaster recovery to the cloud as well as protecting running workloads in the cloud.
Currently this guide focuses on the Amazon public cloud offerings, with expansion planned in the near term to include various other offerings.
Core Cloud Concepts and Technology
The Cloud megatrend represents one of the most disruptive and challenging demands upon our customers applications and infrastructure, forcing new business models and new architecture decisions, which therefore flow onto the decisions on how Commvault can help protect and manage their data.
In general, Commvault believes the cloud contains these attributes that we can focus upon:
- Consumption (Pay for use, easy to consume)
- Easy to consume
- Flexible / Agile / Elastic
The Cloud Connector refers to the native integration within the Media Agent module to directly communicate with Object Storage providers such as AWSâ€™s S3, without requiring translation devices, gateways or VTLs. This native integration is achieved by communicating with the target Object Storageâ€™s REST API interface over HTTPS.
There are many variants of private, public, and hybrid deployment models such as â€œvirtual private cloudâ€ or â€œcommunity cloudâ€. Due to the popularity (and hype) of the cloud, there are many new terms being created to differentiate vendors in a large market. Additionally may use the same terms to refer to different to different things. This can further complicate understanding of the â€™cloudâ€™.
The focus of this document is to familiarize the reader with foundational cloud terminology and which will be utilized throughout the document. The terms below can and will overlap depending on the customer and the particular use case.
Internal cloud deployment within an organization (or service provider), not accessible to the general public for consumption.
â€¢ Ease of Consumption â€“ abstracting existing/new resources
â€¢ On-Premise Security and Compliance
â€¢ Dedicated Service (shared within the organization, not with other orgs)
Deployment available for any customer to consume and the underlying resources are shared among organizations (without any knowledge of each other).
â€¢ Utility Pricing - compared to cost of standing up resources on premise
â€¢ On-demand resource requests - instant/near-instant turnaround for resources (Compute, Storage)
â€¢ Flexibility/ Elasticity
Mixture of private and public cloud, allowing for active workloads to run across cloud types in active/passive or active-active configurations.
â€¢ Utility Pricing for both cloud types
â€¢ Extend on demand resources in to the public cloud on demand
â€¢ Run Production, Dev/Test & DR across both clouds
â€¢ Flexibility/ Elasticity