Restore Branch Archive
Start Menu Path: Project Explorer Menu / Configuration Mgt / Restore Branch Archive
Function:
- The "Restore Branch Archive" script reconnects an archive of branched projects/modules modified offsite back to the branch it was generated from.
Instructions:
- "Onsite" – Archive a Branched Project
- Highlight a branch project, i.e. the modules in the project were created through branching.
- Choose the explorer menu option File > Archive.

- Browse to a location and file name to save the resulting archive file.
- To keep the resulting archive file small, in the GUI choose "do not archive any baselines".
- Press "OK" in the GUI.
- Send the resulting archive file offsite.
- "Offsite" – Restore, Modify, and Archive Received Project
- Choose the explorer menu option File > Restore > Project.

- Browse to the received archive file.
- Enter a new name for the project.
- Press "OK".
- Offsite users can now work in this project modifying its modules (see Restrictions).
- When the project is ready to be sent back, follow the previous "Onsite" instructions for archiving.
- "Onsite" – Use "Restore Branch Archive" Script
- Choose the explorer menu option Configuration Mgt > Restore Branch Archive.

- Browse to the archive file received from offsite.
- Choose a location to restore the project.
- Enter a new name for the restored project (or use the generated one). Verify the name is not already in use with the "Verify" button.
- Press the "Restore" button.
- Open in edit a module in the original branched project (that was archived to start this process).
- Start an integration with the module menu option Configuration Mgt > Integration.
- Select the project created by the "Restore Branch Archive".
- Select the integration options.
- In the integration GUI, you will see the list of changes.
Restriction 1: Only those link pairings that are possible are included in the archived modules.
- If a pairing target module is not included in the archive, that link pairing and its links are removed.
- If a pairing link module is not included in the archive, that link pairing and its links are removed.
- If a pairing target and link module are included in then archive, that link pairing and its links are included. Thus the offsite users can create new links and delete existing links.
- These restrictions are a product of the DOORS archive facility, not BranchManager.
Restriction 2: While offsite, the projects/modules cannot be branched or merged using BranchManager,
nor can their BranchManager attributes be modified. Ignoring this restriction may result in the "Restore Branch Archive"
script being unable to reconnect the archive to the branch it was generated from.