The process for a DB-Push to occur is as follows:
A copy of the Primary server database will be pushed to the Replica through the _acesyncd process or replication engine. The Replica will then shutdown automatically and restart using the new database. You may have to wait one full replication delay cycle (default 100 seconds) for the Replica to restart. The replica cannot be manually restarted at this point. If you do not wait for the process to restart automatically, use the following solution to recover:
How to start RSA ACE/Server Replica after DBPUSH fails You should not open an administration or logmonitor process on the Replica during the DB-Push evolution. If a DB-Push is not successful, the ACE/Server authentication engine or _aceserver processes will not be able to restart on the Replica. 'Sdconnect start', or the startup of the brokers, is successful on the Replica. 'Aceserver start' results in no additional processes running on the Replica.
The Primary and Replica should be able to replicate or synchronize after a successful DB-Push. For more information, see the solution
How to tell the Primary and a Replica are synchronizing in RSA ACE/Server and RSA Authentication Manager.
