[Date Prev][Date Next]
slapd-config(5) Disaster Recovery - Best Practices?
- To: email@example.com
- Subject: slapd-config(5) Disaster Recovery - Best Practices?
- From: firstname.lastname@example.org
- Date: Tue, 16 Jun 2009 10:02:54 -0700 (PDT)
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245171774; bh=wn11Hon8A29FgKnsMXPZdiDqaLHnRSwR/JYXgMF+0Pc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=4eVH+KRx6JSmlrfXYZTNuxwEeDF5T3nBAjuhXo/0fxboafee0oe+zwrgh+FB8MUANXa9nC4GOAAeffG+2Q1/hDRk4wgtUewKcL/xMxbY1czd7QIHl9TlHYDcLFLOYa4jsUat26tAOmTxQb3xFRgZi6WO4m984VY41wj7XUWUPBU=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=wedz0iMbIYxTaHdRcG498PDSlzTDmMfn3+mWFj9dg5GRzFipUPSIoC7PW8iJS26CxqXLOmFmHPfSLyyJ1xkSL1honbim8SGEqRxA9Z9z5U3SfMQQ0zsyUElZOEDSeAS4sSvAdzpQNf5pbRE32GavLWWcCpjBAjzLVUiLZ5ccxjQ=;
I am considering migrating from a monolithic slapd.conf file to the newer DIT slapd-config(5).
My primary concern is how to recover if a dynamic change brings down slapd so it becomes difficult to recover since the configuration is in a database and slapd will not start.
Is it as simple as making a slapcat backup of the configuration database (or some other backup of the configuration database that resides in the slapd.d directory) prior to making changes so that a roll-back would consist of replacing the contents of the slapd.d directory? Or is there some other recovery method that is preferred?