Skip to main content Skip to complementary content

Creating a Backup

The UI based backup/restore use cases are typically:

  • For support to reproduce issues as explained in the Help
  • To deliver demos/tutorial
  • To reproduce production in a demo/QA environment (e.g., with a backup without content and harvest in production)
  • To migrate to a new type of database such as PostgreSQL to Oracle.

The rules by which the backup and restore process works are as follows:

  • A repository backup may be performed at the repository root level, or at any repository sub levels. In all cases, the full path of the backup starting level is not recorded within the backup so that it can then be restored at any repository sub-levels later.
  • When restoring a repository backup, some repository objects may already exist and will be reused as is (rather than overwritten) by the content of the backup.
  • Any repository backup may contain repository objects having repository object dependencies, which is generally the case for a Directory, Configuration, Data Mapping, Semantic Mapping or Physical Data Model. Each dependent repository object is saved in the backup with its full path from the root. Therefore, when performing the backup, the start level name must not conflict with any root level object names.


  1. Sign in as a user with at least the A and with Metadata Reader privileges to all the models and configurations contained with the backup scope.
  2. For a complete configuration backup, Go to MANAGE > Configuration and More Actions and select Backup
  3. For any other backup Go to MANAGE > Repository
  4. Select the root object in the Repository Panel which will be backed up. Remember, all contained models and configurations will also be backed up.
  5. Right-click and select More -> Backup .
  6. If the issue is related to users, groups, capability global role assignment or other system configuration settings, be sure to select YES for BACKUP SYSTEM MANAGED OBJECTS like Groups.
Information note

For security reasons, user passwords are reset to their user names.

  1. Be sure to select the check box for BACKUP CACHED MODELS of models Content.
  2. Click on the BACKUP button.
  3. Wait for the operation to finish and open the log for that operation.
  4. Click Download and save to a location.


Sign in as Administrator and go to MANAGE > Configuration .

Click More Actions > Backup in the header of the list of models.

Click BACKUP .

Open the log for the finished operation.

Click Download Operation Files .

It produces a file like:

Explore Further

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!