Need to consume messages in order with high-availability

Is there a standard design pattern I can leverage to consume messages from a queue in order, but have high availability?

I can, of course, divide the load into separate queues by account number last digit (order is only important per account) which gives me scalability, but if the host handling account numbers ending in '2' fails, for example, I need something to pick up that load.

I would think there's a standard pattern for this sort of processing. unfortunately, I can't make the messages idempotent since the queue source is due to integration from a third party.

Any thoughts are greatly appreciated.