Unsolved
This post is more than 5 years old
21 Posts
0
14008
September 11th, 2014 15:00
replication reserve question
I configured a volume collection for replication. Everything seems to be fine except that the local replication reserve space didn't get removed after the replication (failback snapshot is not enabled for any of those replicated volumes). I am still seeing 500G of replication reserve being reported under the group disk space usage. Why is that?
I realize that replication occurs simultaneously for volumes within volume collection. Does that mean the potential max. pool space required during the volume collection replication will be the sum of all the local replication reserve assigned to each volume?
Thanks for any feedback.
No Events found!
Joe S586
9 Technologist
•
729 Posts
0
September 12th, 2014 07:00
Regardless if you use a failback snapshot or not, the reserve is still allocated, and will not be returned to the pool after replication.
The size displayed is the size of the total reserve space you specified. Sizing the reserve if not using a failback snapshot it's recommended to specify 100% of the volume(s) size.
-joe
ngkeith
21 Posts
0
September 12th, 2014 08:00
Does that mean I cannot use those space even though it is not being used by the replication at the moment?
Joe S586
9 Technologist
•
729 Posts
0
September 12th, 2014 12:00
Correct, the space is allocated for replication, and local reserve borrowing (if you enabled it).
If space used is an issue, you can try using the "space efficient value" for example: The 100% reserved can be lowered if you can calculate the average amount of volume change that occurs during a typical replication operation. Then use the formula: rate of change PLUS 5%-10% and this can be your local replication reserve value.
The online help in the GUI has greater detail for calculating this value, and what happens if the value is too low.
-joe