Confluence 4.0 : Providing Database Dump with Content Anonymised
This page last changed on Sep 15, 2011 by rhartono.
Particularly for indexing issues, it is useful to provide a database backup to Support so that they can reproduce the issue. However, some of your content may be private, so to anonymise it you can use the guide below: Postgres 1) Take the Postgres dump of your Confluence database: pg_dump -U username confluenceDB > outfile.dump 2) Create a test database: createdb -U username tempDB 3) Load it into a test database: psql -U username tempDB < outfile.dump 4) Run the following query against your test database: update BODYCONTENT set BODY='a'; update CWD_USER set CREDENTIAL='{PKCS5S2}ymGp6ZB7V+CS6xORA4DEDNDnv+RHyLlZl43Rc25gJ+Vw7ZTUGpzxuDhJv7hAgruT'; MySQL 1) Take the mysql dump of your confluence database: mysqldump -u username -ppassword database_name > FILE.sql 2) Load it into a test database mysql -u username -ppassword test_database < FILE.sql 3) Run the following query against your test database: update BODYCONTENT set BODY='a'; update CWD_USER set CREDENTIAL='{PKCS5S2}ymGp6ZB7V+CS6xORA4DEDNDnv+RHyLlZl43Rc25gJ+Vw7ZTUGpzxuDhJv7hAgruT';
Other DatabasesPlease consult your database documentation on how to take database dump and restore. Once a copy database has been created, you can execute the update queries above. |
![]() |
Document generated by Confluence on Sep 19, 2011 02:50 |