Detect Configuration Vulnerabilitieson NetApp Filer / Cluster

You’ve surely invested a great deal of time and money in your NetApp Filer or NetApp Cluster 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 NetApp Filer and NetApp Cluster configuration. Unfortunately, even a minor gap between storage, compute and networking can put an entire business application at risk.

NetApp Configuration Vulnerabilities

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 performs NetApp log analysis and checks for configuration issues or best-practice violations.

Here are a few examples:

  • SAN
    • Detect data access risks (e.g., dead paths, sub-optimal multi-pathing policies, potential tampering, …)
    • Cluster data access risks (e.g., standby does not see all shared disks, has reduced bandwidth, etc.)
    • Detect storage alignment issues (e.g., database files, VMware VMFS, etc.)
  • NAS
    • Risks in sharing / export configuration
    • Sharing protocol version, options (Filer and client-side)
  • ONTAP configuration issues (licenses, version, options, etc.)
  • General best practices (e.g., hot-spares, physical drives / tiering)

NetApp Replication Considerations

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

  • Detect partial replication (e.g., host mixing local FS and Filer FS for same data)
  • Detect potentially inconsistent replication / snapshots (e.g., data on multiple volumes without consistency enforced, mixed mode / version, QSM / VSM issues)
  • Detect RPO and retention violations
  • Incorrect alignment to replicated storage (e.g., database data and log on same volume)
  • Detect redundant / old replicas
We use cookies to enable website functionality, understand the performance of our site, provide social media features, and serve more relevant content to you. We may also place cookies on our and our partners’ behalf to help us deliver more targeted ads and assess the performance of these campaigns. You may review our Privacy Policy here

I agree