Defining the Control Data Backup File with the DEFBACKUP Operator Command

When running in multiple user mode, you can change the default destination without stopping the server by issuing the DEFBACKUP operator command. The DEFBACKUP operator command will change the default destination for all subsequent control data backups while the server is running, but it will not change the POOLDEF file. The next time you start the server, the old destination that was recorded in the POOLDEF file with the FILESERV DEFBACKUP command will become the default destination again. You may want to use the DEFBACKUP operator command if, for example:

You discover the minidisk you originally planned to use for backups is not large enough.
You have specified a file mode representing an accessed directory in another file pool, but because communications to that other file pool were disrupted, that directory is not accessed anymore.

For a complete description of this operator command, see DEFBACKUP.

If you need to determine either the default destination for the control data backup file or where the last successful backup file was created, use the QUERY DEFBACKUP operator command: The format of the command is:

If backup was started automatically (because the log was over 80% full) and it did not complete, the default control data backup file destination is invalidated and you will have to specify the backup file destination explicitly on the BACKUP or STOP BACKUP operator command. Depending on what the problem is, you could either correct it and specify the same destination, or you could try to redirect the control data file (for example, from minidisk to tape). In any event, if the problem is not corrected by the time the logs become 95% full, the server will stop. If this happens, execute FILESERV BACKUP and start the server again.

If the default control data backup file destination was invalidated, you can establish a new default destination with the help of the DEFBACKUP operator command.