Picture this: a customer has a PaperCut App Server in their data center; each computer has Direct Print Monitor installed; and the local water company has a date first thing Monday to drill clean through the data center link.
… That hurt to type out. Surely no link means no printing, right? Well, not with failure mode doing its thing. Find out how!
High Availability is incredibly important for maximizing uptime in any print infrastructure using Microsoft SQL Server.
But if a customer wants to go beyond mere implementation, and figure out which High Availability method is truly the best for their business, the process can be a doozy.
So let’s clear things up a bit!
99.99%.
It’s a compelling figure. The uptime guarantee trumpeted in SLAs the world over.
Of course, 100% is simply unattainable. Those SLAs must provide wiggle room for the .01% of unplanned, unavoidable, ‘well I didn’t expect THAT to happen, ‘what do you mean there’s been a power spike to the UPS’, ‘so THAT’S what that switch does’ events.
If you think going to a printer to clear a paper jam is painful, imagine having to do endless tests to trigger error statuses on printers. Pulling the tray out, waiting for an error to appear in the UI and then pushing the tray back in again. There’s got to be a better way. Luckily […]
