Shrink space on migration

John Douglas January 7, 2013

Planning on migrating to Linux and oracle from Mac OSX and Mysql. Overall mysql DB <8Gb. But several spaces may be over 2GB. Would like to reset all space pages to their current version and reduce the DB size and time on conversion. Currently running OSX and Mysql at 64bit so java app isn't a problem. However, documentation states that the space export/import feature will be a problem if export > 2GB.

Will this be an issue or is 2Gb export file size going to be a problem with conflucene import?

3 answers

1 vote
Daniel Borcherding
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 8, 2013

John,

I just wanted to post a link to the feature request that we created for your issue from our support ticket yesterday. Perhaps other people have the same question and we can garner some more votes fro the feature by posting it here.

https://jira.atlassian.com/browse/CONF-27689

Hopefully someone in the Community has a good workaround for you until this feature is rolled into our product.

For completeness lets also post the troubleshooting guide for getting around Out of Memory Errors that you may run into during your XML export of your instance

https://confluence.atlassian.com/display/CONFKB/Cannot+Create+XML+Backup+Due+to+OutOfMemory+Errors

1 vote
AlysonA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2013

Hello,

Indeed exporting/importing really large XML files can be an issue in Confluence. But since you're migrating to a different database, you will need to follow the large installation procedure to migrate your data from one db to another, that includes taking an XML backup without attachments.

I suggest you try this approach and see how it goes.

Cheers.

0 votes
John Douglas January 15, 2013

Thanks on the XML only suggestion. In fact we started off draconian by limiting any attachments to 2MB and creating a seprate WORM file service where users put larger files like their presentation's . Its ~ 1/2TB. So pretty much just the 25,000 pages which average 9 to 1 for versions. Probably not bad for a 5 year old system, but we keep the space's limited and strictly by ACL/ group.

As migration will likely be staged by group/space an alternative is to cleave off major branches of a large space to their own space an migrate them separately.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events