ctm_backup_bcp

The ctm_backup_bcp utility exports data from a Control-M/Server database to one of the following directories:

Windows: <controlm_owner>/ctm_server/bcp_backup

UNIX: ~<controlm_owner>/ctm_server/backup_db

Each database folder is backed up as a separate ASCII file. To run the ctm_backup_bcp utility see Running the ctm_backup_bcp utility.

NOTE: The user running the ctm_backup_bcp utility must have access permission to create the directory <controlm_owner>/ctm_server/bcp_backup or ~<controlm_owner>/ctm_server/backup_db

The time taken to backup the Control-M/Server database using the ctm_backup_bcp utility can be shortened by choosing not to backup the Control-M log information (the IOALOG table).

Differences between the ctm_backup_bcp and ctmdbbck utilities

• ctm_backup_bcp exports the data in the Control-M/Server database. The ctmdbbck utility backs up an image of the database for later restoration using ctmdbrst.
• When using ctm_backup_bcp, you cannot specify the backup directory.
• ctm_backup_bcp backs up each database folder to a separate ASCII file. ctmdbbck backs up the entire database to a single binary file.
• For all databases, except PostgreSQL, when using ctmdbbck and ctmdbrst, the restored database must be the same size as the original database. When using ctm_backup_bcp and ctm_restore_bcp, the original and restored databases do not need to be the same size.

  The ctmdbbck and ctmdbrst utilities are not relevant for Oracle databases, whether dedicated or existing.