Binary-less replication b/w authors | Community
Skip to main content
Adobe Employee
August 30, 2019
Solved

Binary-less replication b/w authors

  • August 30, 2019
  • 4 replies
  • 2474 views

Team,

We have following requirement

1. All our assets are in instance A which is not yet live. Around 170 GB of assets

2. All our live sites are in instance B.

3. Eventually we need to move all content from A to B.

And we want to setup External file datastore for our env.

So, can i do the following?

1.  setup External file datastore

2.  Move the assets from A to External file datastore

3. Map B to point to Same external datastore

4. Create replication agent to to Binary less replication from A to B.

Does this sound logical?

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 joerghoh

That should work, at least from an structural point of view. But crx2oak might have some precautions built in preventing in (for example not to overwrite an already existing datastore).

Give it a try with 2 sample AEM instances just created for this purpose, plus a bit of sample content; then go on to your staging, get the necessary experience and vailidation and finally move it over to PROD.

4 replies

Adobe Employee
August 30, 2019

Jörg Hohmcd​ : Can you please confirm this approach?

joerghoh
Adobe Employee
Adobe Employee
August 30, 2019

That can work. But at point 3, you would need to merge the 2 datastores; system B might have different binaries, and you can use only 1 datastore.

Adobe Employee
August 30, 2019

Thanks.

Any idea how do we do merge the 2 data stores.

One from  instance A and one from Instance B.

Should i merge A's datastore to B'datastore using Crx2oak and then move to External datastore?

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
August 30, 2019

That should work, at least from an structural point of view. But crx2oak might have some precautions built in preventing in (for example not to overwrite an already existing datastore).

Give it a try with 2 sample AEM instances just created for this purpose, plus a bit of sample content; then go on to your staging, get the necessary experience and vailidation and finally move it over to PROD.