$ MUPIP BACKUP * [GTM.BKUP]
          
         

Assuming that [GTM.BKUP] exists and that the current Global Directory, as specified by the environment variable $GTMGBLDIR, has regions that map database files to [GTM.PROD]TBLS.DAT and [GTM.PROD]UBG.DAT, this command creates ready-to-run database backup files [GTM.BKUP]TBLS.DAT and [GTM.BKUP]UBG.DAT.

Example:

            
         $ MUPIP BACKUP /BYTESTREAM ACN,HIST [.BKUP]
         
         

This command creates bytestream backup files [.BKUP]ACN.DAT and [.BKUP]HIST.DAT, assuming that [.BKUP] is an existing subdirectory and that the current Global Directory has regions ACN and HIST that map to files ACN.DAT and HIST.DAT.

Example:

         $ MUPIP BACKUP * [.backup]
         

Example:

         $ INIT MSA0: FULL
         $ MOUNT /INIT=CONT BLOCK=2060 MSA0: FULL
         $ MUPIP BACK /BYTE /TRAN=1 MAIN_REG FULL:MAIN
         

In this example, the first command initializes a magnetic tape with the label FULL. The second command mounts the tape with OpenVMS automatic volume initialization and a block size of 2060. The magnetic tape block size of 2060 handles a database block of 2048 bytes. The MUPIP command backs up the dynamic segment associated with MAIN_REG to the tape. Because of the /TRANSACTION=1, BACKUP copies all blocks in use to the tape.

Example:

         $ MUPIP BACKUP MAIN*,%XREF USR$BCK:[TUESDAY]
         

This comprehensively backs up all regions that have a name starting with "MAIN," and all regions that have names starting with any single character and ending with "XREF" to the directory USR$BCK:[TUESDAY].

Example:

         $ MUPIP BACKUP /INCREMENTAL *[19990505]
         

This backs up all changes made since the last BACKUP /DATABASE for all regions of the database defined by the current Global Directory into the RMS directory [19990505]. BACKUP creates files in the directory, with names corresponding to each dynamic segment's file name.

	Note
	GT.M allows multiple regions to have the same database file name. This occurs because different regions can have the same file names as long as they reside in different directories. However, Fidelity does not recommend this practice. If this happens, you should specify explicit file names for each region, and do not use the command in the above example.