Shulou(Shulou.com)06/01 Report--

Xiaobian to share with you DB2 online incremental backup failure example analysis, I believe most people do not know how to share this article for your reference, I hope you read this article after a great harvest, let us go to understand it!

The company has a DB2 server online incremental backup failure, using the backup software NETBACKUP 7.5. The specific error is as follows:

nbu reported error number 4, and on Symantec's website, error number 4 is described as

The solution given is to verify permissions and whether files can be deleted. If you try to solve the problem in this way, you will be confused. Because even if you set permissions to 777, you will still report this error.

For a change of thought, look at DB2's db2diag.log log. There was a description in the log:

2013-06-19-15.22.29.980017-360 E437909183A905 LEVEL: Severe

PID : 798772 TID : 1 PROC : db2agent (idle) 0

INSTANCE: db2inst2 NODE : 000 DB : PORTALDB

APPHDL : 0-490 APPID: *LOCAL.db2inst2.130619212231

AUTHID : DB2INST2

FUNCTION: DB2 UDB, database utilities, sqlubInitCheck, probe:310

MESSAGE : SQL2426N The database has not been configured to allow the

incremental backup operation. Reason code = "".

This message tells us that the database is not configured to allow incremental backups and needs to be enabled in DB2. In ORACLE, incremental and differential backups can be conveniently implemented through RMAN.

Next we check the TRACKMOD parameter

$ db2 get db cfg for portaldb|grep -i trackmod

Track modified pages (TRACKMOD) = OFF

This parameter was found to be OFF, which is clearly the primary cause of DB2 incremental backup failures.

Because an incremental backup of db2 requires tracemod to be set to on, the database will record the changed partial page on the physical page, marked dirty. Turning on incremental backups means that you don't need to back up a very large database at a time. It also means that you can restore the database to the state it was in before the crash, rather than the state it was in when you last backed it up, minimizing data loss as much as possible.

There are three parameters to be aware of when setting up incremental backups correctly:

db2 update db cfg using logretain on(or recovery); enable archive logging

db2 update db cfg using trackmod on; Enable incremental backups

db2 update db cfg using userexit on; Enable user exit

Effects of changes:

$ db2 update db cfg using trackmod on

DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

SQL1363W One or more of the parameters submitted for immediate modification

were not changed dynamically. For these configuration parameters, all

applications must disconnect from this database before the changes become

effective.

That is, for these configuration parameters, the changes will not take effect until all applications are disconnected from this database (db2 force applications all). In addition, after changing the parameters, the database is in backup pending state. Before performing incremental and online backup, you must perform offline full backup once to make the state normal.

Supplement: How to make online backup, incremental backup and differential backup?

db2 backup db testdb online to backup path (full online backup) include logs

db2 backup db testdb online incremental to backup path

db2 backup db testdb online incremental delta to backup path

How do I recover from backup files?

1. Check the integrity of backup files and verify availability

db2ckbkp -h /db2logs/PORTALDB.0.db2inst2.NODE0000.CATN0000.20130619001007.001

2. Executing the db2ckrst command returns the recommended required recovery action commands.

db2ckrst -d portaldb -r database -t 20130619001007

3. Execute the sequence of commands given in the previous command

db2 restore db portaldb incremental from /backup taken at 20130619001007 buffer 100

The database will be restored to the backup point, after which log roll forward should be performed (at this point the database is in roll forward pending state and will not be available)

db2 rollforward db portaldb to end of logs and complete

Of course, if you don't think you need to roll forward (you'll lose your changes since the last backup), you can

db2 rollforward db portaldb stop

When you understand this knowledge, you will be able to perform backup recovery correctly and orderly, and solve problems quickly and efficiently.

The above is "DB2 online incremental backup failure sample analysis" all the content of this article, thank you for reading! I believe that everyone has a certain understanding, hope to share the content to help everyone, if you still want to learn more knowledge, welcome to pay attention to the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.