In the previous post I’ve describe how migrate volumes across two (or more) EqualLogic in the same group, using different storage pools.
In the same way is also possible migrate the data on the disaster recovery site: in this case data are the remote volume replicas that are stored in a single container called delegated space.
Each destination of a (asynchronous) replication must have a proper delegated space (and only one!), and a delegated space can be stored on a single storage pool.
It will need a lot of time (depending on the used space) but can keep the replications live and working.
So the procedure is quite easy: add new members in the disaster recovery group, create a new pool, change the delegated space configuration, wait (you can monitor the procedure in the operations pane) and then remove the old array(s) and the old pool.
If you simple want to add more space to the existing group and keep your old member you can build a single pool, but remember that in this case all replicas are spanned across the members and if you loose a single member you will lost all of your replicas.
Another option could be create a new group and build a new replication partner and change all the replications to the new partner. But you will need a new full replication operation (of course), and also will break your replication schedules (because remain related to the previous partner). The advantage of using different groups is have different delegated spaces on different pools (for example slow and fast pool).