Re: (Silly?) DB2 Backup question
Hi Bill, Yes you will be able to restore the database from online backup but before online db restore you must restore db logs that have been active during online backup into log_dir directory and after restore you must rollforward db to end of logs .for successful restore you need only logs than have been active during online backup if you want point in time recovery than you need all logs that you have taken after backup Main difference between online backup restore and offline backup restore is that you dont need logs during offline restore.DB2 specialist recommendet at least one offline backup per week. Bill Boyer cc: Sent by: "ADSM: Subject: Re: (Silly?) DB2 Backup question Dist Stor Manager" <[EMAIL PROTECTED] T.EDU> 20.09.2002 21:18 Please respond to "ADSM: Dist Stor Manager" There is a redbook, Backing up DB2 Using TSM SG24-6247 that has sample scripts for different full/log backup retention using the DB2ADUTL utility. I have this running using only ONLINE backups plus the DB2 user exit supplied by TSM for transaction log archiving. My biggest question has been if I only take ONLINE backups with the LOGS will I be able to restore the database, or do I need to do occassional OFFLINE backups to be able to recover? I also believe that the ONLINE backup does backup the log records that have occurred during the backup.I remember reading something about this somewhere, but I can't find it again. So I won't say I'm 100% sure about this. I do know that after an ONLINE backup the DB2ADUTL shows me with additional LOG backups, too. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Levinson, Donald A. Sent: Friday, September 20, 2002 1:40 PM To: [EMAIL PROTECTED] Subject: Re: (Silly?) DB2 Backup question Log files are absolutely required if you are performing online backups. A. the database has to be in logretain mode to allow an online backup B. all transactions that occur during an online backup only go to log and won't be captured in the backup AFAIK. Otherwise logfile archiving is only necessary if you are interested in recovering the data that was committed after the last backup, if it is acceptable to lose all the data that is entered between backups then there is no need to archive log files. The practice I use is to perform offline backups every night (my outage window allows this) and log archives whenever a log is released, the log archives have a 30 day retention. Or you could hack together a script to backup the released logs and then delete them after the next successful offline DB2 backup so that TSM marks them as deleted. -Original Message- From: Lars Bebensee [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 2:18 AM To: [EMAIL PROTECTED] Subject: (Silly?) DB2 Backup question Hi guys and girls, this question is one of the general sort, so forgive me if it has been answered here or in some manual I haven't red yet. Probably, I just need a simpler description. AFAIK, there are three ways to backup a database: 1. Offline filesystem backup 2. Offline backup in the databases quiesced mode via some api 3. Online backup via api The first question I have is about the transaction log archiving. With which of the above does it make sense and why? The second one: does it make sense to run offline AND online backups in a backup cylce, or will one of them be save enough? I read through the TSM Redbook on DB2 UDB implementation. It just explains the ways RDBMS backups can be done not which combinations are useful. As far as I could extract, it is rather useless doing offline backups and log file archiving but no online backups, right?? Thanks in advance Lars This transmittal may contain confidential information intended solely for the addressee. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, distribution or copying of this transmittal is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (collect at 907-564-1000) and ask to speak with the message sender. In addition, please immediately delete this message and all attachments. Thank you.
Re: (Silly?) DB2 Backup question
There is a redbook, Backing up DB2 Using TSM SG24-6247 that has sample scripts for different full/log backup retention using the DB2ADUTL utility. I have this running using only ONLINE backups plus the DB2 user exit supplied by TSM for transaction log archiving. My biggest question has been if I only take ONLINE backups with the LOGS will I be able to restore the database, or do I need to do occassional OFFLINE backups to be able to recover? I also believe that the ONLINE backup does backup the log records that have occurred during the backup.I remember reading something about this somewhere, but I can't find it again. So I won't say I'm 100% sure about this. I do know that after an ONLINE backup the DB2ADUTL shows me with additional LOG backups, too. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Levinson, Donald A. Sent: Friday, September 20, 2002 1:40 PM To: [EMAIL PROTECTED] Subject: Re: (Silly?) DB2 Backup question Log files are absolutely required if you are performing online backups. A. the database has to be in logretain mode to allow an online backup B. all transactions that occur during an online backup only go to log and won't be captured in the backup AFAIK. Otherwise logfile archiving is only necessary if you are interested in recovering the data that was committed after the last backup, if it is acceptable to lose all the data that is entered between backups then there is no need to archive log files. The practice I use is to perform offline backups every night (my outage window allows this) and log archives whenever a log is released, the log archives have a 30 day retention. Or you could hack together a script to backup the released logs and then delete them after the next successful offline DB2 backup so that TSM marks them as deleted. -Original Message- From: Lars Bebensee [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 2:18 AM To: [EMAIL PROTECTED] Subject: (Silly?) DB2 Backup question Hi guys and girls, this question is one of the general sort, so forgive me if it has been answered here or in some manual I haven't red yet. Probably, I just need a simpler description. AFAIK, there are three ways to backup a database: 1. Offline filesystem backup 2. Offline backup in the databases quiesced mode via some api 3. Online backup via api The first question I have is about the transaction log archiving. With which of the above does it make sense and why? The second one: does it make sense to run offline AND online backups in a backup cylce, or will one of them be save enough? I read through the TSM Redbook on DB2 UDB implementation. It just explains the ways RDBMS backups can be done not which combinations are useful. As far as I could extract, it is rather useless doing offline backups and log file archiving but no online backups, right?? Thanks in advance Lars This transmittal may contain confidential information intended solely for the addressee. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, distribution or copying of this transmittal is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (collect at 907-564-1000) and ask to speak with the message sender. In addition, please immediately delete this message and all attachments. Thank you.
Re: (Silly?) DB2 Backup question
Log files are absolutely required if you are performing online backups. A. the database has to be in logretain mode to allow an online backup B. all transactions that occur during an online backup only go to log and won't be captured in the backup AFAIK. Otherwise logfile archiving is only necessary if you are interested in recovering the data that was committed after the last backup, if it is acceptable to lose all the data that is entered between backups then there is no need to archive log files. The practice I use is to perform offline backups every night (my outage window allows this) and log archives whenever a log is released, the log archives have a 30 day retention. Or you could hack together a script to backup the released logs and then delete them after the next successful offline DB2 backup so that TSM marks them as deleted. -Original Message- From: Lars Bebensee [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 2:18 AM To: [EMAIL PROTECTED] Subject: (Silly?) DB2 Backup question Hi guys and girls, this question is one of the general sort, so forgive me if it has been answered here or in some manual I haven't red yet. Probably, I just need a simpler description. AFAIK, there are three ways to backup a database: 1. Offline filesystem backup 2. Offline backup in the databases quiesced mode via some api 3. Online backup via api The first question I have is about the transaction log archiving. With which of the above does it make sense and why? The second one: does it make sense to run offline AND online backups in a backup cylce, or will one of them be save enough? I read through the TSM Redbook on DB2 UDB implementation. It just explains the ways RDBMS backups can be done not which combinations are useful. As far as I could extract, it is rather useless doing offline backups and log file archiving but no online backups, right?? Thanks in advance Lars This transmittal may contain confidential information intended solely for the addressee. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, distribution or copying of this transmittal is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (collect at 907-564-1000) and ask to speak with the message sender. In addition, please immediately delete this message and all attachments. Thank you.
(Silly?) DB2 Backup question
Hi guys and girls, this question is one of the general sort, so forgive me if it has been answered here or in some manual I haven't red yet. Probably, I just need a simpler description. AFAIK, there are three ways to backup a database: 1. Offline filesystem backup 2. Offline backup in the databases quiesced mode via some api 3. Online backup via api The first question I have is about the transaction log archiving. With which of the above does it make sense and why? The second one: does it make sense to run offline AND online backups in a backup cylce, or will one of them be save enough? I read through the TSM Redbook on DB2 UDB implementation. It just explains the ways RDBMS backups can be done not which combinations are useful. As far as I could extract, it is rather useless doing offline backups and log file archiving but no online backups, right?? Thanks in advance Lars