Optimizing 5.0 to 6.0 LDAP upgrade: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
=Pre-upgrade tuning= | =LDAP customization | ||
==Pre-upgrade tuning== | |||
When upgrading from ZCS 5.0.x to ZCS 6.0.x, the LDAP database is exported and then re-imported as the OpenLDAP and underlying database software have changed versions, requiring that this be done. It is possible to optimize this process by increasing the resources available to OpenLDAP to perform this task before starting the upgrade. | When upgrading from ZCS 5.0.x to ZCS 6.0.x, the LDAP database is exported and then re-imported as the OpenLDAP and underlying database software have changed versions, requiring that this be done. It is possible to optimize this process by increasing the resources available to OpenLDAP to perform this task before starting the upgrade. | ||
==Schema migration== | |||
Revision as of 21:12, 14 April 2009
- This article is a Work in Progress, and may be unfinished or missing sections.
=LDAP customization
Pre-upgrade tuning
When upgrading from ZCS 5.0.x to ZCS 6.0.x, the LDAP database is exported and then re-imported as the OpenLDAP and underlying database software have changed versions, requiring that this be done. It is possible to optimize this process by increasing the resources available to OpenLDAP to perform this task before starting the upgrade.
