article thumbnail

Taming the Storage Sprawl: Simplify Your Life with Fan-in Replication for Snapshot Consolidation

Pure Storage

Taming the Storage Sprawl: Simplify Your Life with Fan-in Replication for Snapshot Consolidation by Pure Storage Blog As storage admins at heart, we know the struggle: Data keeps growing and applications multiply. FlashArray//C is designed to address operational workload requirements. Learn more about FlashArray.

article thumbnail

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing

Pure Storage

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing by Pure Storage Blog This blog on the storage architecture spectrum is Part 2 of a five-part series diving into the claims of new data storage platforms. And with Pure Storage’s shared-NVRAM approach, this makes controller failover events completely non-disruptive.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

SSD vs. HDD Speeds: What’s the Difference?

Pure Storage

HDD devices are slower, but they have a large storage capacity. Even with the higher speed capacity, an SSD has its disadvantages over an HDD, depending on your application. Traditionally, the biggest disadvantages of an SSD have been price, degradation, and capacity. SSD devices are faster, but they also cost more.

Benchmark 105
article thumbnail

Decrease Recovery Time for Microsoft SQL Server Disasters with Pure Cloud Block Store in Microsoft Azure

Pure Storage

The capacity listed for each model is effective capacity with a 4:1 data reduction rate. . This blog post will focus on the use of two or more Pure Cloud Block Store instances in different Microsoft Azure availability zones or regions to achieve cost-effective disaster recovery for Microsoft SQL Server instances. .

article thumbnail

Implementing Multi-Region Disaster Recovery Using Event-Driven Architecture

AWS Disaster Recovery

In this blog post, we share a reference architecture that uses a multi-Region active/passive strategy to implement a hot standby strategy for disaster recovery (DR). With the multi-Region active/passive strategy, your workloads operate in primary and secondary Regions with full capacity. Amazon RDS database.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud

AWS Disaster Recovery

This blog post shows how to architect for disaster recovery (DR) , which is the process of preparing for and recovering from a disaster. For most examples in this blog post, we use a multi-Region approach to demonstrate DR strategies. All requests are now switched to be routed there in a process called “failover.”

article thumbnail

Delivering Multicloud Agility with Software-defined Storage

Pure Storage

In the cloud, everything is thick provisioned and you pay separately for capacity and performance. You can update the software on controller 2, then failover so that it’s active. Then, you can update VM 1 with non-disruptive upgrades and within failover timeouts. You also have thin provisioning, dedupe, and compression.