Backup server

A backup server can be defined explicitly for processing HSMS statements (in HSMS V10.0 or higher with the SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE parameter). Processing takes place on the backup server regardless of whether the server is the master or slave host of the shared pubset.

Backup and version backup requests created using the “Concurrent Copy” function form an exception. Such requests are handled in the usual slave/master environment. Any backup server settings are ignored. For details, see section "Backup using the function "Concurrent Copy"".

The archive attribute BACKUP-SERVER-USAGE determines where HSMS statements which concern this archive are processed:

• When *NO is specified, the statements are in general processed on the pubset master, as was the case in HSMS < V10.0 (for details see section "Master mode" and section "Overview".

• When *STD is specified, the statements are processed in accordance with the current setting in the HSMS parameter BACKUP-SERVER:

  • When *NONE is specified, the statements are processed on the pubset master as was the case in HSMS < V10.0.
    When a backup server is used, *LOCALHOST must be entered on this server.

  • When a backup server is entered, the statements are processed on this server.

  • When *LOCALHOST or the name of the local system is entered, the statements are processed on the local server. This setting is obligatory on a system which is to be used as a backup server.

Effect of the various settings

Archive definition BACKUP-SERVER-USAGE=	Value of the BACKUP-SERVER operand on the local system:
	*NONE	<alphanum-name 1..8> <bcam-name>	*LOCALHOST
*STD	Processing without using the backup server functionality1	Processing on the backup server2 3	Processing on the local system The current system is the backup server
*NO	Processing without using the backup server functionality1

1	If the local system is master sharer of a shared pubset, the request is executed locally. If the local system is the slave sharer of a shared pubset, the request is sent to the master.
2	On the backup server a check is made to see whether BACKUP-SERVER=*LOCALHOST is set. If this is not the case, the request is rejected and message HSM0329 is output to the log file.
3	Specifying the name of the local system has the same effect as *LOCALHOST.

Regardless of the BACKUP-SERVER setting, the following requests are always executed locally:

• Requests under CCOPY

• Data transfer statements
  IMPORT-FILES
  EXPORT-FILES
  COPY-EXPORT-SAVE-FILE
  UPDATE-EXPORT-SAVE-FILE

• Node statements

• COPY-SAVE-FILE

• MOVE-SAVE-FILE

Error handling

When a statement for processing is sent to a backup server, the HSMS parameter BACKUP-SERVER is checked to determine whether this system is currently a backup system (i.e. whether *LOCALHOST or the system’s host name is entered). If the system is currently not a backup server, the request is rejected and is assigned the INTERRUPTED status with the BACK-SERV-REPLIED substatus.

In the HSMS report, the message HSM0329 also displays the cause of the error.