STEP CF8: Resume workload on secondary The application workload can now be started on the secondary server. The process used to achieve this varies from organization to organization and is beyond the scope of this redbook. This is the end of the outage of the business application. 3.6.2 Switchback after CF with no data loss Given the controlled nature of the failover, the procedure for switching back to the primary server and establishing normal operations is somewhat simpler than in the case of switchback after an uncontrolled failover. The recommended switchback procedure after a successful controlled failover is shown in Figure 3-8 on page 57 and assumes the following: The primary server is up and running DB2. WebSphere MQ is up and running on both the primary and secondary servers. The primary server is not running any workload -- read-only or update. Q Capture and Q Apply are not running on either the primary or secondary servers.