- Deactivate project in old environment from the Site Administration page
2.
Verify, Repair if needed and Verify Project again from the Site Administration page
3.
Remote into new server where projects will migrate to. mstsc the "//ipaddress e$" of old server then select the drive and repository location. You can then set a drive on the new server to link to the old server location. Copy file repository dir from old to new environment repository in final location via robocopy (robocopy Z:\WORKFORCE\OFC E:\repository\qc\WORK\OFC /s /e /dcopy:t /mt:64 /r:100 /w:5 /v /tee /log:robo.log)
4.
DBA - detach db on old environment, dropping fulltext catalog (this alters the SOURCE system however)
5.
DBA - copy db from old environment to new db (optionally, reattach db on old environment)
6.
DBA - attach db on new db server (new environment)
7.
DBA - on new db in sql run "alter user td with login = td" <------------ this was the SQL error cause, a broken user link
8.
Edit dbid.xml frmo each repository RoboCopied with new file location on new server in text in bold pink below. Best to open other dbid on new server and make changes based on its password, database, port and repository location.
9.
<?xml version="1.0" encoding="UTF-8"?> <ProjectDescription> <PROJECT_NAME>OJIxx</PROJECT_NAME> <DB_TYPE>2</DB_TYPE> <DESCRIPTION>Created on 2011-12-20 16:35:04</DESCRIPTION> <DB_CONNSTR_FORMAT>jdbc:mercury:sqlserver://MSAIRxxxxxxx1D:port#</DB_CONNSTR_FORMAT> <DB_NATIVE_AUTHENTICATION>N</DB_NATIVE_AUTHENTICATION> <DB_NAME>migration_nov_oji_db</DB_NAME> <DBSERVER_NAME>MSAxxxxxxx01D</DBSERVER_NAME> <DB_USER_PASS>QCCxxxxxxxxxxxxxxy+Fw==</DB_USER_PASS><PR_HAS_VCSDB>N</PR_HAS_VCSDB> <PHYSICAL_DIRECTORY>E:\repository\qc\UNEMPL\OJI\</PHYSICAL_DIRECTORY> <USERS_QUOTA>-1</USERS_QUOTA> <PR_IS_ACTIVE>Y</PR_IS_ACTIVE> <SAQ_IS_ACTIVE>Y</SAQ_IS_ACTIVE> <VM_REPOSITORY></VM_REPOSITORY> <PR_LANGUAGE>English</PR_LANGUAGE> <PROJECT_TYPE>Standard</PROJECT_TYPE> <IS_TEMPLATE>N</IS_TEMPLATE> <PROJECT_UID>caa4xxx9-e9eb-4366-a320-ddxxxx32edc46</PROJECT_UID> <PR_SMART_REPOSITORY_ENABLED>Y</PR_SMART_REPOSITORY_ENABLED> <PR_IS_QPM_AUTO_CALC_ENABLED>Y</PR_IS_QPM_AUTO_CALC_ENABLED> </ProjectDescription>
10.
Restore project in new Site Administrator from the project domain by selecting the new dbid file. It can error if the dbid is wrong or if the dba did not run the "alter user td with login = td" command above.
11.
DBA - Rebuild fulltext (in both old and new environment if needed)
12.
Test that new environment works ok.
13.
Activate in old environment and put old environment in Read Only if necessary so they can check the migration was successful
14.
Make sure project has "Automatic Email" checked in the project tab
15.
Email users of the changes