Forcing a Secondary Logical Drive to Change to a Primary Logical Drive
Select Yes on the Change to Primary - Error dialog to force the software to promote the selected secondary logical driveto a primary role.
Use this option when a catastrophic failure has occured to the storage subsystem that contains the primary logical drive, the primary storage subsystem cannot be contacted, and you want to promote the secondary logical drive so that hosts can access data and business operations can continue. When the remote storage subsystem has recovered and any communication problems have been resolved, there will be a Dual Primary error condition. Use Recovery Guru to recover from this error.
Consider using this option when no catastrophic failure has occured to the storage subsystem that contains the primary logical drive, but you want to perform a role reversal for some other reason and a communication problem between the local and remote sites is preventing the demotion of the primary logical drive at the remote site. When the communication problem has been resolved, there will be a Dual Primary error condition. Use Recovery Guru to recover from this error.
Important:
When the secondary logical drive becomes a primary logical drive, any hosts that are accessing the logical drive through a logical drive-to-LUN mapping will now be able to read or write to the logical drive.
To avoid the Dual Primary error condition and subsequent recovery steps when no catastrophic failure has occured to the storage subsystem containing the primary logical drive, wait until the connection between the storage subsystems is operational to perform the role reversal.