Installing GroupShield for Exchange post Neverfail Heartbeat Install.

Follow

Summary
-------
Use this document when you have already installed a Neverfail Heartbeat server pair and you wish to install GroupShield 6.1 for Exchange. Please ensure when installing and configuring the GroupShield Products you use identical locations and configurations on each server.


Important Note
--------------
Please note that there are two methodologies. The first has the benefit of being quicker; however, if the install fails then recovery can be lengthy because data must be restored from backup. The second, although longer, preserves the individual state of each server's information store so that it can mount the databases. In the event of a problem reconfigure the role of each server; active to passive, passive to active.

The reason for this is that the anti-virus tool writes changes to the Information Store instructing it that an anti-virus driver is required to start up. If the software is installed on one server and not the other then the Information Store can not mount the databases on the server without the anti-virus tool. The user is alerted to this issue at Step 6; it does not effect the ability to install but impacts the recovery time if the anti-virus tool should fail to install. It is strongly recommended that you back up your system prior to commencing the install.


Method 1
--------
Ensure GroupShield is configured in an identical way on both servers.
Ensure you have a backup of your system before starting installation.

1. Obtain a valid Neverfail license key that supports the installation of AMX’s and GroupShield.
2. Open up the Neverfail Heartbeat Management Client.
3. When the System & Registry Status are Synchronized, perform a Switchover so that the Secondary server becomes active.
4. Install GroupShield for Exchange on the Secondary server.
5. When the install has completed, providing the System & Registry Status are Synchronized, perform another switchover so that the Primary server becomes active.
6. The information store will fail to start because the Virus Scanner will not initialize. This is normal.
7. Install GroupShield for Exchange on the Primary server in the same location used on the Secondary server.
8. Ensure GroupShield configuration is identical to the Secondary server.
9. Start the Exchange System Manager and mount all Information Stores.
Note: Neverfail Monitor may have already done this for you.
10. Open up the Neverfail Heartbeat Management Client, and select to Shutdown Neverfail Heartbeat leaving the protected application running.
11. Start the Neverfail Configure Server Wizard on the Primary Server.
12. Select the License tab > change the license key to be the new key enabled for the correct AMX. Click ‘Finish’.
13. Run the AMX script for GroupShield.
14. When the script completes, start up Neverfail on both servers and allow the servers to synchronize.
15. Start / Programs / Application Module for Exchange and check that the configuration for the GroupShield services is appropriate.


Method 2
--------
Ensure GroupShield is configured in an identical way on both servers.
It is still advisable to backup your system prior to installing software.

On the Primary Server
1. Obtain a valid license key that supports the installation of AMX’s and GroupShield.
2. Open up the Neverfail Heartbeat Management Client.
3. When the System & Registry Status are Synchronized, perform a Switchover so that the Secondary server becomes active.
4. Open up the Neverfail Heartbeat Management Client, and select to Shutdown Neverfail Heartbeat leaving the protected application running.

On the Secondary Server
5. Unmount the information stores via Exchange System Manager to prevent user access; otherwise, changes made whilst this server are active will be lost.
6. Install GroupShield for Exchange on the Secondary server.
7. From a command prompt: c$> cd to neverfail\r2\bin
8. c$> ..\scripts\exchange\stop.bat
9. Allow the application to stop.
10. Start the Neverfail Configure Server Wizard on the Secondary server.
11. Change the Secondary server role to passive and exit.
12. Start Neverfail Heartbeat on the Secondary server - it should start as Passive.
13. Shutdown Neverfail Heartbeat on the Secondary, by stopping the Neverfail Service via the Windows Service Control Manager (SCM).

On the Primary Server
14. Start the Neverfail Configure Server Wizard.
15. Set the Primary server role to active and exit the wizard.
16. Start Neverfail Heartbeat and allow the application to start.
17. Open up the Neverfail Heartbeat Management Client, and select to Shutdown Neverfail Heartbeat leaving the protected application running.
18. Install GroupShield for Exchange in the same location used on the Secondary server.
19. Start the Neverfail Configure Server Wizard.
20. Select the License tab > change the license key to be the new key enabling the correct AMX. Click ‘Finish’.
21. Double click the AMX script for GroupShield, and press OK when prompted.
22. When the script completes, start up Neverfail on both servers and allow to synchronize.
23. Start / Programs / Application Module for Exchange, and check that the configuration for the GroupShield services is appropriate.

KBID-326

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.