Home Search

DriveWorks Pro 22
How To: Move a Shared Group (KB13010805)

Send Feedback

Introduction

This document provides information on moving a Shared Group and all of the associated data belonging to any project within the group.

It is highly recommended that a backup be taken of any data that is being moved, so that it can be restored to its original location in the event of any issues that could occur while data is being moved.

Overview

The process of moving data will generally resemble the following:

  1. Backup the shared group to be moved and move the backup file to a location that can be accessed from the new location.
  2. Restore the shared group to its new location.
  3. Reconnect all DriveWorks applications to the moved shared group.
  4. Update the DriveWorks Project Data within the group.

The article How To: Deploy DriveWorks Pro provides information on where each DriveWorks application should be installed.

DriveWorks Pro Server should be installed on the machine where the shared group is to be moved to.

Please refer to the Pro Server Configuration topic for information on installing and using Pro Server.

SQL Server Management Studio is required for backing up and restoring SQL databases.

Backup the existing Shared Group

When moving a DriveWorks shared group it is essential a backup is taken.

This backup set creates a physical file that can be moved using Windows Explorer, but also provides a restore point should anything go wrong.

See How To: Backup a SQL Server Database for more information.

Once the backup set has been created the BAK file should be moved to a location that can be accessed from the new machine, using Windows Explorer.

Restore the backed up shared group on the new SQL Server

Follow the steps outlined in the article How To: Restore a SQL Server Database.

Connect DriveWorks Pro Server

Follow the steps below to connect DriveWorks Pro Server to the restored database:

  1. Configure DriveWorks Pro Server to connect to the SQL Server instance.

    See DriveWorks Pro Server Configuration - Connect to a SQL Server for more information.

  2. Ensure the DriveWorks Pro Server service is running.

    See DriveWorks Pro Server Configuration - Pro Server for more information.

Force Ownership of the Restored Database

The restored database may also require upgrading and/or owning by the DriveWorks Pro Server it is hosted on.

  1. Ensure the restored database is displayed in the Groups list.

    See DriveWorks Pro Server - Groups for more information.

  2. Select the Group, from the Groups list, and ensure the version and ownership match the DriveWorks Pro Server it is being hosted on.

    If the Group requires upgrading and/or owning an appropriate button will be displayed.

    See DriveWorks Pro Server - Upgrade, Force Ownership or Force Ownership and Upgrade for more information.

Update the DriveWorks Project Data

If the shared group has been moved from a local server onto a network server the project data will require to be updated.

For information on updating the references to the DriveWorks Project Data please see Data Management.

If the DriveWorks Project Data is also required to be moved please see the article How To: Move DriveWorks Data.

Update Recent Group List in the DriveWorks Applications

When the SQL Server has been moved the Group button and the Recent Group list on the DriveWorks Today home screen will require updating.

To update the Group Button follow the steps below:

  1. Open DriveWorks Pro Administrator.
  2. Click the Group Button
  3. From the Open\ Create Group wizard select Open an existing Group. Click Next.
  4. Select Shared Group. Click Next.
  5. Select the Server that holds the moved shared group. Select the Group on the Server to connect to and click Finish.

The Recent Group list on the DriveWorks Today home screen will automatically update on completion of the above steps.


Knowledge Base Article Ref:KB13010805