Backing up Sun one
Directory Server 5.2:
Backing up Directory Server online:
Precautions:
- Make sure the server is in read-only state. if you want to have consistent snapshot.
mostly i stop the instance and took backup.
Procedure:
1. Bring
Directory server 5.2 into read-only state by modifying the “nsslapd-readonly” attribute to “on” state using the LDIF, make
sure this directory is not replicated at the time of backing up because this
will cause into replication errors, because at the time of backup server is automatically in read only mod and other server cant send update requests to this server.
2. Backing
up LDIF or binary backup
LDIF backup:
ServerRoot/slapd-instance/db2ldif
–a/safe/place/Example.ldif –s
dc=example,dc=com
Binary backup:
ServerRoot/slapd-instance/db2bak.
/safe/place
3. Copy
the “dse.ldif” configuration file to a safe place.
4. Copy
specific schema to a safe place, make sure that the modified schemas which are
located in 99user.ldif is copied to safe location has well has schemas which
have been updated.
5. Bring
back the Directory Server into read-write-mode by modifying the “nsslapd-readonly” attribute to
“off” state
Restoring after a system failure:
Restoring Directory Server from backup
1.
Install both the OS and also Directory Server with
the same configuration as the original system.
2.
Stop Directory Server and all application
processes.
3.
Overwrite the Directory Server configuration with
the backup version
4.
Restore the schema modifications from the safe
place into the schema directory
5.
Restore all non-replicated backend databases from
LDIF or binary backup. For restoring the replicated-data we need to consider
initializing the replica from the supplier
6.
Restart Directory Server and bring back into
read-write state my modifying “nsslapd-readonly” attribute to “off” state.
7.
Reinitialize replication agreements
8.
Restart application processes on the system.
No comments:
Post a Comment