How do I avoid common pitfalls when upgrading DS (All versions)?
The purpose of this article is to provide information on common pitfalls you should be aware of before upgrading DS.
1 reader recommends this article
Upgrading DS
To ensure your upgrade goes smoothly, this article provides pre-upgrade advice, including advice common to all versions and version specific known issues.
Note
As with any software upgrade, we strongly recommend testing the procedure in your own development environment first and ensuring you have up to date backups and recovery plans in case you encounter any issues. You should also make sure you read the release notes relating to the new version of DS so that you are fully aware of all the changes.
Upgrade advice for all versions
Newer versions of DS will install and work seamlessly with older versions in a cluster to allow for a rolling upgrade. Replication will also work between different versions of DS.
This advice includes, but is not limited to:
- Performing a rolling upgrade is recommended as described in How do I perform a rolling upgrade of DS (All versions)?
- Performing the upgrade procedure as the user who owns the DS server files.
- Performing a full backup of your current DS installation to ensure you can revert if the upgrade fails. This is described in Backup and Restore (DS 7 and later) or Backing Up and Restoring Data (Pre-DS 7).
- Unzipping the newer DS release over the top of the previous DS installation.
- Ensuring you are running a compatible Java® version. This is described in Upgrading DS (All versions) fails with UnsupportedClassVersion error.
- Upgrading the DS Password Sync Plugin for IDM if you use it to ensure it's compatible. The correct process is described in How do I upgrade DS (All versions) if I have the DS Password Sync Plugin for IDM installed?
- Checking the DS version you want to use is compatible with the AM version you are using: What versions of DS are compatible with AM?
Known issues in DS 6.x
Note
Before upgrading to DS 6.x, you must convert the PDB backend to a JE backend since this backend is removed in DS 6. See How do I convert a PDB backend to a JE backend in DS 5.x or OpenDJ 3.x? for further information.
The following known issues may affect you post-upgrade - workarounds are included where applicable:
- Failing to add the required permissions for monitoring dsreplication will result in "Insufficient Access Rights" errors when running dsreplication. See Insufficient Access Rights error for dsreplication status after upgrading a replicated server to DS 6.x for further information.
- Changes in AM and DS have made LDAP SSL hostname validation stricter. You must ensure the hostname you are connecting to the LDAP server with matches the hostnames specified in the server certificate via the SAN (Subject Alternative Name). See LDAP connection fails with No subject alternative DNS name matching error in AM 5.1.x, 5.5.2, 6.x, 7.x and DS 5.5.1, 5.5.2, 6.x, 7.x for further details about this issue and solution.
Known issues in DS 5.x
The following known issue may affect you post-upgrade - workarounds are included where applicable:
- Changes in AM and DS have made LDAP SSL hostname validation stricter. You must ensure the hostname you are connecting to the LDAP server with matches the hostnames specified in the server certificate via the SAN (Subject Alternative Name). See LDAP connection fails with No subject alternative DNS name matching error in AM 5.1.x, 5.5.2, 6.x, 7.x and DS 5.5.1, 5.5.2, 6.x, 7.x for further details about this issue and solution.
See Also
FAQ: Backup and restore in DS 5.x and 6.x
FAQ: Installing and configuring DS
DS (All versions) fail to start after upgrade if you use the Password Sync Plugin for IDM
Related Training
Related Issue Tracker IDs
N/A