Connectors working together to provide High Availability

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

Hello Rani,

As also requested by FrankBeckers, could you give us an update on this feature?

The first customer we've introduced this to asked for the High availability function....

So yeah, pretty high prio if you ask me 🙂

Many thanks

Is there any update on this feature?

Should be one of most important features because, only this way you can remove the need of having Servers at office for printing.

Otherwise you need to install it on device which always has access to printer, after that you need to think how you will handle printing in case that device or agent will fail. In case printing is critical service in your business.

Looking forward for this feature in near future.

Definitely should be prioritised if Universal Print is supposed to be used in a production environment.

Should also help with scale-out, as multiple Connectors could process multiple print jobs in parallel, allowing for higher total print throughput. Similar to how the Dynamics 365 Commerce printing solution works, with their https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/print-documents?toc=/dynamics365/commerce/toc.json#service-overview.