The Directory Server Enterprise Edition provides the
following LDAP Backup methods:
Ø Binary Backup Process
Ø Backup to LDIF File
Binary Backup Process
The Binary Backup Process
produces a copy of the database files, and is performed at the file system
level. The output of a binary backup is a set of binary files that contains all
entries, indexes, the change log, and the transaction log. A binary backup does
not contain configuration data.
The
Binary Backup Process is performed
using one of the following commands:
Ø
dsadm backup must be run offline, that is, when
the Directory Server instance is stopped. The command must be run on the local
server containing the Directory Server instance.
$dsadm
backup /dsee7/dsinstances/instancesname
/dsee7/dsinstances/instancesname/bak
Ø
dsconf backup
can be run online and remote to the Directory Server instance.
$dsconf backup
/dsee7/dsinstances/instancesname
/dsee7/dsinstances/instancesname/bak
The Binary Backup
Process has the following advantages:
Ø All suffixes can be backed up at the same time.
Ø The Binary Backup
Process is significantly faster than a Backup
to LDIF File process.
Ø The replication change log is backed up.
Note:
Ø Binary backup has one limitation. Restoration from a binary
backup can be performed only on a server with an identical configuration.
Ø At a minimum, you need to perform a regular binary backup on
each set of coherent machines. Coherent machines are machines that have an
identical configuration.
Ø Because restoration from a local backup is easier, perform a
binary backup on each server.
Backup to LDIF File
The Backup to LDIF File is performed at the suffix level. The output
of a backup to LDIF is a formatted LDIF file, which is a copy of the data
contained in the suffix. As such, this process takes longer than a binary
backup.
The Backup to
LDIF File is performed using one of the following commands:
Ø dsadm
export must be run
offline, that is, when the Directory Server instance is stopped. This command
must be run on the local server containing the Directory Server instance.
$dsadm export /dsee7/dsinstances/instances-name
o=suffix.com /dsee7/dsinstances/instance-name/ldif/ldif_name.ldif
Ø
dsconf export can be run online and remotely
to the Directory Server instance.
$dsconf export –h servername –p389 o=suffix.com
/dsee7/dsinstances/instances-name/ldif/ldif_name.ldif
Note:
Ø
Replication information
is backed up, only if you use the -Q
option with the preceding commands.
Ø
The configuration file
is not backed up in Backup to LDIF File
Process. To enable you to restore a previous configuration, backup this file
manually.
The Backup to
LDIF File has the following
advantages:
Ø
The Backup to LDIF File can be performed from any server, regardless of
its configuration.
Ø
Restoration from an LDIF backup can be performed on any
server, regardless of its configuration.
The Backup to LDIF File process
has limitation in situations where rapid backup and restoration are required.
The Backup to LDIF File process
might take too long to be viable. Therefore, an administrator needs to perform
a regular backup by using Backup to LDIF
File process for each replicated suffix, on a single master in the
topology.
RESTORE LDAP
Ø Binary Restore Process
Ø Restoration from LDIF File
Binary Restore Process
The Binary Restore Process copies data at
the database level. Binary Restore
is performed using one of the following commands:
Ø dsadm restore must be run offline, that is, when the
Directory Server instance is stopped. This command must be run on the local
server containing the Directory Server instance.
$ dsadm restore
/dsee7/dsinstance/instance-name \
/dsee7/dsinstances/instance-name/bak/backup_filename
Ø dsconf
restore can be run online and remote to
the Directory Server instance.
$
dsconf restore -h servername -p port
dsee7/dsinstances/instancesname/bak/backupfilename
The Binary Restore
Process has the following advantages:
Ø
All suffixes can be
restored at the same time.
Ø
The replication change
log is restored.
Ø
The Binary Restore Process is significantly faster than restoring from
an LDIF file.
The Binary Restore
Process is the preferred restoration method, if the machines have an
identical configuration and time is a major consideration.
Restoration from LDIF File
The Restoration from LDIF File is performed at the suffix level. As
such, this process takes longer than the Binary
Restore Process. The Restoration
from LDIF File can be performed using one of the following commands:
Ø dsadm
import must be run
offline, that is, when the Directory Server instance is stopped. This command
must be run on the local server containing the Directory Server instance.
$dsadm import
/dsee7/dsinstances/instance-name
/dsee7/dsinstances/instance-name/ldifl/ldif_filename.ldif
o=suffix.com(suffix DN)
Ø dsconf
import can be run
online and remote to the Directory Server instance.
$dsconf import –h
servername –p port
/dsee7/dsinstances/instance-name/ldif/ldif-file_name.ldif o=suffix.com(suffix
DN)
Ø This command can be performed on any server,
regardless of its configuration.
Ø A single LDIF file can be used to deploy an entire
directory service, regardless of its replication topology. This functionality
is particularly useful for the dynamic expansion and contraction of a directory
service according to anticipated business needs.
The Restoration
from an LDIF File has a limitation in situations, where rapid restoration
is required. This method might take too long to be viable.
very usefull, thanks
ReplyDelete