Appendix
Installing an InterCheck Server on a cluster
Sophos Anti-Virus for OpenVMS user manual
Appendix 1 Installing an InterCheck Server on a cluster
This appendix documents ways to run an InterCheck Server on a cluster.
The rule to observe when running Sophos Anti-Virus on a cluster is that only one CPU can run an InterCheck process serving any specific communications directory (designated by the logical name
INTERCHECK_COMMS_DIR in that CPU’s system logical name table).
The InterCheck Server can be run:
On one CPU only. This is the recommended option.
On more than one CPU.
Appendix 1.1 Running the InterCheck server on one CPU only
The preferred way to run VSWEEP as the InterCheck Server in a cluster is to run it on one CPU only. To maintain the InterCheck service in the event of one node going down, a background task may be run on one or more other nodes, which periodically checks whether it can take over as the InterCheck
Server. The simplest logic for this is to look in the communications directory:
IF
((IC.STA doesn't exist) OR (IC.STA can be deleted))
THEN
@IC_START.COM
ENDIF
Note that any executive-mode system logical names used to configure the
InterCheck Server process (INTERCHECK_*) will need to exist in the system logical name table(s) of the failover CPU(s) as well as in that of the primary
CPU, so that settings are maintained through the switch from one CPU to another.
52
Sophos Anti-Virus for OpenVMS user manual
Appendix 1.2 Running the InterCheck server on more than one CPU
An InterCheck Server can run on more than one of the CPUs. Note that this approach does not allow one node to take over from another, and is therefore not recommended.
1. Create a separate, non-conflicting INTERCHECK_COMMS_DIR logical name for each CPU.
2. Create a separate Pathworks File Service for each CPU to use, with the correct subdirectories [.COMMS] and [.LISTS]. The file services might for example be called ‘INTRCHK1’, ‘INTRCHK2’, ‘INTRCHK3’, etc.
3. Decide which of your PC clients are going to be served by which of these file services, and connect appropriately, for example using
[NET]USE Q:\\vmsclusteralias\INTRCHK2
53
Sophos Anti-Virus for OpenVMS user manual
54
