Replication Risk Detectionfor Symantec VVR

Symantec VVR

You’ve invested a great deal of time and effort in building a replicated environment using Symantec VVR. But will those replicated servers work when you need them most? In the event of a disaster, is the replicated copy of your critical business data guaranteed to be consistent and complete? Will you be able to meet with business’s RPO and RTO requirements, and ensure a smooth and flawless recovery?

Let’s face it: it is difficult to keep your Symantec VVR implementation perfectly aligned with vendor best-practices, and in sync with changes in the other IT layers that Symantec VVR interfaces with (such as OS, Storage, Networking and more). Unfortunately, even a small misconfiguration or discrepancy between production and disaster recovery systems can lead to unsuccessful recovery attempts, painful outages and even data loss.

Symantec VVR – Configuration Analysis

AvailabilityGuard automatically detects a wide range of issues and risks that pose a threat to your Symantec VVR systems and to the integrity and recoverability of your data. General VVR best-practice violations detected include:

  • Multiple RVGs on same DG (difficult management and data risk)
  • SRL is not striped (suboptimal performance)
  • SRL and data on same physical storage volumes (degraded performance)
  • Different SRL protection configuration on Primary and Secondary (insufficient data protection during fail-over or fail-back)
  • Bad replication state
  • Data volume name of source and target volumes do not match

Symantec VVR Replication Risk Detection

AvailabilityGuard identifies replication SLA violations, validating that all required data is replicated and that replication meets RPO requirements. AvailabilityGuard also checks for database replication best practices (Oracle, DB2, MS SQL Server, Sybase), including:

  • Identify partial database replication (data loss risk)
  • Alert when multiple databases are stored on the same RVG (consistency risk)
  • Alert when the files of the same database span multiple RVGs (consistency risk)
  • Different replication configuration for data and logs (consistency risk)