Backup and Support Considerations
Last updated: 8/31/2026Overview
When reporting an issue, it may be necessary to provide a database backup. You may use the following queries to remove sensitive information before creating and sending the backup.
Never perform these queries on your actual database. Executing these queries will make the database unusable and unrecoverable, and are only intended to help you to report an issue to support. You should
- Stop the app server and database server.
- Create a database backup using database utilities.
- Restore the result into a new database using database utilities.
- Then, you may run the below queries, backup again and send the resultant backup to support.
- SQL query to remove bridge parameters:
UPDATE mir_meta_attribute SET val='' WHERE model_id=-1 AND attribute_definition_id=525;
- SQL query to clear user passwords:
UPDATE mir_meta_attribute SET val='' WHERE model_id=-1 AND attribute_definition_id=265;
- SQL query to clear server passwords (email, JIRA, Teams, …):
UPDATE mir_meta_attribute SET val='' WHERE model_id=-1 AND attribute_definition_id=511;
- SQL query to clear the server configurations (cloud identity, authentication, …):
UPDATE mir_meta_attribute SET val='' WHERE model_id=-1 AND attribute_definition_id=514;
- SQL query to clear the data sampling information (this make take a long time):
UPDATE attribute SET val='' WHERE system_type=19;
UPDATE content_attribute SET val='' WHERE system_type=19;
- SQL query to clear the data profiling information (this make take a long time):
UPDATE attribute SET val='' WHERE system_type=18;
UPDATE content_attribute SET val='' WHERE system_type=18;