I'm reviewing our backup/restore scripts and processes. The
directory in question has a single suffix containing about 41,000
entries. It has a single R/W instance, with several R/O replicas,
running 389-Directory/1.4.4.
Working with on-line data, if needed, we could turn one of our
R/O instances into a R/W, and create some new replication
agreements. Or, we could build a new R/W instance, and populate it
by exporting the required information from a R/O instance. We'd
have additional work to do with certs, DNS, and hostnames to put
the finishing touches on.
To make an off-line backup of our R/W instance, we have a scripted process which does:
makes a tar of those and the contents of:
and parks the resulting .tar in a safe place for a couple of months.
My questions are:
-- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston@alaska.gov Department of Administration State of Alaska