Bringing S3-Compatible Storage On-Prem for Mission-Critical Environments

This episode focuses on addressing pain points in object storage such as log data, backup sprawl, and ransomware risks, by introducing Cloudian (+HPE) software-defined, S3-compatible storage solutions. These solutions offer cloud-native workflows on-premises, with capabilities for ransomware-resilient backups, Splunk Smart Store integrations, and AI workflow support. Cloudian provides flexible topologies including replication and erasure coding, ensures mission data security with FIPs aligned features, and supports non-disruptive upgrades. The podcast emphasizes how these solutions can meet varied data storage needs efficiently and securely.

• 00:00 Pain Points in Object Storage
• 00:59 Introducing Cloudian Hyperstore
• 01:38 Key Benefits of Cloudian
• 02:57 Mission Use Cases and Compatibility
• 04:17 Architectural Notes for Storage Practitioners
• 06:01 Conclusion and Contact Information

This episode is brought to you by ATP Gov. Visit us online at www.atpgov.com or follow us on LinkedIn.

[00:00:00] Welcome to the Bottom Line Upfront, the podcast that cuts through the noise to deliver distilled insights from today’s most important technical webinars, presentations and demonstrations designed for federal and military IT leaders. Each episode breaks down complex technologies into mission ready takeaways, so you get the key points.

Fast. Whether it’s cybersecurity, cloud, architecture, or emerging defense technologies, we highlight what matters most and how trusted integrators like a TP gov can help implement and operationalize these solutions across your agency or command. No fluff. No filler, just the bottom line upfront. There are so many pain points in object storage these days.

Ballooning log data, backup sprawl, rising ransomware risk data, serenity rules, and the need to keep sensitive data inside the mission boundary. But what if there was an S3 compatible object store is on-prem that could deliver cloud native workflows without sending data to the public cloud? [00:01:00] Enter cloud and hyper store software defined S3 native.

Scales linearly so that your apps talk S3, whether the bucket lives in AWS or behind the fence. Just to be very, very clear, Ian is a software defined S3 compatible object storage platform that is designed to run on premise. The whole function and the feature set here is that. As I mentioned, AWS S3 is the standard language for cloud native architecture and communication for storage in the cloud.

Clouding provides the same look and feel on premises as you would with AWS, so your applications or any of your teams won’t actually know the difference where the data is sitting because they’re using a standardized language. During this recent product update from HPE, we learned that Clain can actually provide benefits in three key areas, mainly because from a technology perspective, Clain speaks S3 as a standard API for communication.

Now, think of this API, as I’m speaking English, S3 has become the defacto standard for cloud native or cloud storage, mainly because [00:02:00] AWS won the market share. First, compatibility with a high Fidelity S3 API, that gives you portability for dev teams and tools. This increases cloud and security posture. It uses object lock, also known as worm for immutable backup copies, allowing you to recover cleanly after an incident.

And it also includes FIP and second line features at the software level. Encryption options include server side, customer managed keys, and multi-tenant KMS. Cloudent can operate in private cloud or on-prem clusters as the norm with hybrid tiering to public cloud. When policy allows, the smallest supported config is three nodes used for replication, and it raise your coding starts at five nodes for better capacity efficiency, and more importantly, it can run on HPE servers with consumption via GreenLake as well.

What I find is that as awesome as you know, a lot of us are, companies don’t really buy technology just because they wanna buy technology. It’s always tied to a business outcome or an agency outcome, that type of thing. So let’s talk about the mission use cases, [00:03:00] ransomware, resilient backup and archives.

Products you already know or might have in your stack. Like Veeam, Commvault, Rubrik, and Net backup can already write to Cloud and via S3. The Object lock enforce immutability for Retention Cloud and is also compatible with Splunk Smart Store whereby you can move warm and cold tears to cloud and retain hot on NVM.

Typical storage savings are in the 60 to 70% range for Splunk tiers when offloading to on-prem object storage. However, your mileage may vary by interest rate and agency retention policies. Claudia’s AI data platform or A IDP leverages NVIDIA AI Enterprise and blueprints. That means that today you can employ an enterprise chat bot over your mission docs, and next up will be video search and summarization with GPU Friendly paths.

That means S3 over RDMA and GPU Direct with a focus on throughput for training and inference. Lastly, hyper store file services supporting both NFS and SMB can bridge legacy apps [00:04:00] that aren’t already S3 Aware. From a takeaway perspective, the essence of this, basically the message is that cloud in is an S3 compatible platform.

It is scalable and it is very secure, and these three things have helped us to become very successful, both in the federal space as well as in commercial and enterprise. Here are some architectural notes we took away for storage practitioners. When deploying cloud and consider creating a model with one region, multiple data centers all addressed via 1D NS for client simplicity and failover.

You also have a few data protection choices to consider. One being replication. That’s the fastest, simplest, but the least efficient in this paradigm. Then you have a raise your coding, which provides object level parody, better efficiency, but requires a minimum of five cloudy nodes. Then we have distributed ec, which involves three sites with a less than 20 millisecond return trip time for a two of three survivability model.

You could also create a hybrid storage policy where small objects are sorted via [00:05:00] replication, large via ec, all automatically within the same bucket for mixed workloads. Think Veeam payloads versus metadata storage clouding is able to do this at the storage or the bucket level. So you can basically have different data distribution schemes.

So whether you’re replicating between one site, two sites, if you’re having replica factor ratio coding, and all those details, all that’s handled at the bucket or the storage policy level. So if you have a multi-tenant environment, you can have different enclaves or different mission partners have configured for different configurations for data protection to best suits, what their needs are.

Also note that heterogeneous nodes are supported with cloud in thereby allowing non-disruptive hardware refreshes by adding new nodes while retiring old ones. One of the things that we’re able to do is a non-disruptive, both upgrade from a software perspective, but also a refresh perspective. So when that equipment gets to end of life, we can simply add new nodes into the system and decommission the old nodes out of the system while the system continues to provide [00:06:00] data services.

So what’s the bottom line upfront? If your mission needs on-Prem S3, compatible, scalable, and software validated, secure storage cloud and hyper store on HBE hardware delivers a familiar AWS style experience behind the firewall, supporting ransomware resilience through object lock, Splunk Smart store for cost savings, backup and archive tiers, container persistence and AI workflows via cloud’s, AI data platform.

Cloud and only needs a minimum of three node clusters to operate. It provides flexible topologies like replication and era coating, multi-tenancy, and its FIPs aligned features make it fit for DOD, IC and civilian requirements. So let’s keep mission data inside the enclave with on-prem S3 compatible storage using cloud and.

Be sure to reach out to ATP cov today@www.atpgov.com, or email info@atpgov.com, or check us out on social media on LinkedIn. Thanks for listening, and be sure to subscribe to the bottom line upfront wherever you get your [00:07:00] podcasts. And stay tuned for more distilled insights from the front lines of tech and national security.

So until next time, stay secure. Stay mission ready.

The Bottom Line Up Front, is ATP Gov’s podcast that cuts through the noise to deliver distilled insights from today’s most important technical webinars, presentations and demonstrations designed for federal and military IT leaders. Each episode breaks down complex technologies into mission ready takeaways, so you get the key points.

Fast.

Whether it’s cybersecurity, cloud, architecture, or emerging defense technologies, we highlight what matters most and how trusted integrators like ATP Gov can help implement and operationalize these solutions across your agency or command.

No fluff. No filler, just the bottom line up front.