Cisco Cisco Agent Desktop 10.0 Fehlerbehebungsanleitung
Cisco CAD Troubleshooting Guide
48
April 28, 2015
If the above procedure does not work, complete the following steps.
LDAP Monitor service will automatically backup the Directory Services database every
night at midnight. The backups are stored in the ...Cisco\Desktop\ldap_archive folder.
It maintains backups of the last four days. The backup file is named
LdapAutomaticBackup<timestamp>.ldif, where <timestamp> is the number of
seconds since January 1, 1970 (for example, LdapAutomaticBackup_
1339477261406.ldif). You can use the file timestamp to determine when the backup
was made.
night at midnight. The backups are stored in the ...Cisco\Desktop\ldap_archive folder.
It maintains backups of the last four days. The backup file is named
LdapAutomaticBackup<timestamp>.ldif, where <timestamp> is the number of
seconds since January 1, 1970 (for example, LdapAutomaticBackup_
1339477261406.ldif). You can use the file timestamp to determine when the backup
was made.
To recover the Directory Services database (Method 3):
1. On the PC hosting the database, stop the LDAP Monitor service.
2. Rename …Cisco\Desktop\database to …Cisco\Desktop\old_database.
3. Create a new folder called …Cisco\Desktop\database.
4. Copy DB_CONFIG and all files with a *.dat extension from the old_database
folder to the new database folder.
5. Copy one of the Directory Services database backup files from the
...Cisco\Desktop\ldap_archive folder to the new database folder. Choose the
backup file from a date on which the Directory Services database was known
to be good.
backup file from a date on which the Directory Services database was known
to be good.
6. Open a command window and change directories to …Cisco\Desktop\bin (the
drive and exact location of this directory depends on where the services were
installed).
installed).
7. Type the following command and press Enter.
slapadd -f slapd.conf -l LdapAutomaticBackup<timestamp>.ldif -c
8. Type
exit
and press Enter to close the DOS window.
9. Restart the LDAP Monitor service.
Out of Sync Directory Services Databases
The secondary Directory Services database can become out of sync with the primary
Directory Services database. A possible reason for this to occur is that the secondary
database was reinstalled.
Directory Services database. A possible reason for this to occur is that the secondary
database was reinstalled.
Follow these steps to sync up the two databases:
1. On the PC hosting the database, stop the LDAP Monitor service.
2. Open a command window on the primary database computer.
3. Change directories to …Cisco\Desktop\bin (the drive and exact location of
this folder depends on where the service was installed).