Unsolved
This post is more than 5 years old
1 Rookie
•
61 Posts
0
1410
May 25th, 2012 06:00
New Metavolume redundancy rule in NDU 5.1
I was running VPLEX Metro 5.0.1. I have two sites with one VMAX on each site. Each VMAX presents storage to corresponding VPLEX. Each VPLEX has metavolume. We decided to upgrade to 5.1. I ran ndu pre-check before management server upgrade and everything was OK (Green). I upgraded management to 5.1 OK, but now are getting ERROR:
[ERROR]:
Devices of active meta-volume BVPLEX_Meta01 on cluster cluster-1 are sharing the same BE array
[ERROR]:
Devices of active meta-volume RVPLEX_Meta01 on cluster cluster-2 are sharing the same BE array
Is that new requirement to have meta-volumes mirrored from different BE arrays? Can I bypass this? I tried --skip-group-be-checks, but no luck. I could potentially present meta-volumes to VPLEX in remote site, but is that right way to do this? I mean accessing meta-volume mirror via "WAN" connection even if that connection is 8Gbps Fibre?
XRay1978
1 Rookie
•
61 Posts
0
May 25th, 2012 13:00
Nice one. Yet another ndu parameter that is not documented in VPLEX Procedure generator. Very dissapointing! I had to spent/wasted 3 hours to get meta-volumes being mirrored from two arrays over "WAN". Cannot try it as I have already upgraded to 5.1.