Solved

Cloning AEM Instance from One Server to Another Server

Forum|Forum|6 years ago
March 27, 2019
13 replies
10542 views

Dear All,

We have AEM instance on one server with heavy DAM. In order to save time, we would like to clone AEM instance from this server (pre prod) to another server (prod) for example.

Could you please provide some inputs on best practices.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by BrijeshYadav

Yes, it will work without any issue. This is called offline backup in AEM.

The important thing to remember that make sure you change correct run mode before you start AEM at the new location.

Read here more about offline Backup and Restore

Offline Backup

You can always do an offline backup. This requires a downtime of AEM, but can be quite efficient in terms of required time compared to an online backup.

In most cases, you will use a filesystem snapshot to create a read-only copy of the storage at that time. To create a offline backup perform these steps:

stop the application
make a snapshot backup
start the application

smacdonald2008

Look here. Using the CRX2Oak Migration Tool

Gaurav-Behl

Do you mean from a lower environment to upper environment? You may use vlt-rcp or grabbit or rsync

check -

Assets Migration Guide

MCP Asset Ingestion Tools

Migrating huge AEM Content from in-house to Cloud (new infrastructure)

Moving DAM Assets

vish.dhaliwal

Adobe Employee

Few more options:

1. Check this article - How to clone a TarMK instance in AEM

2. Use online backup and then restore.

3. Use packages https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/package-manager.html

4. Use VLT-RCP tool https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/ht-vlttool.html

Maddy737Author

Will it work it i copy whole structure including crx-quickstart, cq jar and license file to another server? Or do i face any issue?

smacdonald2008

Read through the links provided here - they explain everything you need to know for this use case.

BrijeshYadavAccepted solution

Yes, it will work without any issue. This is called offline backup in AEM.

The important thing to remember that make sure you change correct run mode before you start AEM at the new location.

Read here more about offline Backup and Restore

Offline Backup

You can always do an offline backup. This requires a downtime of AEM, but can be quite efficient in terms of required time compared to an online backup.

In most cases, you will use a filesystem snapshot to create a read-only copy of the storage at that time. To create a offline backup perform these steps:

stop the application
make a snapshot backup
start the application

Maddy737Author

Thank you yadav,

I took the copy and moved to new server when instance is up. After restart the original server is giving error “authentication service dependencies missing” and cannot login to the server.

Does copying while isntance is up caused the issue? What should i do to resolve? Kindly help.

thanks

BrijeshYadav

Please mention here if you make any other changes to any file to AEM repository after you moved to a new location?

Now try to login via crx/de and then go to http://host:port/system/console and ensure that the status of all bundles is Active, specifically check the status of Apache Sling Authentication Service bundle, it should have an active status.

Another possible reason could be that indexes get corrupted. You can recreate indexes by deleting or renaming /crx-quickstart/repository/version/index folder.

Maddy737Author

Hi Yadav,

Thanks for the reply. Am talking about the source instance. Accidentally i copied the source instance without stopping it. And now source instance is giving this error.

Thanks

Madhu

Maddy737Author

Also getting below error when i start the server from the new server with offline backup on it.

02.04.2019 09:25:49.395 *INFO* [FelixStartLevel] org.apache.sling.commons.log.logback.internal.Activator LogbackManager initialized at bundle startup

02.04.2019 09:25:49.398 *INFO* [FelixStartLevel] org.apache.sling.commons.log BundleEvent STARTED

02.04.2019 09:25:49.407 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent RESOLVED

02.04.2019 09:25:49.422 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent STARTING

02.04.2019 09:25:49.424 *INFO* [FelixStartLevel] org.apache.sling.javax.activation BundleEvent STARTED

02.04.2019 09:25:49.425 *INFO* [FelixStartLevel] org.apache.felix.configadmin BundleEvent STARTING

02.04.2019 09:25:49.429 *INFO* [FelixStartLevel] org.apache.felix.configadmin Service [Platform Filesystem Persistence Manager,20, [org.apache.felix.cm.PersistenceManager]] ServiceEvent REGISTERED

02.04.2019 09:25:49.440 *INFO* [FelixStartLevel] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,21, [org.osgi.service.cm.ConfigurationAdmin]] ServiceEvent REGISTERED

02.04.2019 09:25:49.441 *INFO* [FelixStartLevel] org.apache.sling.settings Service [org.apache.sling.settings.impl.SlingSettingsServiceImpl,22, [org.osgi.service.cm.ManagedService]] ServiceEvent REGISTERED

02.04.2019 09:25:49.450 *INFO* [FelixStartLevel] org.apache.felix.configadmin BundleEvent STARTED

02.04.2019 09:25:49.458 *INFO* [FelixStartLevel] jcl.over.slf4j BundleEvent RESOLVED

02.04.2019 09:25:49.458 *INFO* [FelixStartLevel] jcl.over.slf4j BundleEvent STARTING

02.04.2019 09:25:49.458 *INFO* [FelixStartLevel] jcl.over.slf4j BundleEvent STARTED

02.04.2019 09:25:49.466 *INFO* [FelixStartLevel] org.apache.sling.installer.factory.configuration BundleEvent RESOLVED

02.04.2019 09:25:49.467 *INFO* [FelixStartLevel] org.apache.sling.installer.factory.configuration BundleEvent STARTING

02.04.2019 09:25:49.468 *INFO* [FelixStartLevel] org.apache.sling.installer.factory.configuration BundleEvent STARTED

02.04.2019 09:25:49.469 *INFO* [FelixStartLevel] org.apache.sling.installer.core BundleEvent STARTING

02.04.2019 09:25:52.480 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[org.apache.felix.http])] org.apache.felix.http.jetty Failed to start Connector: ServerConnector@40fc84db{HTTP/1.1,[http/1.1]}{0.0.0.0:4503} (java.net.BindException: Address already in use)

java.net.BindException: Address already in use

at sun.nio.ch.Net.bind0(Native Method)

at sun.nio.ch.Net.bind(Net.java:433)

at sun.nio.ch.Net.bind(Net.java:425)

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:339) [org.apache.felix.http.jetty:4.0.6]

at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:307) [org.apache.felix.http.jetty:4.0.6]

at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) [org.apache.felix.http.jetty:4.0.6]

at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235) [org.apache.felix.http.jetty:4.0.6]

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyService.startConnector(JettyService.java:695) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyService.initializeHttp(JettyService.java:546) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:444) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:305) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyService.start(JettyService.java:148) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyServiceStarter.<init>(JettyServiceStarter.java:37) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.http.jetty.internal.JettyManagedServiceFactory.updated(JettyManagedServiceFactory.java:68) [org.apache.felix.http.jetty:4.0.6]

at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)

at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)

at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1232) [org.apache.felix.configadmin:1.9.0.B006]

at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1176) [org.apache.felix.configadmin:1.9.0.B006]

at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) [org.apache.felix.configadmin:1.9.0.B006]

at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) [org.apache.felix.configadmin:1.9.0.B006]

at java.lang.Thread.run(Thread.java:748)

02.04.2019 09:25:52.488 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[org.apache.felix.http])] org.apache.felix.http.jetty Jetty stopped (no connectors available)

02.04.2019 09:25:52.488 *ERROR* [CM Configuration Updater (ManagedServiceFactory Update: factoryPid=[org.apache.felix.http])] org.apache.felix.http.jetty Exception while initializing Jetty. (java.lang.NullPointerException)

java.lang.NullPointerException: null

at org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:489) [org.apache.felix.http.jetty:4.0.6]