Expand my Community achievements bar.

SOLVED

Replication from one server to another

Avatar

Level 2

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!

1 Accepted Solution

Avatar

Correct answer by
Level 10

*  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>

View solution in original post

3 Replies

Avatar

Correct answer by
Level 10

*  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>

Avatar

Level 7

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

Avatar

Employee Advisor

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