FILESERV BACKUP

Read syntax diagramSkip visual syntax diagram FILESERV BACKUP 1TAPEvdevDISKfnftdirnamefm
Notes:
  • 1 The default, TAPE or DISK, is obtained from the POOLDEF file.

Authorization

Repository File Pool Server Machine

Purpose

Use the FILESERV BACKUP command to start a server in dedicated maintenance mode to back up the control data. The control data includes the contents of the POOLDEF file, the control minidisk, and the catalog storage group (storage group 1). For more information on file pool recovery facilities, see Recovery Procedures.

Operands

TAPE vdev
identifies the virtual device number vdev for a standard label (SL) tape file. The control data backup will be directed to the identified tape device.
DISK fn ft dirname
DISK fn ft fm
identifies a CMS file to which the control data backup will be directed. The file can reside on a minidisk or in another file pool. The dirname represents the fully qualified directory name of an SFS directory where the backup file is to be created. Note that filepoolid:userid.n1.n2...n8 is the only allowed form of dirname in this case. If an assignment for the control data backup file already exists in the file pool server, it is temporarily replaced. The fm represents one of the following:
  • The file mode of a minidisk accessed by the file pool server whose control data is being backed up.
  • The file mode of an SFS directory accessed by the file pool server whose control data is being backed up.

Usage Notes

  1. This command must be issued from a server machine. It is a dedicated maintenance mode command.
  2. For a list of supported virtual device numbers for tapes, see the description of the FILEDEF command in z/VM: CMS Commands and Utilities Reference.
  3. You can supply startup parameters in a file named serverid DMSPARMS, where serverid is the user ID of the server machine. FILESERV BACKUP will use the first serverid DMSPARMS file it finds in the CMS search order. For information on the startup parameters, see File Pool Server Startup Parameters.
  4. All messages are written to the server machine console.
  5. For CRR recovery servers, IBM does not recommend doing backups of control data (that is, use the NOBACKUP startup parameter).
  6. If you do not specify a FILEPOOLID startup parameter, the filepoolid defaults to the user ID of the server machine (serverid) in which the FILESERV command is running.
  7. The FILESERV BACKUP command locates the file pool minidisks by using a POOLDEF file. The POOLDEF file it uses is the first file named filepoolid POOLDEF in its search order.

    The filepoolid POOLDEF file may reside on a CMS minidisk or it can reside in another file pool.

  8. Backup data will be written to the file identified on the DDNAME=BACKUP record in the filepoolid POOLDEF file or to the file identified on the FILESERV BACKUP command itself.
  9. The BACKUP startup parameter must be in effect for FILESERV BACKUP to complete successfully.
  10. FILESERV BACKUP is not the only way a control data backup can be started. A backup will also be scheduled automatically when the file pool logs fill to 80% full, or may be scheduled by issuing the operator commands BACKUP or STOP BACKUP, or by issuing the administrator command FILEPOOL CONTROL BACKUP. The BACKUP startup parameter must be in effect for any control data backup to succeed.
  11. When the backup file resides on a minidisk, FILESERV BACKUP processing uses a temporary file during the backup. This file is named $$TEMP $BACKUP. If FILESERV BACKUP processing completes successfully, the file is erased. If FILESERV BACKUP processing fails and the backup file resides on a minidisk, see Special Considerations for Control Data Backups to CMS File for the appropriate recovery actions.
  12. You do not need to enter a FILEDEF for ddname=BACKUP. The server creates the proper environment for the backup processing.
  13. If the command fails to complete successfully, it can be rerun. If the command fails and displays error messages, correct the problem and process the command again.
  14. If the control backup is directed to tape, it is assumed the tape will be ready when the backup starts. If it is not, message DMS113S will be issued and control backup will stop.