A customer has enabled MirrorView/A on their VNX arrays. Even before MirrorView/A is actively transferring data, a performance impact is noticed. What is causing this?

Question

Options

• AMirrorView/A is updating the Reserved LUN area to track data changes.
• BMirrorView/A software uses additional memory in the VNX storage processors, causing less
• CMirrorView/A cannot be combined with RecoverPoint in the same array.
• DMirrorView/A is using SAN Copy as underlying technique, causing the overhead.

• A
  71% (34)
• B
  17% (8)
• C
  8% (4)
• D
  4% (2)

No community discussion yet for this question.