1876557 - How to use Copy Data from another Data Source in Crystal Server 2008 Environment

This article can be applied to the following scenarios:

• You have a production CR Server 2008 environment and you want to create a User Acceptance Testing (UAT) environment using the production CMS database
• If your existing CMS database is corrupted, you can copy data from another existing environment's CMS database

Disclaimer: Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

In this article, we refer to production environment as "Source", UAT environment as "Destination".

Production Environment:

• Single Server
• Crystal Server 2008 V1 SP3
• Operating System: Windows 2008 R2 32bit
• CMS Database: Oracle 10g (on an external server)
• Auditing Database: Oracle 10g (on an external server)
• Oracle 10g Client
• Application Server: Tomcat 5.5

UAT Environment:

• Single Server
• Crystal Server 2008 V1 SP3
• Operating System: Windows 2008 R2 32bit
• Current CMS Database: MySQL (on local server)
• Auditing Database: MySQL (on local server)
• Target CMS Database: Oracle 11g (on an external server)
• Target Auditing Database: Oracle 11g (on an external server)
• Oracle 11g Client
• Application Server: Tomcat 5.5

Step 1: Preparation:

1. In CCM, Stop SIA on both source and destination
2. Take a cold back up of source and destination CMS database and filestore

Step 2: Cloning;

On destination server:

1. open Central Configuration Manager (CCM), right click on SIA, then Properties, then Configuration tab, click on Specify next to CMS System Database Configuration
   
2. Choose the Copy Data from Another Data Source option
   
3. In Specify Data Source dialog, do the following
1. in Get Data From section, specify a connection to your source CMS database (in this case the Oracle 10g db)
2. then in "Copy to the following data source" section, specify a connection to your destination CMS database (in this case the Oracle 11g db). Make sure the user's schema is completely empty on the destination database. Grant sufficient privileges to this database user (in terms of Oracle, grant "Connect" and "Resource" role and "Create Table" privilege).
   
4. Click OK, CCM will then prompt you that the operation will delete all tables in the destination database, click Yes to continue
5. The data copy will begin, when it's completed, a dialog pops up saying "CMS Database Setup Completed"
   
6. At this point, DO NOT START SIA yet

Step 3: Change Configuration:

1. On the destination server, in CCM, go to SIA properties and Configuration tab, you'll notice that the CMS data source is now pointing to the new one, also the cluster name will be same as the source. Therefore, you'll need to check Change Cluster Name to and specify a new cluster name, it should be the same as what you had on the destination before the data copy.
   
2. Apply the change and then click OK.
3. At this point, DO NOT START SIA yet.

Step 4: Re-creating SIA on destination:

1. On destination server, in CCM, click on Add Server Intelligence Agent button
   
2. In Add SIA wizard, specify the following:
1. Name: same name as the destination SIA name before data copy
2. Port: same as before
3. Choose Create default servers on the new node
4. Check Recreate SIA... option
   
3. Click Next, then Next again in the Warning screen,  then specify the following:
1. New CMS Port: same as before
2. CMS System Database Data Source Name: your newly copied data source (in this case the Oracle 11g db)
3. Check whether or not you need a new Auditing data source
   
4. Click Next to go to CMS Logon Screen. Note that at this point you should use the admin password on your source because your destination database now contains user information of the source
   
5. Click Next then click Finish. The add SIA operation will take a while to complete.
6. At this point, DO NOT START SIA yet

Step 5: Copy Filestore:

1. By default, the filestore location is <drive_letter>:\Program Files\Business Objects\BusinessObjects Enterprise 12\FileStore
2. On the destination, rename Input and Output folder to Input_old and Output_old
3. Copy the source Input and Ouput directory over to the destination

Step 6: Start SIA:

1. Now you can start SIA in CCM.
2. In CCM, click Manage Servers button and login to CMS, you'll notice that there are 2 sets of default servers. One set is prefixed with the source's cluster name and all the serves should be stopped and disabled. The running and enabled ones are the new servers on destination host.
   

Step 7: Update Objects:

1. Once all the servers are started, you should go to CCM and click on Update Objects button, login to CMS and it'll update all the objects according to the new copied filestore.

Step 8: Cleanup:

1. On destination, you can now login to CMS. Go to Servers and delete all the servers that are prefixed with the source cluster name.

Important:

1. Ensure that the source SIA is stopped at all times

1649772 - How to recreate SIA after computer name of BI 4.0 server is changed on WIndows Server 2003?

crystal server 2008 v1 sp3 businessobjects XI 3.1 clone copy replication duplicate backup back up mirror database cms windows oracle mysql production user acceptance testing UAT environment , KBA , BI-BIP-SRV , CMS / Auditing issues (excl. 3rd Party Authentication) , How To