[Question] Asynch reporting member connecting to multiple failover members
Does anyone know any sites who configure an async reporting member to connect to two different failover mirroring sets ?
I know this is supported, but I would like to know how it is working in real world systems.
Any information would be appreciated.
Hello,
I cannot name specific customers, however this is a configuration used with TrakCare and TrakCare Lab deployments (prior to TrakCare Lab Enterprise which now integrates lab directly as a module into a single TrakCare instance), where each the TrakCare and TrakCare Lab are separate failover mirror sets and TrakCare Analytics is defined as a single Reporting Async mirror member to be the source data to build/support the TrakCare Analytics DeepSee cubes and dashboards in a single instance.
This is our standard architecture for TrakCare based deployments. I hope this helps. Please let me know if there are specific questions or concerns with this deployment model.
King regards,
Mark B-