The Cold Standby feature allows for improved reliability and risk mitigation by using a standby idle backup server. This Secondary Server takes over all Indeni operations in the event the Primary Indeni Server fails.
The switchover to the Secondary Server will be done manually.
Note: The Primary and Secondary Servers must be identical and must be running the same release.
How it works:
Use imanage to identify the Active Server.
Data from the Primary Server is backed-up automatically every 12 hours (at 12 AM & 12 PM).
Data is synced from the Active Server to the Passive Server regularly.
When the Active Server becomes unavailable for any reason, the user can perform a manual switchover to the Passive Server, making it the Active Server.
Step 1: Establish the Cold Standby Cluster
From the Primary Server, run imanage. The Primary Server is now the Active Server.
Select Set Cold Standby Server.
Enter the IP address and password of the Secondary Server; this identifies the Secondary Server as the Passive Server, shuts down the Indeni processes and establishes a data sync between the Primary and Secondary Servers.
Step 2: Enable Indeni Processes on the Passive Server (Perform a manual Fail-over)
From the Secondary Server, run imanage, select Backup & Restore, then select Restore.
This action results in the Secondary Server becoming the Active Server. It will then start all Indeni Services.
Note: When the the Primary Server becomes available again, its services will NOT resume, making it the Passive Server.
Step 3: Re-building the Cluster (Configuring The Cold Standby feature once both servers are back up)
When the Primary Server becomes operational again, re-establishing the cluster becomes possible. This action effectively swaps the two servers, turning the previously Passive Server to the Active Server.
Since the Secondary acted as the Active Server last, the new cluster should be built from it.
To re-build the cluster:
From the Secondary Server, run imanage. Select Set Cold Standby Server.
Enter the IP address and password of the Secondary Server (which is now the Active Server). This identifies the Secondary Server as the Passive Server, shuts down the Indeni processes and establishes a data sync between the Primary and Secondary Servers.