Introduction of IBM DB2 Archive logging leveraged by Avamar DB2 plugin

Article Number: 504655 Article Version: 3 Article Type: How To



Avamar Plug-in for IBM DB2 7.4.101-58,Avamar Plug-in for IBM DB2 7.3.101-125,Avamar Plug-in for IBM DB2 7.5.100-183

The intention of this article is introducing DB2 Archiving logging function, which will be leveraged by Avamar DB2 backup.

Archive logging is used specifically for rollforward recovery. Archived logs are log files that are copied from the active log path to another location. You can use one or both of the logarchmeth1 or logarchmeth2 database configuration parameters to allow you or the database manager to manage the log archiving process.

Active and archived database logs in rollforward recovery. There can be more than one active log in the case of a long-running transaction.

User-added image

Taking online backups is only supported if the database is configured for archive logging. During an online backup operation, all activities against the database are logged. When Avamar online backup is restored, the logs must be rolled forward at least to the point in time at which the backup operation completed. For this to happen, the logs must be archived and made available when the database is restored. After Avamar online backup is complete, the database manager forces the currently active log to be closed, and as a result, it will be archived. This ensures that Avamar online backup has a complete set of archived logs available for recovery.

The logarchmeth1 and logarchmeth2 database configuration parameters allow you to change where archived logs are stored. The logarchmeth2 parameter enables you to archive log files to a second separate location. The newlogpath parameter affects where active logs are stored.

Unless you specify that you want to manage the active logs (by using the LOGRETAIN value), the database manager removes log files from the active log path after these files are archived and they are no longer needed for crash recovery. If you enable infinite logging, additional space is required for more active log files, so the database server renames the log files after it archives them. The database manager retains up to 8 extra log files in the active log path for renaming purposes.

Related:

Re: Time to Time DB2 Backup Faliure

Hi,

We have Networker 9.1 that deployed on a Win 2012 R2. We are schedule a DB2 full backup on every day 3 am. Past few months we are facing the backup failure in time to time. In the every time when the backup failed we got the below error.

Backing up the ‘PB_PROD’ database.

Unable to backup PB_PROD database due to backup request failure, SQLCODE : -2025, SQL2025N An I/O error occurred. Error code: “3”. Media on which this error

occurred: “VENDOR”.

NMDA backup failed.

64673:nsrdasv: Unable to backup PB_PROD database due to backup request failure, SQLCODE : -2025, SQL2025N An I/O error occurred. Error code: “3”. Media on which this error

occurred: “VENDOR”.

— Job Indications —

prdbsvr1:DB2:/PB_PROD/NODE0000: retried 1 times.”



But after we restart the NW services from next day onwards backup was run as normal. DB backup size is ~1.5 TB. We have open several SR‘s with DELL EMC NW support team. As per them in the very first time they advised to restart the NW services. As I previously said after restarting the services it was runnin fine. In the second time when we open the SR they asked to created a separate ddboost device to backup the data. That thing also we already did. Now we yesterday backup was again failed with the same error.



Is anyone can advised how to solve this issue permanently.

Related:

Prevention policy for DB2

I need a solution

I see under the AIX prevention the only DB prevention policy for MySQl.  Is there a best practice or template  for DB2? We are trying to set up prevention for an AIX 7.2 server running IBM DB2. We have a policy in place for the  OS – but want one geared toward the Data Base.

0

Related:

Netwoker Client Direct Backup not Working

Hi,

We have the NW 9.1 deployed on a VM. OS is Win 2012 R2. We are expecting backup slowness on our DB client. It contains ~1.4 TB data. We are use the client direct for backup the data to DD. To investigate this issue we have rendered the daemon.raw file in the NW server and go through it. Then we are able to identified client direct backup it not happening. Pls refer the below log output.

70896 9/19/2018 4:00:50 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 4:00:50 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘3600907418’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

71659 9/19/2018 7:44:12 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 done saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001) 1358 GB

70896 9/19/2018 7:44:15 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 7:44:15 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘2124525815’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

Then we have check the connectivity between the client and DD vice versa. Connectivity is fine. And we are use the dedicated VLAN for the backup purpose. That means all the backup clients and DD are in the same range.

How can we solve this issue. Pls advised.

Related:

Avamar 18.1



Avamar 18.1 and Data Domain System Integration Guide

This guide describes how to install, configure, administer, and use a Data Domain system as a backup target for Avamar.



Avamar 18.1 for Windows Servers User Guide

This guide describes how to install the Avamar client for Microsoft Windows, and how to back up and restore data on a Windows server.



Avamar 18.1 for SQL Server User Guide

This guide describes how to install Avamar in a Microsoft SQL Server environment, and how to back up and restore SQL Server databases.



Avamar 18.1 for IBM DB2 User Guide

This guide describes how to install Avamar in an IBM DB2 environment and how to back up and restore DB2 databases.

Avamar 18.1 for SAP with Oracle User Guide

This guide describes how to install Avamar in an SAP environment with Oracle, and how to back up and restore SAP servers with Oracle databases.



Avamar 18.1 for Oracle User Guide

This guide describes how to install Avamar in an Oracle database environment, and how to back up and restore Oracle databases.

Avamar 18.1 for NDMP Accelerator for Oracle ZFS User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for Oracle ZFS , and how to back up and restore data on Oracle ZFS.



Avamar 18.1 for NDMP Accelerator for EMC NAS Systems User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for EMC NAS systems, and how to back up and restore data on supported EMC VNX and EMC storage systems.



Avamar 18.1 for NDMP Accelerator for NetApp Filers User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for NetApp Filers, and how to back up and restore data on supported NetApp filers.



Avamar 18.1 for Lotus Domino User Guide

This guide describes how to install Avamar in a Lotus Domino environment, and how to back up and restore data.

Avamar 18.1 for SharePoint VSS User Guide

This guide describes how to install Avamar in a SharePoint environment, and how to back up and restore data using Avamar with Microsoft Volume Shadow Copy Service (VSS) technology.



Avamar 18.1 for Sybase ASE User Guide

This guide describes how to install Avamar in a Sybase environment, and how to back up and restore Sybase Adaptive Server Enterprise (ASE) databases.

Related:

7022986: DB2 sqlcode -2044 error – backups fail

This document (7022986) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)

SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)

Situation

After updating to kernel version 3.0.101-108.38.1 or version 3.0.101-108.41.1 storage backups were starting to fail. The DB2 errors pointed to ipc (interprocess communication) related errors.

The DB2 log (db2idag log) is showing an error like this:
FUNCTION: DB2 UDB, database utilities, sqluBufInUse, probe:1453

MESSAGE : SQL2044N An error occurred while accessing a message queue."

Resolution

The SLES11 SP4 kernel update: 3.0.101-108.52.1 and SLES11 SP3 LTSS kernel update: 3.0.101-0.47.106.32.1, both released May/31 include the patch to resolve the problem.

Cause

Cause is a faulty parsing of msgctl args in a fix of an ipc data structure inconsistency.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: