Restore model as copy - Intergraph Smart 3D - Administration & Configuration - Hexagon PPM

Intergraph Smart 3D Global Workshare (SQL Server)

Language
English
Product
Intergraph Smart 3D
Subproduct
Global Workshare
Search by Category
Administration & Configuration
Smart 3D Version
13.1

Use the workflow outlined below when the Host server in a Global Workshare Configuration (GWC) is "lost" and can no longer participate in the GWC. This workflow requires you to use a backup of the Host databases that was completed while the GWC was in-place.

As part of the restore process for the model, the software performs the consolidation process. This is the same series of actions that you perform manually during the standard consolidation workflow; however, in this workflow, the software performs them automatically.

The databases that result from this workflow will behave as they would in a standard, non-workshare setup, and all permission groups are reset to the new Host location. The restored dataset is fully supported for future replication.

  • Do not substitute the workflow in this scenario for the standard consolidation workflow as queued or error data will be lost.

  • Do not deviate from the following sequence of steps. Additionally, do not proceed to a subsequent step in the workflow until the previous one is complete.

  1. Use the Database Wizard to create a new, empty site and site schema database on the Host server. Because you will be restoring the original catalog and catalog schema databases in a later step, create these new site databases using an existing catalog. Depending on the type of databases you are using, see Create a new site database for SQL or see Create a new site database for Oracle in the Project Management Help.

    The names of the new site and site schema databases are not required to be the same as in the backup set from the Host.

  2. Use the Restore Wizard in Project Management to restore the catalog, catalog schema, and model databases on the Host server from the backup that was completed prior to the work stoppage. See Restore a model as a copy.

    When the restore is complete, review the consolidate .LOG file in the %temp% folder of the logged-in user who ran the restore.

  3. Regenerate the reports database after the project databases are restored on the Host server.

  • The workflow outlined in this scenario can also be used to test the consolidation of the databases in order to pre-screen for possible errors without affecting the live dataset. Such pre-screening is useful in preparation of migrating data or for ensuring minimal downtime during consolidation. In instances where pre-screening is the objective, you must perform the workflow on a server that is independent of any of the servers participating in the live GWC.

  • You can also implement this workflow for the purposes of conducting a design review. The databases participating in the live GWC can remain intact and operable, while the latest work from the backup set can be restored onto a laptop and presented in the design review.