Copying data from a Crystal Enterprise 10 CMS

You may want to copy repository objects from one Crystal Enterprise 10 installation to another. For example, you may have repository data on a test system that you want to move onto a production server.

Use the Crystal Import Wizard to copy repository data from the source CMS. You can choose to merge the contents of the source repository into the destination repository, or you can update the destination with the contents of the source CMS.

Merging repositories

When you merge the contents of the source repository with the destination repository, you add all repository objects from the source CMS into the destination CMS without overwriting objects in the destination.

This is the safest import option. All of the objects in the destination repository are preserved. Also, at a minimum, all repository objects from the source system with a unique title are copied to the destination repository.

If an object from the source has the same title as an object in the destination, the object is imported to the destination repository if:

• The object is not a Business View.
• You have selected "Automatically rename top-level folders that match top-level folders on the destination system."

The end result is a destination repository that contains all objects from the source repository that have unique titles, copies of all non-Business View objects from the source repository that have titles that match titles of objects in the destination, and all objects originally in the destination repository.

When an object is copied from the source CMS to the destination CMS, the folder or folders that contain the object are also copied, replicating the folder hierarchy of the source system on the destination. However, the names of top-level folders must be unique. Selecting "Automatically rename top-level folders that match top-level folders on the destination system" allows these folders to be renamed on the destination repository, and the objects in such folders to be copied to these renamed folders.

Note:    Top-level folders containing Business Views are not renamed, regardless of the options set. Renaming these folders would change the unique identifier associated with the Business View, causing the Business View functionality to fail.

Updating the destination repository

When you update the contents of the destination repository using the source repository as a reference, you add all objects in the source CMS to the destination CMS. If an object in the source repository has the same unique identifier as an object in the destination, the object in the destination is overwritten.

All object titles in a folder must be unique. By default, if copying an object from the source CMS to the destination CMS would result in more than one object in a folder with the same title, the copy fails.

If you want these objects to be copied, select the check box "Automatically rename objects if an object with that title already exists in the destination folder."

Note:    System Objects (users, user groups, servers, server groups, events, and calendars), are not renamed when you import them from one CMS to another, regardless of the options set. Changing the names of these objects would cause user management, server management, and event management for these objects to fail.

See Importing with the Crystal Import Wizard for full instructions on using the Import Wizard to copy objects from one Crystal Enterprise 10 repository to another.