Today I attempted to restore the dirsrv-admin to a previous version.
I used this Documentation, "4.3.4. Restoring a Single Database" from Redhat's
web site.
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Populating_Directory_Databases-Backin
On 05/02/2016 01:14 PM, Job Cacka wrote:
Today I attempted to restore the dirsrv-admin to a previous version.
I used this Documentation, "4.3.4. Restoring a Single Database" from Redhat's
web site.
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration
Thanks for the quick reply Mark.
Perhaps I do not understand the layout of 389 DS correctly.
Should there be a separate backup of the dirsrv-admin data?
I think I may have changed a setting in the 389-ds console that took affect
after one of the reboots we had this winter/spring.
My hope was
On 05/02/2016 01:44 PM, Job Cacka wrote:
Thanks for the quick reply Mark.
Perhaps I do not understand the layout of 389 DS correctly.
Should there be a separate backup of the dirsrv-admin data?
No - there is no backup functionality for the HTTP admin server.
I think I may have changed a se
"There are config files for the admin server: /etc/dirsrv/admin-serv"
That directory has many files that have changed recently. It looks like I have
two "backup" directories in there. One is labeled 10-21-15 and the other is
10-7-2013 from the original installation. So I could stop the dirsrv-ad
I looked at this directory location and only two config files are changed since
"go live". When I ran a diff against the originals in the backup file it
contains differences that turn on SSL and other related settings. There are
some anomalies though some parameters are in quotes and some are no
