I am planning to update LDAP OpenDJ 2.6.4 version to OpenDJ 4.4.11 version. Is there any recommended way to migrate the data to the new OpenDJ 4.4.11 LDAP server with minimalistic downtime?
The expectation is to migrate the data records to OpenDJ 4.4.11 version, with minimum downtime.
OpenDJ supports replication of data between servers of different versions.
And it also supports easy upgrade from version 2 to version 4.
If you have setup high availability through replicated servers, you should be able to upgrade with no downtime of the service.
Related
I'm trying to perform an upgrade on an environments 2 OpenDJ directory servers with 1 standalone replication server between them referring to the 3.5 Upgrade doc. However, I could not find information on the order of upgrade for replication topology with standalone replication server. Should we go with upgrade of Directory servers first followed by replication, or vice versa. Can upgrade script identify between replication and directory servers.
It doesn't matter, replication is compatible between versions.
We have a situation where IBM Data Replication CDC for Db2 on i ver 6.1 (AS400) is installed as the source and Oracle 10.2.x being the target. A hardware upgrade is being scheduled on the source with a new AS400 box coming in, the existing database would be migrated/transferred to the new box. The Oracle box will stay the same and only an upgrade of the CDC agent is to be done. Management Console and Access Server are going to be upgraded too as part of this exercise.
In this scenario, we want to install CDC ver 11.4 on the new AS400 box to take advantage of the latest version and fixes. My queries are, (some might be silly, my apologies)
Would this be an install or upgrade on the new AS400 box as the database contains CDC related information?
What would happen to the subscriptions, would they have to be created again or an export/import of subscriptions work?
Will a refresh have to be triggered?
Given the target is the same and source is a new server, what are the implications and how to resolve them?
You should be aware that CDC v6 and CDC v 10.2.x are no longer supported (except for the zSeries 10.2.1 version) so if you have any issues during your migration process you may find it difficult to get support.
In general terms, you should be able to install something like CDC 11.3.3 on the current iSeries in advance of the migration as this version of CDC supports OS/400 6.1 and 7.1 7.2 and 7.3. Then you can save/restore the CDC product library along with all the other libraries. Do not forget to add the TCP/IP listener port service as well. If there is a change of hostname or IP address, you should follow the documented procedure to update the datastore properties in the Access Server https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.cdcdoc.mcadminguide.doc/tasks/handlinghostportforsource.html
Before you restart operations on the new iSeries, you will either need to mark table capture point for all source tables or use SETJRNPOS to manually specify the restart position for replication as the target bookmarks are based on the old journal receiver chain and on the new system this will different
I prefer to upgrade pre-install mainly because it avoids making two changes at the same time. If you had an issue with CDC after migration and then upgrading you would have to determine if it was the new version or the migration that was the cause. However, upgrading the migrated CDC instance immediately after the migration should be OK.
If the IP address or hostname used in the Access Server datastore configuration is changed, you will need to change this following this procedure
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.cdcdoc.mcadminguide.doc/tasks/handlinghostportforsource.html
I currently have a dedicated server running the following:
Apache/2.2.32
WHM/CPanel 11.44.3 (build 5)
MySQL Server version: 5.5.40-cll
Because of a security with the version of Cpanel I am told by my hosting company that Cpanel requires an update. The issue they have is because the current Cpanel is version 11.44.3 they can not update to the latest version.
Question, has anyone else had this issue and if so what was if any the resolution.
Many thanks in advance for your time
The hosting company are telling me that the only way around this issue is to have a completely new server configured with all the latest Apache, WHM/CPanel.
This of course would require all the scripts for our web site been transferred to the new server.
You have too old version and to avoid possible issues and downtime, it is recommended to setup and new server with CentOS 7 and latest cPanel and then migrate account one by one. This will allow you to check your websites one by one as you migrate. You should be able to generate full account backup and then you can restore it on a new server.
There is possibility to upgrade the version on your existing server but it is possible that it may cause other issues and you may face lots of issues and downtime.
I have a Visual SVN Server 3.2 x64 installed in Windows 2008 R2 Server x64.
I have less or more 50 projects with some huge binary files (eg.: 500 MB). After a commit with large change (difference/delta) on those huge binary files i have notice a cpu peak. The server has a bit of traffic (400 clients/hour) and is fully dedicated to Visual SVN Server (AWS EC2 large instance)
After a little investigation i think the problem is in the default compression of the default settings of Visual SVN Server.
Increase cache on delta doesn't help.
Visual SVN Server/subversion has a problem with compression large delta?
Disable it, when the delta between the commits is huge, is a best practice?
Other good suggestion is appreciated. Thanks.
Please, upgrade the server to the most recent version and see whether it helps. I'm pretty sure that the issue you've encountered has been already fixed. If the upgrade won't help, please drop us a line at support#visualsvn.com.
Upgrading from VisualSVN Server 3.2 to the latest 3.5 version should complete in less than 5 minutes. Please read KB95: Upgrading to VisualSVN Server 3.5 guide before beginning the upgrade.
You can get the latest VisualSVN Server installer at the main download page.
VisualSVN Server 3.2.x has reached End of Support in September, 2015. VisualSVN Server 3.2.x is not supported anymore and does not receive security and patch updates.
Please, keep your server instance up-to-date. We timely release maintenance updates for VisualSVN Server with security and bugfixes, and we strongly recommend our users to keep VisualSVN Server at the latest version. The list of fixed vulnerabilities is available for every release in VisualSVN Server changelog and on our release announcements page.
i'm working in installing and configuring Alfresco community edition 4 (alfresco-community-4.0.d-installer-linux-x64.bin) on a 64bit ubuntu server (10.04.4 LTS). I'm trying to authenticate and syncronize users and group with out OpenLDAP server but as long as we make changes to
$TOMCAT_HOME/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1/ldap-authentication.properties
i have to restart tomcat or the whole server.
Is there a way to restart only a single subsytem in alfresco community edition?
Thanks
Unfortunately, not. The reason is that JMX, which allows you to restart subsystems without a restart, is only available in Enterprise Edition.