Yes your config you’d definitely accomplish what you want.  Just few points for your consideration.  Symantec has basically 4 recommended architectural designs Centralized, Distributed, Log replication, and High Availability.  In the HA scenario  there is really no need for a load balancer since it can be accomplished by simple DNS round robin but if you have one than why not use it. As for database HA, a clustered database would be my first choice and then replication for DR/loss of site.  Veritas cluster server is a great way to cluster the database

Here is some info on the recommendations I found.

 

 

 

 

 

 

 

 

 

Ok,  the fact that you load balancer is hosting a DNS vip is fine.  The clients don't need to know the real address of the management server.  They just need to connect to one at the address or name specified in the Management Server list specified in the policy applied.

 

So let look at replication.  In SEPM replication takes place between 2 SEPM servers not at the database.  So if at the primary location the SQL server goes down the SEPM managers using that database can not function as they really don't know about the other SQL server you were replacing to since all they know about is the other SEPM server.  This is why it is recommended for a HA environment you cluster your SQL servers.  If you are using Veritas Cluster Server for you SQL database it will handle the database failover from one SQL server to another.  And just like with the clients and the loadbalancer the SEPM does not really know the true IP of the SQL database.  It only knows about a virtual IP controlled by Veritas cluster server.  So that IP will fail the SQL database over.  If you lose the whole site SEPM and Database from say a building disaster the clients can be configured to go look for the replicated info in the DR site.

 

I hope this helps.