Repository Logical Backup
Before you make a repository backup, dispatch all current private workspaces so that their changes are included in the backup. To view private workspaces active on your repository, use the private workspaces administration tool, see "Workspace Administration.
Logical backup:
• creates a command file that allows you to reconstruct the repository by update of an empty repository.
• analyzes all repository content.
• is safer than a physical backup since it checks that all data in the repository is readable.
• can be used as a long term archive or to merge repositories.
You can execute updates on the repository after starting logical backup by dispatching a private workspace. However, note that these modifications are not included in the backup.
You can temporarily prohibit users from updating the repository by clearing the Authorize Dispatch option in the environment or user options.To perform a logical backup of a repository:
1. Connect to HOPEX Administration and select the repository concerned.
2. Right-click the repository concerned and select Logical Backup.
The Repository Logical Backup dialog box opens.
3. In the Destination pane, select the export format of the backup file:
• text format (*.MGR).
For more details on .MGR file syntax, see Command File Syntax.• MEGA XML format (*.XMG)
This format is reserved for exchange of data between HOPEX and other applications. It includes commands or data (objects and links).
This format cannot be used to extract the metamodel or technical data.
This format is reserved for exchange of data between HOPEX and other applications. It includes commands or data (objects and links).
This format cannot be used to extract the metamodel or technical data.
For more details on MEGA XML data exchange format, see technical article MEGA Data Exchange XML Format EN.
Environment options enabling configuration of HOPEX data export (XMG encoding, default export format, etc.). See Managing Options.4. (Optional) In the Destination pane, click Browse 
to browse the folder tree and modify the name and/or location of the backup file.
to browse the folder tree and modify the name and/or location of the backup file.By default, the backup creates a file "RepositoryName.mgr" in the WORK work folder.
We recommend that this backup be made to a physical device other than the device on which the repository is located. Selection of a different logical device, such as a different partition on the same disk, does not protect your backup in the event of disk failure.5. Select the type of data you want to save.
The Extensions buttons correspond to data created by users.Carry out a complete backup only if technical support asks you to do so.You can choose what you want to save: extensions common to environment repositories and data specific to current repository. It is recommended that you save all these elements in separate specific files, with names indicating their contents.For a standard logical backup, simply select the Data and its Extensions.In the Data common to environment repositories pane, select the data type of the system repository to be saved:
• Technical Data allows extraction of data such as descriptors, queries, and report templates (MS Word).
A complete logical backup of the repository including the Technical Data can take time and occupies considerable space.• Profiles and Business roles allows extraction of created profiles and business roles (those not provided by MEGA).
• Writing access areas, reading access areas and LDAP allows extraction of created writing and reading access areas (those not provided by MEGA) and LDAP parameters (parameters, servers, groups).
• Users allows extraction of created users (persons, person groups, logins).
• Workflow statuses enables extraction of workflows (workflow instances, transitions and statuses, tasks, validations, requests for change).
In the Data specific to current repository pane:
• Data allows extraction of repository data. This data includes assignment of business roles to persons.
• Log objects allows you to include object histories in the extraction of HOPEX data.
For more information on object logs, see Viewing Object History.• Objects of merging allows you to export technical objects resulting from merging objects (_TransferredObject).
For further information on merging objects, see Merging Two Objects.6. (If needed) In the File password protection pane, select Password protect the generated file.
The password is asked at file import.7. Click Backup to start backup.
During execution of backup, a series of messages keeps you informed of progress.
The backup report is displayed in the Report area.
For more information on this file, see Viewing the Environment Report File.To update a repository, import the repository backup file.
For more details on importing a command file, see Updating a Repository.Deleting an RDBMS Repository
To delete an RDBMS (SQL Server or Oracle) format repository, you need the appropriate administration rights.
• Oracle: you need at least an account equivalent to “system” to delete a schema.
• SQL Server: you need at least db_creator rights.
To delete an RDBMS repository:
1. Connect to HOPEX Administration and unreference the repository concerned.
2. Ask the database administrator to delete the database or schema concerned from the RDBMS server.
Duplicating an Oracle repository
For detailed information on duplicating an environment and an RDBMS repository, see the RDBMS Environment Duplication technical article. See also deployment documentation: RDBMS Repository Installation Guide.Prerequisite: before duplicating a repository, check that there is no other active or passive private workspace on this repository, see "Workspace Administration.
To duplicate an Oracle repository:
1. Connect to HOPEX Administration and select the Oracle repository concerned.
2. Right-click the RDBMS repository concerned and select RDBMS Administration > Duplicate Oracle Storage.
The Duplicate a Repository dialog box appears.
The name of the Source repository is indicated.
3. (Optional) In the Name field of the Target pane, modify the name of the repository to be created.
4. (Optional) Click Browse to select the location where the repository will be created.
5. (Optional) In the Schema field, modify the schema.
The source schema is used by default. You should use a different schema for a different repository. 6. (Optional, if you have kept the name of the source schema) In the Prefix to be used field, enter a prefix to distinguish the source schema from the target schema.
The prefix must start with an alphabetic character.7. Click OK.
8. In the connection window, enter the password to access Oracle.
9. Click Test connection.
You must validate the test before continuing the procedure.
10. Click Test GRANTs.
You must validate the test before continuing the procedure.
11. Click OK.
The repository is duplicated.