#Mirroring

Basically the title, I couldn't find anything concrete in the documentation regarding this. The documentation states 'The user-defined ^ZMIRROR routine allows you to implement your own custom, configuration-specific logic and mechanisms for specific mirroring events, such as a failover member becoming primary.' I didn't see any more details on what exactly those mirroring events are besides a failover member becoming primary, which I wasn't sure if that included a DR async becoming primary.

It appears to be working correctly, mirroring data etc. but the status on the Primary Cache DB is showing the wrong status for the DR DB.

re-configured Cache Mirroring BUt still have the same issue afterwards.

The GUI display remains the same regardless.

From primary Cache portal