Our Blog

In a complex cluster setup, it is practically impossible to ensure 100% availability across all IT layers. The ongoing changes inevitably result in configuration inconsistencies, introducing availability risks that often remain hidden until disaster strikes. Detecting those risks ahead of time, can prevent the next costly outage.

What are the scariest IT scenarios that can bring down your IT infrastructure? Naturally, one would think about disasters such as hurricanes, fire, or maybe cyber-attacks. But the actual threats to your critical systems may surprise you – and you can actually have control over them, given the right tools and processes.

What would the report that every IT infrastructure and business continuity manager include? Check out this sample report and learn how you can get important information such as business services at risk, replication status, configuration gaps, and IT response time in one single report.

Read the following survey and learn how your service availability metrics and disaster recovery practices compare to your industry.

Today’s Topic: Cluster Shared SAN Configuration Drift The most common way to share data between cluster nodes is through the use of multi-homed SAN storage. Inconsistent

Today’s Hidden Risk: Invalid Database Snapshot An invalid database copy can be created when a storage-based snapshot (or any other type of copy, such as replica,

Configuration drift is a data center environment term. At a high level, configuration drift happens when production or primary hardware and software infrastructure configurations “drift” or become different in some way from a recovery or secondary configuration or visa versa. Production or primary and recovery or secondary configurations are designed to be identical in certain aspects is order for business resumption should there be a disaster or major failure in production. When these infrastructure configurations drift from another, they leave a gap between them which commonly called a configuration gap.