Cloning a space - key conflict upon restore

I am trying to make a copy of a space, by following the procedure here but I am getting a failure message indicating a duplicate primary key. I have been very careful to confirm that I have modified all occurrences of the space key and space name in the entities.xml file before zipping it and trying to restore. See the message in this screen shot:

It was suggested that I try the resolutions listed here: but that was not useful.

Anyone else solve this problem?

1 answer

1 accepted

1 vote
Accepted answer

The PK problem may not be related to the backup/restore at all. Other common causes for this are migrating from a database without case insensitivity to one that does. Try the restore without the cloned space.

As for copying the space, I suggest giving the Copy Space Plugin (See: ago. Its much easier to use than manually manipulating the backup xml files and generally works better.

Sure would be nice if Copy Space Plugin were available in OnDemand instances.

As it stands, manually doing things is the only way for us OnDemand users, which sorta defeats the purpose of paying for a hosted solution.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in New to Confluence

How to use Confluence Cloud for stakeholder management

Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...

1,183 views 4 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you