Yes it is possible to do it, it's called 'clustering'.
Having secondary MX server(s) for email has nothing to do with clustering.
Never had to do it though. I know webmin can manage an email server cluster.
And will most likely totally destroy the DA configuration in the process.
You'll have to replicate all your mailboxes to both servers all the time (I think) so in case on goes down, the other will have the same content.
No, you don't have to do that; you set up a secondary MX configuration and the slave will hold email until the primary is available. You don't want the slave to keep mail because if it did each of your users would have to check mailboxes on both servers each time they check email, or else they'd never get all their email.
Then you can setup a second MX entry with a lower priority in your DNS record.
Not if you've got a cluster; if you have a cluster then the clustering software handles the delivery.
But yes, if you've got a seconary MX server. Which has it's own set of problems. Fpr example, your idea of duplicate mailboxes except for how users would get mail from both servers.
Let me know if you find a howto about this.
There are plenty of HowTos on the net for using exim (and just about any other MTA software as well) as a secondary MX server.
Most of us have given up on the idea though because of the issues involved in keeping track of users to accept mail for, and users to bounce.
Because if we accept email for non-users, then we're stuck with it when the primary mx comes back up. It won't accept the mail, we can't return it because we don't know if it's really from the purported sender or not, and RFCs don't let us destroy it.
The right way would be to continually update all users on the primary mx to a list the secondary mx uses to know how to accept mail for. Easier said than done.
Jeff