DB2 UDB LUW, Avamar Backup and Recover, Roll-forward Question

Question

Hello all,

I will like to confirm a story I heard about how Avamar is not capable of backup and recover of DB2 LUW database if DB2 data, active logs and archive logs are placed in any other filesystem or directory paths other than the default directory, which in windows is the "C:\DB2\NODE0000\*".

To describe the scenario, because of space constraints, we deliberately want to put our DB2 active logs, archive logs in separate directory/filesystem paths.

But, as I am made to believe, Avamar will ONLY backup from default directories for current data, active and archive logs.

Can anyone with expert knowledge of Avamar technology confirm this story, please? The Avamar setup in our shop currently is not able to backup our small DB2 data because we have placed our active and archive logs in separate DISKS and directories other than the default C: drive.

How true is this...

Thanks

Okonita

ionthegeek · Answer

One of my colleagues spoke with the developers on your behalf. I have pasted their response below (with some editing for clarity and formatting):

In 6.1.101.87 the DB2 plugin supports only logretain option for archival logs. Redirecting logs to an alternate DISK is supported in 6.1.102-46. There is a limitation in this version of the plugin -- logs sent to the disk path are not backed up automatically by the plugin.

In this case logs need to be manually backed up using file system backup and the DB2 administrator can roll the database forward.

This limitation is taken care of in the upcoming release.

I hope this helps.

Avamar4589 · Answer

RMAN duplication feature is not included in the Avamar RMAN plug-in. RMAN Duplicate Feature also doesn't support Avamar as well.

Avamar

DB2 UDB LUW, Avamar Backup and Recover, Roll-forward Question

Was this post helpful?