Citect SCADA allows for redundancy of the File Server. The [CtEdit]Backup parameter specifies a backup project path. If Citect SCADA cannot find a file in the Run directory (i.e. as specified by the [CtEdit]Run parameter), it will look in the backup path. If the file is found in the backup path, Citect SCADA will assume that the run path has become unavailable for some reason (for example, the file server has become inoperative). It will then look for relevant files in the backup before changing over. When Citect SCADA changes over to the backup path, it will call event number 11 and generate the hardware error: "File server failed, to Standby".
File Server redundancy will only operate correctly if the redirector (or shell) on the computer can respond appropriately if the File Server becomes inoperative.
Note: Only Citect SCADA switches to a backup path. Any other applications that are using files on the File Server will become inoperative when the File Server becomes inoperative. This may cause the computer to wait for long periods for the File Server (or to itself become inoperative). This includes Windows itself, so install Windows on a local drive.
To enable File Server redundancy, set the [CTEDIT]Backup parameter to a backup database path. For example, if your primary path is F:\CITECT\USER\DB, set the backup path to another File Server or a local drive, such as
( C:\ProgramData\Schneider Electric\Citect SCADA 2016\User).
You will want to verify that the project in the Backup path is the same as the one in the Run directory - each time you compile the project in the run directory copy it into the backup directory.
|
|
|
UNINTENDED EQUIPMENT OPERATION Before placing your Citect SCADA system into service, confirm that the Standby File Server has an identical copy of the current project, and that the [CTEDIT]Backup parameter is correctly set. Failure to follow these instructions can result in death, serious injury, or equipment damage. |
See Also
Published June 2018
