Data resilience and infrastructure design for the modern datacenter
Virtualization, storage, backup, and disaster recovery, down to the metal.
Cloud Backup Is Not Cloud Application Recovery
Rubrik can recover EC2, Azure VM, cloud database, and Kubernetes objects, but application recovery still depends on target networking, identity, keys, managed services, capacity, DNS, and external dependencies.
RubrikIdentity Has to Recover Before Most of the Datacenter Matters
During a destructive outage, identity becomes recovery infrastructure. Design Rubrik recovery so Active Directory, DNS, time, administrative access, Entra ID, and application trust are restored in the right order.
RubrikRecovery Testing Should Prove More Than the VM Boots
A successful Rubrik recovery and a running VM prove part of the recovery path. Real testing must also validate networking, DNS, authentication, application dependencies, data, and user access.
RubrikA Clean Recovery Point Is a Forensics Problem Before It Is a Restore Problem
Rubrik can narrow a ransomware recovery window with anomaly evidence, Threat Monitoring, threat hunts, and quarantine state. None of those alone proves a snapshot is clean
VeeamWhat a Cold OpenShift DR Site Actually Has to Keep Ready
A cold-site OpenShift design can keep the recovery cluster powered off, but the backup target, build assets, credentials, network, storage plan, and dependencies still have to survive the production site failure and be ready before the outage.
RubrikImmutability Does Not Mean You Are Ready to Recover
Rubrik immutability protects recovery points, but the enforcement boundary changes by workload and storage location. Recovery still needs a usable point, target infrastructure, and a tested path.
AI InfrastructureRAM Is Becoming a Data Sovereignty Problem
AI is changing who memory gets built for. As HBM and server DRAM absorb more capacity, the cost of owning enough compute for private AI becomes part of the data sovereignty decision.
RubrikReplication and Archival Solve Different Recovery Problems
For Rubrik data center workloads, replication and archival can both create secondary copies, but they use different mechanisms, retention behavior, access paths, and recovery infrastructure. Design each copy around the failure and recovery role it is meant to serve.
RubrikRubrik Security Cloud Is the Control Plane. You Still Have to Design the Backup Architecture.
Rubrik Security Cloud centralizes management, but the protection and recovery architecture still changes by workload, deployment model, network, storage, and recovery target.
VeeamThe Repository Is Not the Only Bottleneck in a Backup Architecture
Veeam backup performance is a complete data-path problem. Read Source, Proxy, Network, and Target before blaming the repository.
RubrikA Rubrik SLA Domain Is an Architecture Decision, Not a Backup Schedule
A Rubrik SLA Domain defines far more than backup cadence. Design it from the recovery points, retention, copy placement, workload behavior, and assignment model the application actually needs.
EncryptionDC Coms: Private Team Chat as Infrastructure
DC Coms started as private team chat and turned into an infrastructure project. Here is how the Community V1 design handles Matrix, encryption, service exposure, backup state, recovery, and reproducible deployment.
Subscribe
Get new articles by email.