Data Store Migration Strategies

Migrating Server Farms and the Data Store

Use the Dsmaint command to migrate a Presentation Server farm to a different type of data store. For example; from Access to Microsoft SQL Server or from Microsoft SQL Server to Oracle.

Migration Between Different Database Versions

Refer to the appropriate Presentation Server Administrator Guide.

Refer to the following articles for more information on migrating from one database platform to another:

In CTX112223 – Citrix Presentation Server 4.5 Administrator's Guide:

• Migrating to SQL Server on page 410

• Migrating to Oracle on page 413

• Migrating to IBM DB2 on page 417

In CTX106319 – MetaFrame Presentation Server 4.0 Administrator's Guide:

• Migrating to SQL Server on page 58

• Migrating to Oracle on page 61

• Migrating to IBM DB2 on page 66

The dsmaint command can migrate farm data between databases (dsmaint migrate) and reconfigure servers to use the new database (dsmaint config).

The following examples show the syntax for the dsmaint migrate and dsmaint config commands:
Note: Type the respective command as one continuous string at a command prompt.

dsmaint migrate /srcdsn:dsnfile /srcuser:user /srcpwd:password /dstdsn:dsnfile /dstuser:user /dstpwd:password

dsmaint config /user:username /pwd:password /dsn:dsnfilename

Where:
dsnfilename is the DSN file for the database, including the full path. Refer to CTX108699 - Error: Failed to connect to the data store....during DSMAINT CONFIG for more information.

username is the user name for the database.
password is the password for the database.

Migration can be performed with users logged on to the farm. Stopping and restarting the IMA Service does not affect currently connected sessions. However, no new connections are allowed until the IMA Service is completely restarted.

Important: Restarting the IMA Service on more than 10 servers simultaneously can cause the database server to become a bottleneck, resulting in startup delays.

Migrating from Access to Microsoft SQL Server or Oracle

Note: Migration from an Access indirect database to a Microsoft SQL Server 2000 direct database using the dsmaint migrate command is supported only with MDAC 2.5.

To migrate from Access to Microsoft SQL Server or Oracle, complete the following steps:

Create a new database on Oracle or Microsoft SQL server.
Create a new Mf20.dsn file pointing to the new database created in Step 1. By default, the DSN file is located in the following directory: <ProgramFiles>\Citrix\Independent Management Architecture
On the host server, run the dsmaint migrate command, entering the current DSN file as the source and the new DSN file created in Step 2 as the destination. If the password for the old database is not changed, the default user name/password is citrix/citrix.
Tip: Enter the complete path of the DSN file (inside quotation marks if the path contains spaces) when required as a parameter for the dsmaint migrate command.
Run the dsmaint config command on the original host server to point to the new DSN file.
Stop and restart the IMA Service on the host server. When the IMA Service on the host server is restarted, the remaining indirect servers begin accessing the new data store indirectly through the host server.

Important: Restarting the IMA Service instead of restarting the server might cause the SNMP service to Dr. Watson if SNMP is enabled. This error is benign.
Copy the DSN file created in Step 2 to all remaining indirect servers in the farm.
Execute dsmaint config on all remaining indirect servers to establish a direct connection to the new database through the DSN copied in Step 6.
Stop and restart the IMA Service on all remaining indirect servers in the farm.
Tip: You can complete Steps 6 through 8 on all the servers by using a simple batch file placed in a central location. For information about data store migration, refer to DSMAINT on page 368 in CTX106319 – MetaFrame Presentation Server 4.0 Administrator's Guide.

Migrating from Microsoft SQL Server or Oracle to the Other

This section contains information about migrating data store information between different versions of Microsoft SQL Server and Oracle.

To migrate the database, complete the following steps. For the best performance, complete this procedure on the data collectors after all other servers are reconfigured.

Create a new database on the destination server (Oracle or Microsoft SQL Server).
Create a new DSN file that points to the new database.
Run the dsmaint migrate command on the server with the new DSN file.
Run the dsmaint config command on the server.
Stop and restart the IMA Service on the server.

Important: Restarting the IMA Service instead of restarting the server might cause the SNMP service to initiate Dr. Watson if SNMP is enabled. This error is benign.
Ensure that the server is using the correct DSN by checking the following registry settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\DatabaseDriver
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\DataSourceName
If the IMA Service started successfully, copy the new DSN file from to all servers in the farm.
Run the dsmaint config command to change the IMA Service configuration on all servers in the farm.
Stop and restart the IMA Service on all servers in the farm.
Tip: You can run Steps 7 through 9 on all the servers by using a simple batch file placed in a central location.

Migrating the Database to the Same Version such as SQL 2005 to SQL 2008

Migrating from one database version to the other might be necessary to move the data store to a more powerful server. The best method for migrating between versions of the database is to back up and restore the database using the utilities provided by the database software vendor.

To point a Presentation Server farm to a new database complete the following steps. For the best performance, complete this procedure on the data collectors after all other servers are reconfigured.

Back up the existing farm database and restore the database to the new server.
Create a new DSN file that points to the restored database.
Run the dsmaint config command on the server with the new DSN file.
Stop and restart the IMA Service.

Important: Restarting the IMA Service instead of restarting the server might cause the SNMP service to initiate Dr. Watson if SNMP is enabled. This error is benign.
Ensure that the server is pointing to the new data store by checking the following registry setting:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\DataSourceName
If the IMA Service started successfully, copy the new DSN file to all servers in the farm.
Run the dsmaint config command to change the IMA Service configuration on all remaining servers in the farm.
Stop and restart the IMA Service on all servers in the farm.
Tip: You can execute Steps 6 through 8 on all the servers from a simple batch file placed in a central location.

Migrating to Access

Migration from Microsoft SQL Server or Oracle to Access is not supported.