topic Re: MSA 2062 to MSA 2052 replication error in HPE MSA Storage

MSA 2062 to MSA 2052 replication error

MadS2 — Wed, 02 Apr 2025 07:09:51 GMT

Hello!

I am using replication between a MSA 2062 Fc and a MSA 2052 Fc and I am currently deleting old replication sets (I was used to have a set per volume and quickly lost overview) and creating new replication sets with multiple volumes included.

Now the following error is stopping me... - in english it is something like "The replication data set could not be created. The maximum number of volumes that can be replicated and/or copied has been exceeded on this system."

Currently 30 volumes are in replication sets... looks like a boundary at 32.

On both systems 512 Remote-Snaps are licensed.

MSA 2062 (Firmware IN110R001)

MSA 2052 (Firmware VL270P008)

Is there a trick howto enable the replication of more than 32 volumes between the two systems? - The replication is my "life insurance" in the current situation and it feels like pain in the neck not to have all volumes backed up

Would be very happy if someone can help me out.

Best regards

Mad S

Query: MSA 2062 to MSA 2052 replication error

support_s — Thu, 27 Mar 2025 17:02:51 GMT

System recommended content:

1. HPE MSA 2050 and 2052 Storage VL100P001 Firmware Release Notes

2. HPE MSA Firmware Release Notes for MSA 1050 (VE270P005) and MSA 2050/2052 (VL270P005)

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

Thank you for being a HPE valuable community member.

Re: MSA 2062 to MSA 2052 replication error

ArunKKR — Tue, 01 Apr 2025 08:24:54 GMT

Hi,

From MSA 2060/2050 CLI guide:

The maximum number of individual volumes that can be replicated is 32.

Unfortunately this is a firmware set limit and cannot be overridden.

Re: MSA 2062 to MSA 2052 replication error

MadS2 — Tue, 01 Apr 2025 10:45:07 GMT

Hello ArunKKR!

Thanks a lot for the solution.

Maybe this essential limit would be something for the datasheets

Best regards

Mad S

Re: MSA 2062 to MSA 2052 replication error

Sunitha_Mod — Wed, 02 Apr 2025 09:29:59 GMT

Hello @MadS2,

That's Excellent!

We are glad to hear your concern has been addressed.