confluence 3.4.9 xml backup always failed

[Ping Xiao]

Hello,

I'm doing xml backup from our current confluence v3.4.9. It has 3GB in its home directory. DB2 is the database. The backup always failed and i never got zip file in home directory.

The atlassian-confluence.log shows ERROR as below.

(1) Is the backup related to the size of data? Are there command-line to run backup (i.e. export)?

(2) We have installed a confluence v3.5.17 on a separate server. We would like to restore the v3.4.9 data to new v3.5.17. Are there other way to export data from lower version and restore into the newer version of confluence?

Thanks.

--------------------------------- LOG Piece-----------------------------------------

2014-06-27 13:14:30,461 ERROR [TP-Processor16] [sf.hibernate.proxy.LazyInitializer] initializeWrapExceptions Excep
tion initializing proxy
-- referer: https://wiki-ut.isvcs.net/admin/backup.action| url: /admin/dobackup.action | userName: admin | actio
n: dobackup
net.sf.hibernate.ObjectNotFoundException: No row with the given identifier exists: 126559544, of class: com.atlass
ian.confluence.core.ContentEntityObject
at net.sf.hibernate.ObjectNotFoundException.throwIfNull(ObjectNotFoundException.java:24)
at net.sf.hibernate.impl.SessionImpl.immediateLoad(SessionImpl.java:1944)
at net.sf.hibernate.proxy.LazyInitializer.initialize(LazyInitializer.java:53)

---SKIP---

2014-06-27 13:14:30,472 ERROR [TP-Processor16] [confluence.importexport.impl.BackupExporter] backupEntities Couldn
't backup database data.
-- referer: https://wiki-ut.isvcs.net/admin/backup.action| url: /admin/dobackup.action | userName: admin | actio
n: dobackup
net.sf.hibernate.LazyInitializationException: Exception initializing proxy: [com.atlassian.confluence.core.Content
EntityObject#126559544]
at net.sf.hibernate.proxy.LazyInitializer.initializeWrapExceptions(LazyInitializer.java:64)
at net.sf.hibernate.proxy.LazyInitializer.getImplementation(LazyInitializer.java:164)

[Ping Xiao]

Hello,

Do you have any updates?

I tried to do XML backup on the environment which is has 18GB data) but failed with the following error.

2014-07-05 22:02:27,985 WARN [Timer-0] [mchange.v2.async.ThreadPoolAsynchronousRunner] run com.mchange.v2.async.Th

readPoolAsynchronousRunner$DeadlockDetector@157b448 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

Our current confluence is 3.4.9. We'd like to upgrade to 5.5.2. Based on Confluence recommendation, we are going to go through v3.5.17 and v5.0.1 and then v5.5.2. We have built a confluence v3.5.17 without data. How do we load the data from v.3.4.9 to v3.5.17? The v3.4.9 is using DB2. We will use Postgres for newer version. Do you have an upgrade/migration document for our situation?

thanks.

[Ping Xiao]

Do you have size limit for exporting from a large database for Confluence version 3.4.9?

What's the best way if we want to upgrade and migrate from a large database (18GB data)? Currently we are using version 3.4.9 and want to move to latest version 5.5.2. Our plan is to keep current version 3.4.9 and build a brand new 5.5.2 system and migrate data from 3.4.9.

thanks.

[Bruna Griebeler]

Hi,

Seems that the problem is related to the versions. If the XML file was generated on a v3.4.9, it should be imported on v3.4.9 as well. Just then you can upgrade it to a newer version.

The size also is bigger that the recommended for the XML to be well imported (2GB is the max).

So if the problem persists importing the XML using the same version, try exporting/importing spaces froma confluence to another.

Kind Regards