Experience with auto_synchronize

[glanzmann]

Hello,
I'm in the process of migrating 500TB from two 10400 to two 8400. The 8400 will run 3.3.1 MU2 with all public patches applied. When setting up RCFC with transparent failover, I noticed a new policy called auto_synchronize. I wonder if someone has gained experience with it. I would like to enable it on transparent failover next to auto_recover, auto_failover and path_management. From the documenation:

The auto_synchronize policy is available with HPE 3PAR OS 3.2.2 MU2 and later.
When the auto_synchronize policy is set, the HPE 3PAR Remote Copy system
automatically recovers and synchronizes all volumes in the group after a system
failover, for either automatic or manual failover scenarios. For example, the
HPE 3PAR StoreServ Storage at a failed site automatically recovers and
synchronizes all volumes in the group after system recovery and initialization
are complete and after remote copy communication links have been
re-established. Use the setrcopygroup pol auto_synchronize <group_name>
command to set the automatic synchronization policy. In addition, this policy
also allows the failover command to be used when remote copy groups are started
and online. It is no longer necessary to stop the groups before initiating a
failover command to the secondary system.

Cheers,
Thomas

[apol]

Hi, I'd ask HPE support how this auto-synchronization will be handled. If 500TB start resyncing all at once, this will probably have interesting effects on service times.

[ailean]

Yeah I spotted that recently while planning a similar migration. We're cautious of even doing auto_recover on large arrays in case of some flapping issue kicking off out of hours. As I'd not heard people talking about the new policy I decided to ignore it for now.

I've got a mix of settings currently but will be trying to make them consistent on the new hardware, probably just auto_failover and path_management to start with.