This guide describes how to install, configure, administer, and use a Data Domain system as a backup target for Avamar.
This guide describes how to install the Avamar client for Microsoft Windows, and how to back up and restore data on a Windows server.
This guide describes how to install Avamar in a Microsoft SQL Server environment, and how to back up and restore SQL Server databases.
This guide describes how to install Avamar in an IBM DB2 environment and how to back up and restore DB2 databases.
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.
This guide describes how to install Avamar in an Oracle database environment, and how to back up and restore Oracle databases.
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.
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.
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.
This guide describes how to install Avamar in a Lotus Domino environment, and how to back up and restore data.
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.
This guide describes how to install Avamar in a Sybase environment, and how to back up and restore Sybase Adaptive Server Enterprise (ASE) databases.
|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.
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.
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
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
— 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.
I think that have some problem with the ENV.But the error is that the NWDB2’s error.
I had mike the CFG file:
DB2:/BIDW/NODE0000 nsrdb2sv -f /nsr/db2_cfg
db2 backup db BIDW online LOAD /usr/lib/libnsrdb2.o options @/nsr/db2_cfg
#If the node you are using is through a local connection, use the Instance Name.
#nsrdb2sv -f /nsr/db2_cfg -P password
and all of the client Remote Access is:*@*
and I had recover a file of filesystem(not database data),it can be redirect to another computer.
With the suspicion with the networker module for db2 2.1 build 261,so I update the module with hotfix for LGTpa91317,But the error is the same.
So,I change the networker module is 1.6 with both the client and the recoverd client.The error as following:
SQL2542N No match for a database image file was found based on the source database alias “alias_name” and timestamp “20081013182509” provided.
the restore command(networker module for db2 2.1):
db2 “restore database bidw rebuild with tablespace(SYSCATSPACE) load /usr/lib/libnsrdb2.o options @/nsr/db2_cfg taken at 20081012165644 on /db2sys_res without prompting
Has anybody solved a problem like that?