Hi,
We're in DB2 9.7 fp6 and currently using TSM 6.1 for backups and log archiving (on AIX 6.1)
We have a 4,5TB database and we only use online backups.
I have a question regarding log archiving / retrieving performance with TSM.
When I check the db2diag.log, log archiving is done in 4 seconds max usually (log file - 10240 pages - 40 Mb)
2013-01-16-22.47.59.260500+060 E480740A376 LEVEL: Info
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
DATA #1 : <preformatted>
Started archive for log file S0005963.LOG.
2013-01-16-22.48.01.089827+060 E481117A438 LEVEL: Info
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
DATA #1 : <preformatted>
Completed archive for log file S0005963.LOG to TSM chain 1 from /var/db/db2/p1epro/E_PRO/redo/NODE0000/.
But when my online backup open the last TSM session to retrieve logs (include logs in backup) The time to retrieve the archive logs can get up to 1 minute and 30 seconds for each file.
2013-01-16-22.49.39.705625+060 I482357A366 LEVEL: Warning
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0005960.LOG.
2013-01-16-22.51.05.758610+060 I482724A433 LEVEL: Warning
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0005960.LOG on chain 1 to
/var/db/db2/p1epro/E_PRO/redo/NODE0000/.
I'm no TSM expert unfortunately but I'm still looking arround.
Could this retrieve time be tunned ? (DB2 or TSM side ?)
Is there anything I should ask the TSM guy to check ?
a DBA DB2 friend showed me that, with his similar setup, the retrieve was as long as the archive (meaning 5 seconds each)
Thanks for your help.
Best regards,
JFU.
We're in DB2 9.7 fp6 and currently using TSM 6.1 for backups and log archiving (on AIX 6.1)
We have a 4,5TB database and we only use online backups.
I have a question regarding log archiving / retrieving performance with TSM.
When I check the db2diag.log, log archiving is done in 4 seconds max usually (log file - 10240 pages - 40 Mb)
2013-01-16-22.47.59.260500+060 E480740A376 LEVEL: Info
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
DATA #1 : <preformatted>
Started archive for log file S0005963.LOG.
2013-01-16-22.48.01.089827+060 E481117A438 LEVEL: Info
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
DATA #1 : <preformatted>
Completed archive for log file S0005963.LOG to TSM chain 1 from /var/db/db2/p1epro/E_PRO/redo/NODE0000/.
But when my online backup open the last TSM session to retrieve logs (include logs in backup) The time to retrieve the archive logs can get up to 1 minute and 30 seconds for each file.
2013-01-16-22.49.39.705625+060 I482357A366 LEVEL: Warning
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0005960.LOG.
2013-01-16-22.51.05.758610+060 I482724A433 LEVEL: Warning
PID : 35651656 TID : 3600 PROC : db2sysc 0
INSTANCE: p1epro NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (E_PRO) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0005960.LOG on chain 1 to
/var/db/db2/p1epro/E_PRO/redo/NODE0000/.
I'm no TSM expert unfortunately but I'm still looking arround.
Could this retrieve time be tunned ? (DB2 or TSM side ?)
Is there anything I should ask the TSM guy to check ?
a DBA DB2 friend showed me that, with his similar setup, the retrieve was as long as the archive (meaning 5 seconds each)
Thanks for your help.
Best regards,
JFU.