See if this helps you:
CRM Moving Documents
Issue
How can I move the Microsoft CRM SQL Server databases to a different machine
within the same domain.
Resolution
This process is intended for use in a scenario where a user is required to
move the Microsoft CRM SQL Server databases to a different/new server within
the same domain.
Note This process should not be used to move data from one server to another
across domains, nor should it be used when moving from a named Microsoft SQL
server instance to a default instance on the same server.
Before completing this process please read the entire document completely.
Prerequisites to verify before completing this process include:
1. Have all users log out of Microsoft CRM.
2. Ensure that all Microsoft CRM Sales for Outlook Clients have
synchronized all of their offline data to Microsoft CRM by going on-line.
Un-install all Microsoft CRM Sales for Outlook clients in the deployment.
3. This process should be performed by the same domain administrator
account that installed Microsoft CRM.
4. Make sure you make a copy of all reports you have customized or
modified, these reports will need to be re-published.
5. Ensure that you have a current backup of your Active Directory system
state and all the Microsoft SQL Server databases.
Moving the Databases:
1. Make a Microsoft SQL Server backup of each of the 3 primary Microsoft
CRM databases. It is not necessary to back up the MSCRMDistribution
Database. This will be re-created on your new Microsoft SQL server manually.
The three databases are as follows:
- <OrganizationName>_CRMCRYSTAL
- <OrganizationName >_METABASE
- <OrganizationName >_MSCRM
To complete these backups:
a. Open Microsoft SQL Server Enterprise Manager (Start | Programs |
Microsoft SQL Server).
b. Expand your Server until you see the databases.
c. Right Click on your database and choose: All Tasks | Backup
Database.
d. Leave the backup type set to "Database - complete".
e. In the destination field click "Add".
f. In the "Select Backup Destination" Window click the ellipsis box.
(...)
g. In the "Backup Device Location" Window set a file name and location
for the backup file. Click OK.
h. Click OK until all windows are closed and you receive a message that
the backup has completed successfully.
i. Repeat steps A-H for all three databases you are backing up.
j. Please do NOT delete anything off of this Microsoft SQL server at
this point, as the original setup will be needed for reference during this
process.
2. Transfer the backup files made in step 1 to your new Microsoft SQL
server.
3. After transferring the backup files, please create the three new
databases that you will restore the backups into. To do so, follow these
steps:
a. Open Microsoft SQL Server Enterprise Manager.
b. Expand your server until you have opened the Databases directory.
c. Right click on the Databases Directory and choose: New Database.
d. Enter a name for your database, <OrganizationName>_CRMCRYSTAL. It
is very important to make sure the naming syntax used is exactly as it
appears on your original SQL Server.
e. Repeat steps C and D two more times, creating your
<OrganizationName>_METABASE and <OrganizationName>_MSCRM databases. Again,
ensure the naming syntax exactly matches the databases on your original SQL
Server.
4. Once the databases have been created the backup files will need to be
restored.
a. Open Microsoft SQL Server Enterprise Manager.
b. Expand your server until you have opened the Databases directory.
c. Right click on your _Crystal database.
d. Choose: All Tasks | Restore Database.
e. In the "Restore Database" window select to restore from Device.
f. Click the "Select Devices" button.
g. In the "Choose Restore Devices" window click add.
h. In the "Choose Restore Destination" window click the ellipsis box
(...).
i. Select the location for the backup file for the _Crystal database
and click OK.
j. Click OK in the "Choose Restore Devices" window.
k. In the "Restore Database" window click the Options Tab.
l. On the options tab choose "Force Restore over Existing Database.
m. In the "Restore Database File As:" section of the window you should
see two paths for the physical database files. Ensure that these paths are
valid locations. If they are not, modify them as necessary.
n. Click OK in the "Restore database" window. This will begin the
restore process. Depending on the size of your database, this may take some
time. When it is finished you should receive a message that the restore
completed successfully.
o. Repeat these steps for your <OrganizationName>_METABASE and
<OrganizationName>_MSCRM databases.
5. After successfully restoring the databases, you will need to set up the
security groups by mapping to the NT security groups.
Note For this step it will be beneficial to view the security folder on the
original Microsoft SQL server for reference.
a. Open Microsoft SQL Server Enterprise Manager.
b. Expand your server until you have opened the Security Folder.
c. Right click on the Logins icon and choose New Login.
d. In the "SQL Server Login Properties - New Login" leave the
authentication set to Windows Authentication.
e. In the Domain field, choose your domain.
f. In the Name field you should see "<Yourdomain>\".
g. Click the ellipsis box for the Name field. You will be prompted
with a list of your domain users and groups.
h. Find the SQLRepl group and select it. Click ok after it has been
selected.
i. Click OK to close all the property Windows. When you close the last
window you may be prompted with a message "It has been detected that this
login has permissions in the specific database(s) - the login will have
access to these database now." This is a normal message, simply close it.
j. Repeat steps C through I this time choosing the SQLAccessGroup in
step H.
6. Once the security groups have been set, the new system will need to be
prepared for replication.
Replication is the process that the Microsoft CRM Sales for Outlook clients
will use to go offline. It is not recommended to skip this step, even if
you do not currently use Microsoft CRM Sales for Outlook.
a. Open Microsoft SQL Server Enterprise Manager.
b. Open the Management Folder in Enterprise Manager.
c. Ensure that the Microsoft SQL Server Agent is running. If it is
not, start it by right clicking on it and choosing Start.
d. Go to Start | Programs | Microsoft SQL Server | Query Analyzer.
e. In the Connect to SQL Server dialog box, connect to your Microsoft
SQL Server. Make sure to log in as a Microsoft SQL Server Admin user.
f. On the toolbar, from the drop-down list, select the database
<OrganizationName>_MSCRM.
g. Run the following command:
EXEC p_CRMReplicationSetup <SQL Server name>, <SQL Server name>,
<'Microsoft CRM database name'>, <'Metabase database name'>, <'replication
SQL Server directory'>, <'SQL login group name'>, <'MSCRMDistribution
database name'>
Where:
<Microsoft CRM_Database name> = This is the database that has a name in
the format <OrganizationName>_MSCRM.
<Metabase database name> = This is the database that has a name in the
format <OrganizationName>_METABASE.
<replication SQL Server directory> = This is the path to the REPLDATA
directory on the Microsoft SQL Server, for example: C:\Program
Files\Microsoft SQL Server\MSSQL\REPLDATA. <SQL login group name> = This is
the name located in the Logins node under Security. It is in the format
<domainname>\SQLRepl {E5334FB9-440A-4BD8-A19A-0FA54E6B248C}. For more
information about how to find this name, see the following Note.
<MSCRMDistribution database name> = This is the database that has a name
in the format <OrganizationName>_MSCRMDistribution. If you do not see this
database in Microsoft SQL Server, specify the database name as listed above,
in the parameter and the database will be created.
NOTE - To find the SQL login group name do the following:
a. On the Start menu, point to Programs, point to Microsoft SQL Server, and
click Enterprise Manager.
b. In the console tree, expand the Security node of the server for
which you want to determine the group name (the one you specified during
setup).
c. Click Logins to view a list of login names.
d. In the details pane, right-click the login name that is in the
format <domain name>\SQLRepl {E5334FB9-440A-4BD8-A19A-0FA54E6B248C}, and
click Properties.
e. In the Properties dialog box, click the Database Access tab.
f. On the Database Access tab, the SQL login group name is the name
located in the User column for one of the populated rows. (Any one of the
names listed in this column will work.)
g. Right-click the name and click Copy. Paste the name from the User
column into the <SQL login group name) parameter in the command listed.
Example:
For an organization created with the name MyOrganization, with users in the
domain MyDomain, installed to a Microsoft SQL Server called MySQLSvr, you
would use code similar to the following:
EXEC p_CRMReplicationSetup MySQLSvr, MySQLSvr, 'MyOrganization_MSCRM',
'MyOrganization_METABASE', 'C:\Program Files\Microsoft SQL
Server\MSSQL\REPLDATA', 'MyDomain\SQLRepl
{E5334FB9-440A-4BD8-A19A-0FA54E6B248C}', 'MyOrganization_MSCRMDistribution'
7. After the replication is enabled, the MSCRM folder needs to be shared.
a. Open Windows Explorer on the new CRM server.
b. Path out to the \Program Files\Microsoft SQL
Server\MSSQL\REPLDATA\mscrm folder.
c. Right click on the mscrm folder and choose sharing.
d. Share the folder with the name MSCRMSnapshotShare. Be sure to match
the syntax exactly.
e. For the share permissions, share the folder to the Everyone group
with full control.
f. For the NTFS permissions give the domain users group access with
Read and Execute rights to the folder and sub-folders.
8. Once the folder is shared, you will re-configure the Microsoft CRM
server and the Microsoft Sales for Outlook clients.
a. Un-install all Microsoft CRM Sales for Outlook clients.
b. On the Microsoft CRM server export your customizations using
Deployment Manager and then un-install The Microsoft CRM server through
Add/Remove Programs.
c. Once CRM has been removed from the system, restart the server.
After the CRM server has been re-started, delete the Microsoft CRM folder in
the Program Files directory.
d. Re-install the Microsoft CRM server. When prompted during install
choose to connect to existing databases and choose the location of the new
Microsoft SQL server.
e. After installing, import and publish your customizations using the
Deployment Manager. NOTE: Install these hot fixes BEFORE import and publish
of Schema.
1. Max String Lengths Fix 32140
2. Workflow Fix 29313
3. Role Deletion Fix 29646
4. CR Timeout Fix
5. Activity Hot Fix
6. Template Hot Fix
f. Re-install all Microsoft CRM Sales for Outlook clients.
9. Test the Microsoft CRM application and ensure that you are able to
access your data. Also test your Microsoft CRM Sales for Outlook clients to
ensure you are able to use the application.
10. At this point you should not have access to any of the reports in
Microsoft CRM. The reports will need to be re-published. This requires a
tool that Microsoft CRM Technical support has. Contact the support team for
assistance re-publishing the reports. The support team can be reached at
1-888-477-7877 or www.greatplains.com/support.
11. Once you have tested the Microsoft CRM Sales for Outlook clients and web
application functionality to ensure that they are working, you can clean up
your "old" Microsoft SQL server. To do so, please follow these steps:
a. Open Microsoft SQL Server Enterprise Manager.
b. Expand your server until you see the Replication Folder.
c. Right Click on this folder and select Disable Publishing.
d. A Wizard will appear.
e. Select the option yes, to disable publishing.
f. Complete the Wizard, this will disable publishing. This process can
take several minutes or more.
g. Once replication is disabled you can delete the Microsoft CRM
databases.
This should successfully complete the process of moving you Microsoft CRM
SQL databases from one server to another. Don't forget to schedule regular
backups of the database on the new server.
"Tuxoo" <info_@_tuxoo.net> wrote in message
news:403dc221$0$28146$636a15ce@news.free.fr...
