Bug 1098654

Summary:	db2bak.pl error with changelogdb
Product:	Red Hat Enterprise Linux 7	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	7.1	CC:	nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.3.1-1.el7	Doc Type:	Bug Fix
Doc Text:	Cause: When a replication is configured, a replication change log db is also a target of the backup (db2bak and db2bak.pl). Backing up a change log db failed since there was no backend instance associated with a replication change log db. Consequence: Backing up on a server failed if the server hasd a replication change log db. Fix: If a backing up db is a change log db, it skips checking the backend instance is associated with the db or not. Result: Backing up works on a server which has a replication change log db.	Story Points:	---
Clone Of:	1098653	Environment:
Last Closed:	2015-03-05 09:34:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1098653
Bug Blocks:

Description Noriko Hosoi 2014-05-16 20:17:16 UTC

+++ This bug was initially created as a clone of Bug #1098653 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47804

We are backing up our database daily with db2bak.pl, and have started to notice the following messages:

[13/May/2014:03:59:08 -0600] - Backend instance "changelogdb" does not exist; Instance path /var/lib/dirsrv/slapd-cora/changelogdb could be invalid.
[13/May/2014:03:59:08 -0600] - Backup: error in copying directory (/var/lib/dirsrv/slapd-cora/changelogdb -> /var/lib/dirsrv/slapd-cora/bak/cora-2014_05_13_03_59_08/.repl_changelog_backup): err=-1

# ls -l /var/lib/dirsrv/slapd-cora/changelogdb
total 2796
-rw-------. 1 dirsrv dirsrv 2859008 May 14 13:22 dab99282-1dd111b2-84f8fd5b-e7890000_4e7cb85b000000010000.db4
-rw-rw-r--. 1 dirsrv dirsrv       0 May 12 14:30 dab99282-1dd111b2-84f8fd5b-e7890000.sema
-rw-------. 1 dirsrv dirsrv      30 Dec  9  2012 DBVERSION

389-ds-base-1.2.11.29-1.el6.x86_64

Noriko reproduced with master as well.

Comment 1 Noriko Hosoi 2014-05-16 20:29:05 UTC

Steps to reproduce:
1. set up MMR
2. run some modify operations to generate a change log db
3. stop a server
4-1. /path/to/db2bak
4-2. /path/to/db2bak -D 'cn=directory manager' -w <pw>
5-1. restore from 4-1.
5-2. start the server and verify the server is healthy.
5-3. stop the server.
6-1. restore from 4-2.
6-2. start the server and verify the server is healthy.

Comment 3 Sankar Ramalingam 2015-01-14 13:45:26 UTC

I followed the steps to backup and restore using db2bak.pl and db2bak script files, its completed successfully. Hence, marking the bug as Verified.

Build tested: 389-ds-base-1.3.3.1-11

Comment 5 errata-xmlrpc 2015-03-05 09:34:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html