Connectors working together to provide High Availability. Now one connector is associated to one printer. If connector is down, printing is not possible. Just like similar solution as we have with m...
Hi Rani_Abdellatif,
How is this going?
I'm thinking that we'd have the following configuration at a branch
1. Server connector / Desktop connector / UP Appliance (e.g. ezeep) that caters for connector print jobs
2. Server connector in Azure as a Backup for the connector machine if there is a failure.
Printer routing fails over between Primary (Site Connector) to Secondary (Azure / Data Centre Connector)
Could this be catered for?
If design correctly we could have many connectors in a pool with failover / load sharing capabilities.
Primary = One / Many at Branch - Secondary = One / Many at Azure / DC
Hopefully this is the kind of architecture you will have been thinking about.
Thanks