New Identity Store / eDirectory backups

Idea ID 2784828

New Identity Store / eDirectory backups

Most customers are not doing a 3 replica recommendation
Most are implementing two servers and not even having drivers running on the second server in the driver set.

As a result, many also don't setup eDir backups as they should but are relying on snapshotting, which can hose transitive synchronization.

Recommendation:
As part of the installation of eDirectory setup backup location and schedule backups automatically that can of course be configured, but help force the backups as part of the product install and configuration.

Example of issue:
ndsrepair -R error 69 bug hit a customer, they don't have backups and are spending 20+ hours recouping.

Why build it in by default? Most customer's don't have the depth of knowledge with all best practices. eDirectory / IDM is just a small subset of products and technologies. With eDirectory being such a critical piece that is a unique skill set to say a database administrator; many tuning and fault tolerance issues arise. So, if on setup we can help a customer plan storage for backup and have it configured on install all the more we are doing to help them not shoot themself in the foot.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.