Introducing Multi-Partition Support for Lucidity Auto-Scaler

At Lucidity, we are committed to providing innovative solutions to optimize cloud storage for our enterprise customers. We understand the challenges that organizations face when it comes to managing their cloud storage, including over-provisioning and downtime during peak hours. An ‘audit’ that we conducted of our customers’ cloud environments, showed that 5 out of 6 customers have multiple data partitions attached to every VM instance. 

Armed with these insights, we are excited to announce the  release of our Multi-Partition support for our Auto-Scaler platform. This new feature will enable our customers to on-board more than one data partition onto the Auto-Scaler platform, providing greater savings and improved performance. The best part? This solution seamlessly integrates with popular cloud service providers AWS and Azure, and supports both Windows and Linux operating systems, making it highly versatile and accessible.

The Pitfalls of over-provisioning cloud storage

Over-provisioning cloud storage, though intended to prevent downtime, has provoked several significant challenges for our customers:

1. Waste of resources: Over-provisioned cloud storage that remains unused can result in resource wastage and unnecessary costs. Shockingly, most enterprise companies observe up to 70% of their storage being wasted!

2. Difficulty in managing storage capacity: Managing a large amount of cloud storage can be challenging, and it may be difficult for a company to keep track of how much storage is being used and how much is available.

Introducing Multi-Partition support for Lucidity Auto-Scaler

With our Auto-Scaler solution, customers can automatically scale their storage up or down based on their actual usage, eliminating the need for over-provisioning. 

Our newly introduced Multi-Partition support takes this one step further by allowing customers to on-board multiple data volumes from the same instance with ease and efficiency. This means that they can easily and efficiently manage their storage across different applications or workloads, without the need for manual intervention. 

Designing an efficient Multi-Partition support solution

After engaging with our customers to understand all the use cases for multi partition support, we identified a few key requirements that our solution had to meet:

1. Flexible Onboarding: Our platform should allow customers to onboard one or multiple data partitions. Customers should also have the option to bulk onboard multiple data volumes.

2. Deboarding Option: Allow customers to deboard a data volume if they desire. While we are completely confident with the value that our solution will offer, we still want to give our customers the ability to deboard one or more data volumes from the Auto-Scaler platform.

3. Optimal Utilization: Scale the underlying storage to ensure we don’t cross 70-80% utilization. Maintaining utilization between 70% - 80% is generally the sweet spot which ensures a disk’s capacity is being optimally used while still maintaining a buffer for any additional storage requirement.

The Result

Our cutting-edge Multi-Partition support offers customers a myriad of benefits, including reduced cloud storage costs, zero downtime during peak hours, and effortless storage management.

We're excited to share that in our beta release, select customers who leveraged the multi-mount point functionality reported an impressive increase in their savings by as much as 62%. This validates the potential of our Auto-Scaler platform.

Onboarding data volumes and reaping the benefits of our Auto-Scaler platform is now as simple as clicking a button. We're eager to offer this new feature to our customers, assisting them in optimizing their cloud storage, and reducing their costs.

To discover more about our Auto-Scaler solution and how it can drive benefits for your organization, we invite you to get in touch with us today.

You might also like

Stay up-to-date on all things Lucidity

Thank you for subscribing.
Oops! Something went wrong while submitting the form.