DB2 备份 以及 各个参数(国外英语资料).doc

DB2 备份 以及 各个参数(国外英语资料) DB2 backup and various parameters (1) DB2 logs are stored in file systems as files, and are divided into two modes: Circular logs and archived logs. When you create a new database, the default mode for the log is the circular log. In this mode, offline backup and recovery of databases can only be achieved. If you want to implement online backup and restore, you must set it as an archive log mode. In DB2 UDB, offline backup is the easiest backup. Offline backup requires full database backup; obviously, the database is offline during the backup process. In other words, when an offline backup is performed, the user cannot access the database. If you are using cyclic logging, offline backup is the only supported backup type. When you first create a database, this is the default logging method. For circular logging, log, retain, for, recovery, status, and user, exit, for, logging, status are set to NO. The two parameters of LOGRETAIN and USEREXIT are set to OFF. Log, retain, for, recovery, status = NO User, exit, for, logging, status = YES Log, retain, for, recovery, enabled (LOGRETAIN) = OFF User, exit, for, logging, enabled (USEREXIT) = OFF At present, in the integrated services system, the set is archived log mode, other systems (such as after the supervision, management decisions, intermediate business, etc.) are generally set as circular logging mode. As for what kind of mode, you can modify the database configuration parameter (LOGRETAIN) to achieve: archive log mode: DB2 update DB CFG for using logretain on note: on instead, view the database configuration parameter logretain value, the actual display is recovery. Once this parameter is changed, the database is again connected to the BACKUP PENDING state. At this point, you need to do an offline DB backup (DB2) to make the database status normal. Circular logging mode: DB2, update, DB, CFG, for, using, logretain, on Modify log mode Purpose: the log is modified as an archive log to continue w