FOS and DR

FOS and DR -Steps to Troubleshoot

Failover Service and Disaster Recovery:


I have added the below steps to analyze the issue related to FOS and DR.

Primary Checks: FOS as an add-on license is required

Failover service : 1. Please check if the customer has 3 servers, 1. Primary 2.Secondary 3.Database
                               2. Check if all the servers are on the same region and the common IP Address in the same network as primary and secondary servers.
                               3. Servers used for the FOS setup must have two-way read-write access for the ManageEngine folder (where ServiceDesk Plus is installed).
                               4. Check if the valid NIC card details are being used:We can get them by opening the command prompt as admin and then invoke the iflist.exe by navigating to C:\Program Files\ManageEngine\ServiceDesk\tools\fos\bin and invoke iflist.exe and check for the adapter status as UP and make use of the adapter name.
 



                              5.Check on the Secondary sever if all the files are mirrored. We can modify the files you would like to modify on the haconfig file.

Important Note: Please note that only two tables related to FOS are populated on your secondary server which is readily available. Once the primary goes down the secondary will load the other tables and start the application. We can check them on the Wrapper log to validate if the configurations are being right


Disaster Recovery: 1. Primary server 2. Secondary Server. 3.SQL with AOAG enabled
                                  2.Validate if all of them are using different IP address for DR which is the primarry check
                                 3.File attachments should be externalised.It should be a network path and should be accessible from both the servers.

Database queries related to FOS and DR:

                               1.select * from FOSNodeDetails;
                               2.select * from HAConfig; 
                               3.we can use the following update query to disable FOS: update haconfig set paramvalue='Disabled' where category='HAMODE'

To disable FOS from the application,

Uncheck the Enable FOS Startup Mode option under ESM Directory > General Settings > FOS Configuration.
Invoke \bin\shutdown.bat in both the primary and secondary servers. This will stop ServiceDesk Plus.
You can then restart the application in the servers individually by invoking \bin\run.bat command. On restarting, the servers will behave individually as two separate machines.
Alternatively, you can also start ServiceDesk Plus as a service on each server.

Important Note: We can analyze the logs if everything is checked as mentioned above for the root cause





    • Related Articles

    • Unable to restore data after changing DBserver to SQL

      After changing the DB server to MSSQL, We tried to restore the data from the backup file, but the restore didn't take place successfully so we followed those steps and everything worked perfectly. Please follow the below steps and re-initiate the ...

    • Performance is slow

      Try access ServiceDesk using the IP address of the Server not using the Alias URL and if the page loads up considerably fast. follow those steps: 1- Go to this path C:\ManageEngine\ServiceDesk\conf and open server.xml file. 2- change the ...

    • Database Warning : Your database transaction log file size has crossed the threshold

      You are getting this email as a result of an enhancement that was made in the 11 version to notify administrators if the SQL Log File Size crossed the threshold. In Service Desk Plus, under Performance Settings in Admin/ESM Directory you have the ...

    • Change Postgres Password

      Problem :- Need to change the default password for postgres. Solution :- 1- connect to the database. 2- execute the below steps. servicedesk=# \password Enter new password : Enter it again : 3- Once execute it, do the below. - Open ...

    • Delete Large System error logs records

      Problem: for large Log files (over 1 million records)  When we select the  "delete all" button in the system log viewer in the support tab the system Crashed !  So How can  we delete these large  log files?  Solution: we can delete them from database ...