Skip to main content
formis17
Level 2
October 16, 2015
Solved

Replication from one server to another

  • October 16, 2015
  • 3 replies
  • 2005 views

I am using 5.4. I am attempting to move content from one server to another using the replication tool. However, I get the following error upon replication:

Error while building replication content com.day.cq.replication.ReplicationException: RepositoryException during serialization

I also tried to transfer the content via packages, but I got an error in package manager saying, 

"No space left on device"

I saw a post that said I need to clear the tmp folder to correct this issue, but I don't know how to do this.

Any suggestions concerning either of these errors are most welcome!

Thanks!

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 Sham_HC

*  Traditional locations for operating system at http://en.wikipedia.org/wiki/Temporary_folder

 

The replication and package manager uses temp directory. Make sure the temp directory size is always double the size of package and replication at a given point of time.

You can change the temp directory to mount to other drive that has enough space. In order to do that modify the startup script to include [1] to set JVM parameters for path of tempdir and let me know how it goes.

[1] -Djava.io.tmpdir=<hugeemptydiratD>

3 replies

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

*  Traditional locations for operating system at http://en.wikipedia.org/wiki/Temporary_folder

 

The replication and package manager uses temp directory. Make sure the temp directory size is always double the size of package and replication at a given point of time.

You can change the temp directory to mount to other drive that has enough space. In order to do that modify the startup script to include [1] to set JVM parameters for path of tempdir and let me know how it goes.

[1] -Djava.io.tmpdir=<hugeemptydiratD>

rampai
Community Advisor
Community Advisor
September 18, 2017

Is there a need to restart the AEM instance after doing this?

joerghoh
Adobe Employee
Adobe Employee
September 18, 2017

Technically it's not required. But when your system already logged "no space left on device" I would check if the volume holding the temp directory was affected or the volume where the repository resides.

Jörg