Ensure Data Availability & Protectionon IBM SVC / V7000

IBM SVC / V7000

You’ve surely invested a great deal of time and money in your IBM SVC / V700 environment and carefully designed and implemented redundancy, availability and data protection. But what guarantees that your storage service will always deliver the required level of availability and efficiency that you expect?

It is difficult to maintain a configuration that is always aligned with vendor best-practices, and even harder to ensure that changes in other IT layers are well aligned with your IBM SVC / V7000 storage array configuration. Unfortunately, even a minor gap between storage, compute and networking can put an entire business application at risk.

IBM SVC / V7000 Configuration Analysis

A well-designed foundation is where it all starts or ends as the slightest misconfiguration can affect hundreds of servers and cause service or data loss issues. AvailabilityGuard automatically detects SVC / V7000 storage appliances and their configuration, including:

  • Model
  • VDisk, Mdisk, MDG
  • Replication and Point in Time copies (dependencies, state, etc.)
  • Correlation with external storage arrays devices
  • Internal storage / SSD
  • Consistency groups
  • EasyTier

The above information is correlated to other configuration data obtained by scanning servers, databases, virtualization, and more. This includes:

  • Host configuration, HBA configuration, LVM and filesystem configuration, and more
  • IO multipath tools (SDD, PowerPath. HDLM, MPIO, Veritas DMP and many others)
  • Database configuration

IBM SVC / V7000 Configuration Vulnerabilities

AvailabilityGuard performs IBM SVC / V7000 log analysis and checks for configuration issues or best-practice violations. Here are a few examples:

  • Cluster data access risks (e.g., standby does not see all shared disks, has reduced bandwidth, etc.)
  • Detect data access risks (e.g., dead paths, sub-optimal multi-pathing policies, potential tampering, and more)
  • Detect storage alignment issues (e.g., database files, VMware VMFS, etc.)
  • Storage mapping risks
    • Vdisk mapping to shared cluster (visibility, # of paths, state, locking, etc.)
    • Replicas mapping to DR hosts
    • Detect SAN security breaches (e.g., Cluster Vdisks visible by non-cluster member)
  • MDG best practices
    • Mdisks of same type / array / performance characteristics (except in EasyTier configurations)
    • Offline Vdisks
    • Different extent size across MDGs
    • Vdisks requiring recovery
    • Vdisks with non-synchronized mirror
    • Space Efficient Vdisk on already thin-provisioned storage
  • Hosts directly accessing storage managed by SVC / V7000

IBM SVC / V7000 Replication Considerations

AvailabilityGuard provides deep analysis of replication and mirroring, include MetroMirror, GlobalMirror, and FlashCopy. A few key checks are listed below – see more info on appropriate solution pages.

  • Detect partial replication (MetroMirror, GlobalMirror, FlashCopy)
  • Detect potentially inconsistent replication / FlashCopy
  • Detect RPO and retention violations
  • Incorrect alignment to replicated storage (e.g., database data and log on same volume)
  • Detect redundant / old replicas