Skip to content

DB2 LUW Backup Multiplexing and LIST HISTORY

06-Feb-09

Have you, as a TSM or NetBackup backup solutions user, noticed multiple entries in LIST HISTORY BACKUP for each of your successful DB2 backups, each with a different image sequence number, and wondered why? If you are using multiplexing DB2 backup software such as TSM or NetBackup, DB2 LIST HISTORY BACKUP will show a separate entry for every channel/session used by the backup. Each entry, distinguished by unique 3-digit Sequence Number (( as found in the image name format
DB_alias.Type.Inst_name.NODEnnnn.CATNnnnn.timestamp.Seq_num
[REFERENCE] )) corresponds to one channel or session. An 8-channel multiplex will therefore show 8 entries in LIST HISTORY BACKUP for every single successful backup operation.

A simple thing, but it does not seem to be well documented.

Thanks to Surbhi Gupta of Cognizant for pointing this out.

Here is an example of a typical LIST HISTORY BACKUP for a backup using 4 sessions and NetBackup with 4 channels:

List History File for mydb

Number of matching file entries = 4

Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log  Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B  D  20090206020335001   N    O  S0030352.LOG S0030352.LOG
----------------------------------------------------------------------------
Contains 10 tablespace(s):

00001 SYSCATSPACE
00002 USERSPACE1
00003 MYDB8KDATASPACE1
00004 MYDB8KINDEXSPACE1
00005 MYDB8KLOBSPACE
00006 MYDB32KDATASPACE
00007 MYDB32KINDEXSPACE
00008 MYDB32KLOBSPACE
00009 MYDB4KDATASPACE1
00010 SYSTOOLSPACE
----------------------------------------------------------------------------
Comment: DB2 BACKUP MYDB ONLINE
Start Time: 20090206020335
End Time: 20090206043818
Status: A
----------------------------------------------------------------------------
EID: 36458 Location: /usr/openv/netbackup/bin/nbdb2.so64

Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log  Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B  D  20090206020335002   N    O  S0030352.LOG S0030352.LOG
----------------------------------------------------------------------------
Contains 10 tablespace(s):

00001 SYSCATSPACE
00002 USERSPACE1
00003 MYDB8KDATASPACE1
00004 MYDB8KINDEXSPACE1
00005 MYDB8KLOBSPACE
00006 MYDB32KDATASPACE
00007 MYDB32KINDEXSPACE
00008 MYDB32KLOBSPACE
00009 MYDB4KDATASPACE1
00010 SYSTOOLSPACE
----------------------------------------------------------------------------
Comment: DB2 BACKUP MYDB ONLINE
Start Time: 20090206020335
End Time: 20090206043818
Status: A
----------------------------------------------------------------------------
EID: 36459 Location: /usr/openv/netbackup/bin/nbdb2.so64

Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log  Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B  D  20090206020335003   N    O  S0030352.LOG S0030352.LOG
----------------------------------------------------------------------------
Contains 10 tablespace(s):

00001 SYSCATSPACE
00002 USERSPACE1
00003 MYDB8KDATASPACE1
00004 MYDB8KINDEXSPACE1
00005 MYDB8KLOBSPACE
00006 MYDB32KDATASPACE
00007 MYDB32KINDEXSPACE
00008 MYDB32KLOBSPACE
00009 MYDB4KDATASPACE1
00010 SYSTOOLSPACE
----------------------------------------------------------------------------
Comment: DB2 BACKUP MYDB ONLINE
Start Time: 20090206020335
End Time: 20090206043818
Status: A
----------------------------------------------------------------------------
EID: 36460 Location: /usr/openv/netbackup/bin/nbdb2.so64

Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log  Backup ID
-- --- ------------------ ---- --- ------------ ------------ --------------
B  D  20090206020335004   N    O  S0030352.LOG S0030352.LOG
----------------------------------------------------------------------------
Contains 10 tablespace(s):

00001 SYSCATSPACE
00002 USERSPACE1
00003 MYDB8KDATASPACE1
00004 MYDB8KINDEXSPACE1
00005 MYDB8KLOBSPACE
00006 MYDB32KDATASPACE
00007 MYDB32KINDEXSPACE
00008 MYDB32KLOBSPACE
00009 MYDB4KDATASPACE1
00010 SYSTOOLSPACE
----------------------------------------------------------------------------
Comment: DB2 BACKUP MYDB ONLINE
Start Time: 20090206020335
End Time: 20090206043818
Status: A
----------------------------------------------------------------------------
EID: 36461 Location: /usr/openv/netbackup/bin/nbdb2.so64

Footnotes

Filed in DB2 Administration | Tagged , , , , , , , , , | Comments (0) »

International Relocation: In Defense of IBM and Project Match

04-Feb-09

IBM is under fire this week from many for its plan to offer laid off workers in the U.S. assistance in relocating to IBM offices in other countries. The program, named “Project Match,” specifically offers relocation help in China, India, Brazil, Mexico, the Czech Republic, Russia, South Africa, Nigeria, and the United Arab Emirates. The story broke this week Monday in Information Week, and the news has spread rapidly through other outlets such as The Raw Story.

Comments in Information Week and The Raw Story are notable for their vitriol and strong raw emotion. IBM is accused by commenters of sending U.S. workers overseas to work for pennies. Much of the invective is saved for India and seems coarsely xenophobic.

In point of fact, as I understand it, these workers have been laid off, and are free to pursue any opportunities they choose. Ex-employees of IBM are not being coerced to work overseas. They are being given an option which many of them would be wise to accept. IBM is a global corporation with offices in most countries. And the 21st century is a global century. Many young people in college today are learning Chinese and expect to live and work in that country. Having global and international skill sets in one’s resume strengthens earning potential and improves the chance of remaining employed.

I understand that many employees, particularly those in their fifties and older, may be aghast at the thought of uprooting their lives and living in another country. But this is a different world, and any opportunity is still an opportunity. An international relocation is not a life sentence – one might come back from two years in Dubai with an enviable work record and be a catch for any U.S. corporation. Many of the countries listed under Project Match are colorful, exciting and interesting places to live. The IBM worker’s salary (though less by dollar exchange rates) would still put them in the local upper classes in many of these countries, allowing them luxuries unheard of in the U.S., such as the ability to hire house staff, a cook and a driver, and many other perks. People with open minds might view this as an adventure and a big step up into a larger world.

I applaud IBM’s Project Match for opening its employees up to these unexpected, exotic opportunities. Unless U.S. citizens learn more about becoming global citizens, partly by actually living overseas, we are not going to be able to adapt to the economic challenges ahead. Those who do not adapt, perish.

Filed in IT Contracting/Consulting | Tagged , , , , , , , , | Comments (13) »