Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for DB2 3.3 - User Guide

Enabling Archive Logging for the database

The Circular Logging method, which is the default logging behavior for any new DB2 database, only supports Full, Offline Backups. To perform Online Backups, a database must be configured for Archive Logging. With this type of logging, the log files are retained and made available for roll-forward recovery. To enable Archive Logging, you can set either the LOGRETAIN, available only with DB2 9.1 and earlier, or the LOGARCHMETH1, available only with DB2 9.5 and later, configuration parameter.

1
Start a terminal session on the DB2 Server, and navigate to the “…\SQLLIB\BIN” directory, where “…” indicates the installation path of DB2.
2
To access the DB2 command prompt, type:
DB2
3
Run the applicable command:
•
To set the LOGRETAIN configuration parameter, DB2 9.1 and earlier, to Recovery mode, type:
update db cfg for <databaseName> using logretain ON
In the Recovery mode, the active log files are retained and become online archive log files for use in roll-forward recovery. This process is called log retention logging.
•
To set the LOGARCHMETH1 configuration parameter, DB2 9.5 and later, to LOGRETAIN, type:
update db cfg for <databaseName> using logarchmeth1 LOGRETAIN
This command is equivalent to setting the LOGRETAIN configuration parameter to Recovery mode. It stores the Archived Logs in the same location as the Active Logs.
•
To set the LOGARCHMETH1 configuration parameter to DISK, type:
update db cfg for <databaseName> using logarchmeth1 DISK:<completePath>
This command lets you specify the location where the Archived Logs are stored.

Enabling the TRACKMOD parameter

The TRACKMOD configuration parameter enables tracking and recording of the database page updates. Set this parameter to YES to allow Incremental and Delta Backups. For system-managed space (SMS) and database-managed space (DMS) tablespaces, the granularity of tracking is at the tablespace level. A flag indicates whether a tablespace contains any pages that must be included in an Incremental or a Delta Backup. If there are no pages, then the backup operation can skip that tablespace.

1
Start a terminal session on the DB2 Server, and navigate to the “…\SQLLIB\BIN” directory, where “…” indicates the DB2 installation path.
2
To access the DB2 command prompt, type:
DB2
3
Type the following command:
update db cfg for <databaseName> using trackmod ON
* 
NOTE: After you enable the TRACKMOD parameter, run a Full Backup first before performing any Incremental or Delta Backups.

If you create a tablespace after enabling this parameter, perform a backup that includes the new tablespace. You can perform either a database-level or a tablespace-level backup.

Additional notes

•
To prevent users from accidentally dropping a table, you can add the Restrict on Add attribute as shown in the following examples:
create table <tableName> (<tableSpecificInformation>) in
<userSpace> with restrict on drop
– or –
alter table <tableName> add restrict on drop
•
To remove the Restrict on Add, you can use the following command:
alter table <tableName> drop restrict on drop

Backing up data

•
Available backup modes
•
Available backup types
•
Defining a backup strategy
•
Performing backups
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione