Hello to all,
due to a weird behaviour in zmsetup.pl sometimes you will find the field "Use ephemeral storage" automatically set to yes.
This prevents us to automate securely Zimbra updates. So we need a clarification on how Ephemeral Storage works.
Old documentation says that the migration to Ephemeral Storage is one-way-only, so no one of our customers has adopted it.
As we stated before we had some infrastructures that after a bugged install.sh had the "Use ephemeral storage" left to yes. This seems to have had effect only on the zimbraEphemeralBackendURL parameter, that has been set to "ldap://default"
Looking at more recent admin guides we found that the migration to eph.stor. needs an explicit setup of this value to "ssdb://something".
Does the "ldap://default" means that the Ephemeral Storage is actually disabled?
Thanks in advance
due to a weird behaviour in zmsetup.pl sometimes you will find the field "Use ephemeral storage" automatically set to yes.
This prevents us to automate securely Zimbra updates. So we need a clarification on how Ephemeral Storage works.
Old documentation says that the migration to Ephemeral Storage is one-way-only, so no one of our customers has adopted it.
As we stated before we had some infrastructures that after a bugged install.sh had the "Use ephemeral storage" left to yes. This seems to have had effect only on the zimbraEphemeralBackendURL parameter, that has been set to "ldap://default"
Looking at more recent admin guides we found that the migration to eph.stor. needs an explicit setup of this value to "ssdb://something".
Does the "ldap://default" means that the Ephemeral Storage is actually disabled?
Thanks in advance
Statistics: Posted by gabrieles — Mon Apr 29, 2024 1:47 pm