Primary Server Startup Process

1. The management process starts up.

2. The status of the Secondary Server is checked.

3. If the secondary is in control, the secondary retains control until a manual recovery is performed to return control to the Primary Server. See section Recovery.

4. If the secondary is not in control, the startup of the primary continues and the primary is in control.

Note: If any of the following processes do not start, the appliance is not in control: httpd, dhcpd, named, mysqld, SSHd, TomcatAdmin and TomcatPortal. If any of these processes fail, then failover from primary to secondary is started.