Unsolved
This post is more than 5 years old
4 Posts
0
2119
March 7th, 2007 15:00
Mirrorview/A Maximum LUN Size
Hi All,
We have 2 x CX700's and 1 x CX3-80, all running FC24; we are using MV/A to replicate from each 700 to the 380. However, we have hit a snag; we have one LUN on one 700 that is approximately 6.8TB. I can create the remote mirror specifying the primary image, however when I attempt to assign the secondary secondary image I receive an error ( Adding the secondary image for remote mirror MIR-WIN-VR1-FS-1. Add secondary failed, the operation failed on the secondary array. Check that the replication cache is set up on the remote array and all installed software on the remote array is working properly (0x71528071) ).
In that we have a number of mirrors already operating I believe that the cache and software are fine.
Event Log of Secondary array SP: "Failed to create remote mirror due to File: FarAdminMessaging.cpp Line: 1128 Details: Error 0x71008031 while starting protective session T_FAR_PSS_MIR-WIN-VR1-FS-1 71 52 86 51"
Event Log of Primary array SP has no corresponding entries.
This looks as though there is a maximum LUN size that can be mirrored, is this true, or is it simply that I am doing something wrong.
Sorry for such a huge question, but thought the more detail the better...
Thanks in advance,
Cliff.
We have 2 x CX700's and 1 x CX3-80, all running FC24; we are using MV/A to replicate from each 700 to the 380. However, we have hit a snag; we have one LUN on one 700 that is approximately 6.8TB. I can create the remote mirror specifying the primary image, however when I attempt to assign the secondary secondary image I receive an error ( Adding the secondary image for remote mirror MIR-WIN-VR1-FS-1. Add secondary failed, the operation failed on the secondary array. Check that the replication cache is set up on the remote array and all installed software on the remote array is working properly (0x71528071) ).
In that we have a number of mirrors already operating I believe that the cache and software are fine.
Event Log of Secondary array SP: "Failed to create remote mirror due to File: FarAdminMessaging.cpp Line: 1128 Details: Error 0x71008031 while starting protective session T_FAR_PSS_MIR-WIN-VR1-FS-1 71 52 86 51"
Event Log of Primary array SP has no corresponding entries.
This looks as though there is a maximum LUN size that can be mirrored, is this true, or is it simply that I am doing something wrong.
Sorry for such a huge question, but thought the more detail the better...
Thanks in advance,
Cliff.
No Events found!
an_hidden_KB
87 Posts
1
March 7th, 2007 23:00
EMC recommends a replication cache LUN with a minimum of 10-20% of the source LUN size for copy-on-first-write (COFW) data (including an overhead of approximately .2% of the source LUN size).
For example, if you are attempting to add a secondary image for a 1 terabyte primary image LUN, the Reserved LUN Pool should have at least a 100-200 GB unallocated LUN. Approximately 2 GB of the replication cache LUN will be used for managing COFW data.
CB1966
4 Posts
0
March 14th, 2007 18:00
It was the subtlety of needing 10-20% for the SP not the reserved LUN pool as a whole that caused the problem for me. Doubling the capacity for each SP has resolved the issue.
Thanks Again.
Cheers,
Cliff.
samwyse
1 Rookie
•
25 Posts
0
August 18th, 2008 13:00
you've configured for both arrays Reserved LUN Pool.
EMC recommends a replication cache LUN with a minimum
of 10-20% of the source LUN size for
copy-on-first-write (COFW) data (including an
overhead of approximately .2% of the source LUN
size).
For example, if you are attempting to add a secondary
image for a 1 terabyte primary image LUN, the
Reserved LUN Pool should have at least a 100-200 GB
unallocated LUN. Approximately 2 GB of the
replication cache LUN will be used for managing COFW
data.
I want to point out that the COFW data has to fit on a single LUN. In the example, the Reserved LUN Pool needs to contain at least one unallocated LUN more that approximately 2 GB in size. I once got bitten by a meta that was 1.75 TB in size, leading me to redo my entire pool using 3.5 GB devices.