Micro Focus Enterprise Test Server 2.3 Update 1 > Mainframe Support for Deployed Applications > MSS Configuration and Administration > Using Fileshare with Enterprise Server > iFileshare > iFileshare Configuration > Configuring iFileshare for High Availability > High Availability Group Walkthrough > Emulate a Failover Situation

Emulate a Failover Situation

To demonstrate what would happen if the primary server were to fail, you can kill off its process, which should initiate the failover process.

On the Enterprise Server Administration home page, click Details in the Status column for the primary server.
Click ES Monitor & Control.
Click SEPs.
The SEPs information appears.
Make a note of the process ID for the ES Manager.
On Windows, do the following:
1. Press Ctrl+Shift+Esc.
  The Windows Task Manager appears.
2. If not already on display, click the Processes tab.
3. If the PID column is not displayed, right-click the Name column heading and select PID.
  The PID column appears.
4. Highlight the entry for the PID noted in the previous step, then click End Task or End Process (depending on your version of Windows).
  Note: If you cannot locate the PID, click Show processes from all users.
5. If you are prompted to confirm, click End Process again.
  This kills off the primary server and automatically assigns the role of primary to one of the standby servers.
This kills off the primary server and automatically assigns the role of primary to one of the standby servers.
On UNIX, type the following:
```
kill <process ID>
```
This kills off the primary server and automatically assigns the role of primary to one of the standby servers.
On the Enterprise Server Administration home page, click Details in the Status column of each standby server, then click ES Monitor & Control. You will notice that one of the standby servers is now displaying a status of HA VSAM Primary.
To confirm the group is still operating as expected, from the Enterprise Developer command prompt, type:
```
run runner.int
```
This reruns the previous program; if you examine the system directories for each of the remaining servers, you'll notice that the timestamp for FILE.DAT has been updated, confirming that the file is still being replicated within the group.

This concludes the walkthrough. You can now stop each server to close the group.

Note: If you plan to restart the group, ensure that you delete the logtrans.tlog file from the system directory on each server in the group before it is started.