Removing 3PAR Remote Copy

[Gaisu]

Hi,

We are removing 3PAR Remote Copy between two sites(Main and DR), we've disabled the copy operations by using the command:

#stoprcopy -stopgroups

Now we are looking to clear the configurations and volumes created on the DR 3PAR to free some space.

If we execute the command #stoprcopy -clear on the main 3PAR will it affect the current virual volumes created on the main 3PAR since they are still in production?

Main Site has VV1, VV2, VV3 added to copy group (must stay online)

DR Site has VV1, VV2, VV3 which are copied from main site (need to clear)

[support_s]

System recommended content:

1. HPE 3PAR Storage Systems - Support Guides | HPE 3PAR Storage - Remote Copy Link Down/Failed (RCIP)

2. HPE 3PAR Storage Systems - Support Guides | HPE 3PAR Storage - Removing Expired Temporary License Key

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[sbhat09]

Hello @Gaisu,

The command is not as destructive as you are thing about.

The command 'stoprcopy -clear' will only clear the remote copy configuration completely. It will NOT remove any volumes on either main or DR sides.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Gaisu]

HI @sbhat09 ,

Thanks for your reply.

In HPE Documents the command #stoprcopy -clear will clear any VV's created by RC, below qoute and link for reference. Does that mean it will remove the VV's copies synced to the DR system or what exactly?

"Issuing the stoprcopy -clear command removes any VV sets that were automatically created for remote copy group" refer to: https://support.hpe.com/hpesc/public/docDisplay?docId=a00045752en_us&docLocale=en_US

Thanks

[sbhat09]

Here is the complete version of the document you are referring - https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03618143

The information that you are referring is in pg no 101-102. It says that 'the command will delete all remote copy configuration data' only. Volumes on main 3PAR are not created by remote copy configuration, hence they will not be deleted.

The document continues to say 'Removes any virtual volume sets that were automatically created for Remote Copy group'. These 'virtual volume sets' refer to what is mentioned in the page no 129.

The document also confirms 'No volumes on Remote Copy targets are removed'. There is no mention about the volumes on the source 3PAR because they are not created by remote copy originally.

The command 'storcopy -clear' will remove the remote copy configuration and groups completely. The member volumes will be outside the remote copy group and become independent volumes just like any other non-replicating volumes.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Gaisu]

Hello @sbhat09 

Thanks for the great explaination.

Just one more point, if the VVs in the target are not deleted with stoprcopy -clear, whats the proper way to clear these volumes after clearing the configurations?

[sbhat09]

Hello @Gaisu,

You can remove them manually from SSMC or with the command 'removevv vv_name'.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Gaisu]

Hello @sbhat09 

We don't have SSMC, only 3PAR Management Console, the option to remove the volumes which are in copy group is not avaiable in DR site. I was thinking it might be protected since we haven't cleared the configurations yet, once cleared we might be able to remove them, is that right?

[sbhat09]

Hello @Gaisu,

As long as those DR volumes are part of remote copy, you can't delete them. Please try to delete them from the GUI or cli after 'stoprcopy -clear'.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[sbhat09]

Hello @Gaisu,

Hope you could remove the remote copy configuration successfully.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Gaisu · Accepted solution]

Hello @sbhat09 ,

Thanks for the follow up.

Here's the update:

I've engaged HPE 3PAR Team to help me with removing the configurations, they said that it won't affect running production on the lun's if we remove the RC configurations, they started by changing RC Policy to no_mirror so source and target will stop replciating configurations, then started on the DR by removing RC VV from the group and then removing the RC group. everything went fine so far, when it came to clearing the main site which is under production, the moment the VV's got removed from RC group we started facing issues with VM's stored on these VV's, the 3PAR started acting weird, some mismatch between interfaces and incorrect configuration output on CLI, production got an impact, so after looking around we figured out that those VV's were exported to hosts via the RC Group, some would say that's a rockie mistake yet 3PAR team missed out on that one, anyway we started exporting them back yet could't use the same lun ID since it was reserved via RC group, so we added them back to RC group to get everything running for that moment. 

In conclusion: you can't remove RC confgiration while the VV's are exported, you have to unexport them, delete the RC configuration then export them again.  We couldn't afford doing so in the last maintenance window and we had shared VMDKs on one of the VM's which doesn't support online vMotion, so we are going to do it later this month.

Sorry for the long story, I'd be happy to share more details if anyone is interested.

[sbhat09]

Hello @Gaisu,

Thanks for sharing the details. Hope you can complete it in the next maintenance window.

Please let me know anytime if you need further assistance.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.