[
https://issues.apache.org/jira/browse/DIRSERVER-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307721#comment-16307721
]
Emmanuel Lecharny commented on DIRSERVER-2216:
----------------------------------------------
Once the database is corrupted, teh export is likely to fail.
We have added a feature in M24 that *could* restore the database, you just have
to restart the server with the 'repair' command instead of 'start'. It reads
the Master table (which contains the entries) and the RDN table (which contains
the entry's DN) an tries to restore the indexes.If you are lucky, the server
should be able to work properly.
> Data corruption with the export
> -------------------------------
>
> Key: DIRSERVER-2216
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2216
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: installer-plugin
> Environment: Windows
> Reporter: prisy cherian
> Fix For: 2.0.0-M24
>
> Attachments: ldap_backup_2017-12-28_13-13-15.ldif
>
>
> Hi,
> We are using Apache DS in Windows for an year now.
> We started with 50 users for development and everything was working as
> expected.
> We scheduled backups every 2 hours.
> Later in Production, LDAP data hangs & Search stops to work throwing USER NOT
> FOUND or LDAP Connection Timeout Exception or Attribute not found etc. The
> exception differs every time, eventually we found out in one of the back up
> files that it is Data Corruption.
> Everytime, we had to restore the backup & it is more than 10 times by now.
> We have around 11,000 users now. We schedule backup every day.
> We found a similar issue happening in M17 & M20 with the large number of user
> import-export.
> Is this issue with JDBM Backend is still in M24 also?
> Can you please suggest ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
