4.9. Migrating Workspaces

A superuser can dynamically migrate any workspace that is in restricted configuration mode using the EKM Server Administration interface. Workspaces that are in “configuration mode” will be marked with an asterisk (*) in the Workspaces list in the EKM Server Administration window.

Refer to Restricted Configuration for details on how to start a restricted configuration mode and where it is used. Note that only the user who has been designated as the Root User can perform restricted configuration actions.


Important:  Data migration is a potentially risky step that may cause data loss or corruption if it cannot be successfully completed for any reason. Therefore it is highly recommended that you take a complete backup of your EKM data before migrating a workspace that is in production use.


To migrate a workspace that is restricted configuration mode:

  1. Sign in to the EKM Administration Interface as superuser (see Signing In and Out of EKM Server Administration). Select a workspace that is in “configuration mode” and click Migrate Workspace. This opens the Migrate Workspace dialog box.

    Figure 4.5:  Migrate Workspace Dialog Box

    Migrate Workspace Dialog Box

    If the data model has changed as a result of your configuration and data loss may result for the workspace, the dialog box indicates which changes are affected under Type Changes Involving Removal of Metadata or Child Objects. If you click Cancel, no migration will take place. If you click Apply, migration will take place but the workspace will remain in configuration mode. If you click Apply & Accept, the workspace will exit from configuration mode after migration, and other users will be able to sign in to it. When you accept changes, you can optionally add a comment that will be used as the check-in comment for the new version of the /Administration/Configuration folder.

  2. When you click Apply or Apply & Accept in the Migrate Workspace dialog box, migration begins and a Progress dialog box opens and report on the status of the migration (Figure 4.6: Progress Dialog Box During Migration). Depending on the amount of objects in the repository, migration can take from several minutes to a few hours to complete. You can also view a log of the migration as it progresses by clicking the Show Log button or download it using Download Migration Log.

    Figure 4.6:  Progress Dialog Box During Migration

    Progress Dialog Box During Migration

    Once it finishes, the Migration Completed dialog box indicates successful completion, as shown below. You can view the log after download by selecting this option in the EKM Server Administration. The log will be overwritten each time you migrate a workspace configuration.

    Figure 4.7:  Migration Completed Dialog

    Migration Completed Dialog


Note:
  • Workspaces migrated from EKM version 15 or earlier will have automatic account creation turned off by default in EKM version 18.2.

  • In EKM version 17, workspaces are no longer designated as “shared” or “individual”. A user’s privileges in a workspace are determined by the Access level assigned to the user in his or her user profile (Shared, Analyst, or Basic). For more information, see Licensing and Access in the Installation Guide.

    When migrating a repository from version 16 or earlier, users belonging to both shared and individual workspaces in version 16 will be granted Shared access in version 17. If you do not want certain users to have Shared access, you must change their Access level to Analyst in their user profile. See Editing a User’s Profile.

  • When viewing the migration log, you may see the message DEBUG - Removing Property: fullControl if you are migrating a version 16 repository to version 17. This has no implications for the migrated workspace, and can be ignored.



Release 18.2 - © ANSYS, Inc. All rights reserved.