We are very excited to share with you VPLEX CloudArray integration that extends the key VPLEX use case of mobility to public and private cloud storage. The use case for cloud storage behind VPLEX hinges on frequency of use: cold data that is accessed much less frequently can be pushed to volumes on CloudArray and its extension to public and private cloud. This saves valuable primary storage and helps you take advantage of more cost effective cloud storage for cold data. More details in this great white paper by Don Kirouac.

vplex cloudarray.png

Following are some use cases that show the need for varying frequency of data access:


Splunk host/warm/cold/frozen tiering - CA to provide frozen/cold tiers

Splunk is an application that collects logs from datacenter equipment and enables query functionality on those logs.  It collects enormous amounts of data over time.  Since the more recent information is generally more interesting to queries / analytics, Splunk has the ability to tier data (typically by time) into hot/warm/cold/frozen tiers.  The frozen tier is not included in any queries at all unless it is promoted back to cold. It is possible to store cold / frozen tiers on CloudArray so that faster and more expensive primary storage arrays are freed up.  They would only have to serve the hot/warm tiers in this case.


Microsoft Exchange archive mailboxes

Due to cost concerns, users are often provided mailboxes which are too small.  Users can then use archive mailboxes to store older emails for posterity and this is common practice.  Exchange even allows one to setup policies to automatically move older emails to an archive mailbox. With CloudArray, it is possible to host the inbox on primary storage and archive mailboxes on cloud-based storage for lower cost.  Since archive mailboxes are accessed less frequently, CloudArray provides adequate performance to host these.


Oracle and DB2 Database partitioning by key (i.e. timestamp)

Databases such as Oracle 12c and DB2 offer the capability to partition tables by a primary key – which could be a date.  In this way, older data can be stored in a separate table which can live on slower storage – such as CloudArray.  Since it is touched less frequently by database queries and since the database queries that do access these records tend to be Decision Support workloads (sequential in nature) the performance of CloudArray is appropriate for hosting this older data.


SQL Server snapshot / backup long term retention, manual tiering

Database administrators often use snapshots for operational recovery of their databases.  The older the snapshot, the less likely it is to be used.  With VPLEX and CloudArray, it is possible to migrate snapshots from the primary array to the Cloud so that it can be deleted from the primary array.  This frees up space on the primary array and lowers the total cost of keeping these various copies of the database.


Feel free to share how you plan to take advantage of the cloud tiering capability of VPLEX. We are eager to know.