[THIN] Re: Migrate SQL Datastore to another SQL Server

  • From: "Andrew Wood" <andrew.wood@xxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 7 Jan 2009 12:04:24 -0000



The dsn file can be very simple :






APP=Citrix IMA

SERVER=(SQL instance)


will work - so the dsn file can be the same for each server


What you can do is copy a script to each server that copies the dsn from a
central location, executes the dsmaint command and restarts the IMA service;
optionally you can get it to dump the reg key and compare 


I'd start with your test servers, and once you're happy go on to the farm
starting at the zdcs... in the past I've used psexec with a file containing
the servers to change to run the script.


For the summary database connection server - 


1.       Sleep  the summary service

2.       Backup/restore the summary database 

3.       Test connection to the new database

4.       Reconfigure the odbc connection on the connection server & test it

5.       Wake the summary service 

6.       Do an update


Don't forget to keep the old dsns and have a rollback plan just in case.




From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Angela Smith
Sent: 07 January 2009 11:23
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Migrate SQL Datastore to another SQL Server



I will be migrating my CPS 4 farm SQL DB to another SQL Server.  SQL
versions are not changing.  Im simply moving the DB from a single SQL Server
to a SQL cluster.  Ive never moved a Datastore so I was hoping someone could
validate these steps for me.

1. Back up the existing farm database and restore the database to the new
SQL Cluster.

2. From a Citrix Server, create a new DSN file that points to the database
restored in Step 1

3. Execute the dsmaint config command on the server with the new DSN file.

dsmaint config /user:domain\userid /pwd:password /dsn:"c:\program
files\citrix\independent management architecture\mf20.dsn"

4. Stop and restart the IMA Service.

5. Verify that the server is using the correct DSN by checking at the
following registry setting:


6. If the IMA Service started successfully, copy the DSN file created in
Step 2 to all servers in the farm.

7. Execute the dsmaint config command to change the IMA service
configuration on all servers in the farm.

8. Stop and restart the IMA service on all servers in the farm. 

9.  Create new Published Application.  Ensure DB is working correctly.

In relation to the steps above, I have a few questions:

1) Is there a Preferred server order I should follow?  Should the Zone Data
Collector be done last?
2) If I copy the DSN to all servers, wont the DSN be wrong on all servers as
the information within the file will be specific to the first server it was
copied from.  IE WSID field
3) The Server in question which I am migrating off also holds the
RMSummaryDB.  Whats the best way to migrate this?



Download free Holiday emoticons today! Messenger's
<http://livelife.ninemsn.com.au/article.aspx?id=669758%20>  gift to you!

Other related posts: