Hello,

EMC Technical Support can help you to complete this via the CLI. You can contact Technical Support 'Live Chat' via Unisphere directly in the Support -> Need More Help screen or the following link: Live Chat and select VNXe from the product list.

Kind Regards

Graeme

Please also see the VNXe Community discussion: https://community.emc.com/message/616497#616497 which covers same subject and is now answered.

Thank you

Graeme

That link appears to be broken. Is there an update link to get this resolved?

Hi Steve,

I couldn’t find that thread, but here is some information on increasing the size of the replicated share.

How to increase the size of filesystem or make any changes on filesystem which is part of the replication session.

From MR4 code and above, Replication algorithm added a feature to increase the size of the filesystem which is a part of replication without breaking the replication session.

How to increase share/filesystem size which is part of the replication session. 

Till MR3(2.3) code, there was no option to make changes on filesystem/share if it has the replication configured. As per design, it is required to delete the replication session and re-create it again with full copy.

If VNXe unit is running pre-MR4 code and there is a requirement to increase the size of the share which is a part of replication, upgrade firmware version on both source and destination VNXe unit to MR4(2.4.x.xxxxx) and follow the resolution process to increase the size of the filesystem.

Till MR3 code (2.3.1.20364), it was not supported to make any changes in the filesystem which is part of replication session (Ex: Extending the share). As per design and procedure, it was required to delete the replication session and re-create it with full copy for replication data again.

If VNXe is running pre MR-4, follow the steps below, It requires deletion of the replication session, make changes to source, delete replication destination and recreate replication session again.

1.       Login to source VNXe unit and navigate to system > system replication.

2.       Select the appropriate replication session and click delete.

3.       If delete process fails, contact EMC VNXe lab for investigation.

4.       Once deletion process completes, login to the destination VNXe unit and again navigate to system > system replication and identify that associated replication session should be deleted.

5.       Once replication session is deleted, it will allow to increase the size on source filesystem.

6.       Once changes are done on source, it requires re-creation of the replication session.

7.       In order to re-create the replication session, old destination filesystem needs to be deleted with associated old destination replication session and re-create it with replication wizard again.

8.       Go through the replication wizard to configure replication session. 

9.       Once replication session is configured, it will be a full copy again.

If VNXe software version is MR4 and above, you may perform changes by following this procedure.

1.       Login to source VNXe unit and navigate to system > system replication.

2.       Select the appropriate replication session and click on details. If it is transferring the data(Syncing), it is not recommended to pause the replication session. It may create an inconsistency between source and destination filesystem.

3.       If it is not replicating the data, pause replication session and wait for the process to complete. If pause operation fails, contact EMC VNXe lab for investigation.

4.       Now navigate to storage > Shared folder storage and select appropriate CIFS share.

5.       Click on details and make changes to the shared folder capacity.

6.       Login to destination VNXe unit and go to the details of the associated replication destination filesystem.

7.       Make changes to the shared folder capacity in MBs.

8.       For example, if source was 100GB and after pausing replication session its now 150GB. On destination filesystem, you need to convert 150GB in MB (153600MB) and apply changes.

9.       Go back to source VNXe unit and try to resume the replication session.

10.   This will be an incremental copy from where it was paused.

If trying to resume process fails with allocation mismatch, recalculate size of both the source and destination. For replication session to resume, it should have source and destination filesystem with identical size.