Ignition redundancy does not understand master/backup database instances (and databases should never be installed on the same server as Ignition in production environments). You are expected to set up high availability database clustering outside your Ignition servers, using DB native technologies, such that both master and backup gateways can point to the DB cluster with a single URL.
Yes. And if you need a redundant DB, it has to be done internal to your DB brand. Often done with HAproxy or similar load balancers that track which real DB is "master" behind the proxy. Some solutions use floating IP addresses the move to the live "master". There are multi-master options in some environments, but Ignition isn't really equipped to handle that.