Hi,
Thank you for posting in Symantec community.
I would be glad to answer your query.
There are two types of database i.e Embedded database and SQL database. Embedded database is built in database & SQL is third party database.
If Replication is configured between databases then SEPM will make fail-over automatically like replication between 2 SEPM's with 2 SQL database. Also, SEPM Database on SQL server with Mirroring is Supported with SEP 12.1.
But When the SEPM Database connection wizard is run, specify an IP address or machine name hosting the database. As long as that IP address is available, the SEPM will connect to it.Symantec Endpoint Protection Manager cannot natively “fail-over” between two SQL databases. Thus if you implement database mirroring, the content of the DB will be available, but you will have to re-run the wizard to reconfigure the database IP address though you may only have to stop and restart the SEPM services to get the SEPM pointed to the proper address. To overcome this you can think of virtual IP mirroring if there is any option.
An alternative method is that the customer uses an Availability Group Listener for SQL which will give a virtual network name (VNN), virtual IP (VIP), this VIP or VNN can be used to configure the SEPM database. The Availability Group Listener will ensure that it connects to the correct SQL database.
In short, SEPM can not fail-over automatically if SQL clustering/HA used new IP/hostname for SEM5 database.