Initiating Maintenance Failovers
Maintenance failovers can be used to temporarily halt all activities except restores in the CommCell. Use this option to perform maintenance related activities without completely shutting down the CommServe server. For example, to install service packs on the production CommServe host.
Before You Begin
- Make sure that the SQL Client from both the production and standby CommServe hosts can communicate with the CommServe and with each other.
Tip: Open the Process Manager associated with the SQL Server client. From the Failover Assistant tab, under Node Information, make sure that both the Production Node and Passive Node(s) have the green light.
- All the clients in the CommCell must be able to reach the standby CommServe host after the failover, either through a proxy or any other method used to communicate with the standby CommServe host.
- Log on to either the production CommServe host computer, or the standby CommServe host computer.
- Click Start and point to All Programs.
- Click Commvault > Process Manager.
Note: Open the Process Manager associated with the SQL client.
- On the Failover Assistant tab, select the following options:
- From the Failover To list, click the name of the passive node that must be used for performing the failover.
- From the Failover Type list, click Production Maintenance.
- Click Initiate Failover.
- On the Confirm prompt, type confirm and click Ok.
Important: After the maintenance failover, only restore operations are allowed .
All other activities, including installation, should not be performed.
- The failover is initiated and the sequence of tasks performed during the process is displayed in the Process Manager window.
- If a floating CommServe name is not used, make sure to open the CommCell Console and Command Center from the new active CommServe host, after a successful failover. (Type or choose the name of the active CommServe host in the CommCell list displayed in the Connect to CommCell dialog box.)
Recommendation: To ensure that the Commcell Console and Command Center points to the correct CommServe, use a floating name. Even if the CommServe is not installed with a floating name, you can create a virtual DNS record and point to the IP address associated with the active CommServe. For other alternatives, see Third-Party Port Mappings (TPPM or Network Proxy).
- If you have failed over to a CommServe host located in a Cloud, or behind a firewall where port 8401 (GxEvMgrS port) is not reachable, make sure to enable the Connect through firewall option, click the Configure button, and then specify the proxy computer details in the Proxy hostname or IP address and Proxy port number boxes. Ideally this proxy computer must be a standalone computer which is accessible to both the CommServe host and the clients.
- You will notice the following in the CommCell Console:
- All activities, except restores, are disabled.
- All the jobs will appear as Suspended in the Job Controller. (However, you can start and perform restore operations from this CommServe host.)
Last modified: 9/12/2019 7:24:54 PM