Please refer to Troubleshooting failed XML site backups instead.

If creating an XML backup of Confluence fails with a stack trace error similar to this, your database has become slightly corrupted. This is likely to have occurred while using the embedded database. If you are using the embedded database, be aware that it is bundled for evaluation purposes and does not offer full transactional integrity in the event of sudden power loss, which is why an external database is recommended for production use.

To correct the corruption, increase the level of logging to identify the cause and manually correct any invalid entries in the database. To do this:

  1. Confluence を終了します。
  2. Open the confluence/WEB-INF/classes/log4j.properties and add this to the bottom and save: 
    log4j.logger.com.atlassian.confluence.importexport.impl.XMLDatabinder=DEBUG, confluencelog
log4j.additivity.com.atlassian.confluence.importexport.impl.XMLDatabinder=false
  3. Restart Confluence and begin a backup.
  4. When the backup fails, the error will be logged to the log files. Open the most recent log and review the stack track of the error for information identifying the object causing the failure. Here's an example error you can use to identify the database object: 
    2005-08-24 00:00:33,743 DEBUG [confluence.importexport.impl.XMLDatabinder] Writing object: com.atlassian.confluence.core.ContentPermission with ID: 5 to XML.
2005-08-24 00:00:33,743 DEBUG [confluence.importexport.impl.XMLDatabinder] Writing property: type
2005-08-24 00:00:33,743 DEBUG [confluence.importexport.impl.XMLDatabinder] Writing property: group
2005-08-24 00:00:33,743 DEBUG [confluence.importexport.impl.XMLDatabinder] Writing property: expiry
2005-08-24 00:00:33,743 DEBUG [confluence.importexport.impl.XMLDatabinder] Writing property: content
[ERROR] LazyInitializer - Exception initializing proxy <net.sf.hibernate.ObjectNotFoundException: No row with the given identifier exists: 2535, 
of class: com.atlassian.confluence.core.ContentEntityObject>net.sf.hibernate.ObjectNotFoundException: 
No row with the given identifier exists: 2535, of class: com.atlassian.confluence.core.ContentEntityObject
	at net.sf.hibernate.ObjectNotFoundException.throwIfNull(ObjectNotFoundException.java:24)
	at net.sf.hibernate.impl.SessionImpl.immediateLoad(SessionImpl.java:1946)
	at net.sf.hibernate.proxy.LazyInitializer.initialize(LazyInitializer.java:53)
	at net.sf.hibernate.proxy.LazyInitializer.initializeWrapExceptions(LazyInitializer.java:60)
	at net.sf.hibernate.proxy.LazyInitializer.getImplementation(LazyInitializer.java:164)
	at net.sf.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:108)
	at com.atlassian.confluence.core.ContentEntityObject$$EnhancerByCGLIB$$cc2f5557.hashCode(<generated>)
	at java.util.HashMap.hash(HashMap.java:261)
	at java.util.HashMap.containsKey(HashMap.java:339)
	at com.atlassian.confluence.importexport.impl.XMLDatabinder.toGenericXML(XMLDatabinder.java:155)
    This excerpt from a log file shows that there was an error trying to confer the ContentPermission object with id 5 into XML. The database object is a row in the CONTENTLOCK table with id = 5 and reset CONTENT column property so that it no longer points to the id 2535 (the id of an entry that no longer exists). If you are wondering which table a certain object is stored in, here's a rough guideline: Pages, blogposts, comments are stored in the CONTENT table, attachments in the ATTACHMENTS table.
  5. データベース管理ツールを使用して、Confluence データベースにログインします。関連するテーブル内の行を見つけて、エントリーを修正します。テーブル内の他の行のデフォルト列値について確認します。これは null、0、または空白である場合があります。不正な行の値をデフォルト値で上書きします。
  6. Once the database has been updated, restart Confluence and reattempt the backup.
  7. To help prevent this issue from reoccurring - If you are using the embedded database, you should migrate to an external database.
  8. To help prevent this issue from reoccuring - If you are using an older version of Confluence than the latest), you should consider upgrading at this point.