Cloning a space - key conflict upon restore

[Kevin Buchs]

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: https://docs.google.com/present/view?id=ddhxzkwn_180pjscznm6

It was suggested that I try the resolutions listed here: http://confluence.atlassian.com/display/CONFKB/Cannot+Create+or+Restore+XML+Backup+Due+to+Primary+Key+Constraint but that was not useful.

Anyone else solve this problem?

[m@ · Accepted solution]

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: https://studio.plugins.atlassian.com/wiki/display/CPSP/Confluence+Copy+Space+Plugin) ago. Its much easier to use than manually manipulating the backup xml files and generally works better.

[TJ Baker]

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.