Use the information in this article to move or migrate a Fusion Servicing Director production server to another server, creating a new production server.

The procedures below are for your local IT or system administrator familiar with Windows and Microsoft SQL Server.

Note: Each Servicing Director system you have will need Servicing Director product licensing. Your Servicing Director product licensing is stored in your production server; therefore, when you move a copy of your production server data to your new server, your production server licensing becomes effective on the new server.

Review the following:

• If you want to immediately upgrade Servicing Director in combination with the migration, use the newer upgrade version for all references in the following procedures. For example, use the System Requirements for the upgrade version as the requirements for your new server.
• Servicing Director System Requirements. Search the knowledge base for the system requirements article for the correct software version. 
• Review Servicing Director SQL Server Required Configuration Settings. 
• Servicing Director Installation Guide. You will find the Installation Guide on the Current Release Documentation page on Support Center website in the Solutions for Servicing Director. Review the related Servicing Director Upgrade Guide if you are planning to upgrade Servicing Director.
• Determine if you have optional or custom add-on software or interfaces connecting to your Servicing Director system, such as the Customer Self-Service web product or the UltraData RealTime Online Interface, or other custom interfaces, imports or exports.  If so, any changes to the Servicing Director server may need to be coordinated with these other optional or custom add-on software or interfaces, which is outside of the scope of this article.

Make sure the new server computer meets the Servicing Director System Requirements:

• The only versions of Windows supported for Servicing Director are listed in the System Requirements.
• The new server must be on a separate Windows server from the old production server.

Install Microsoft SQL server on the new server:

• The only versions of Microsoft SQL server supported for Servicing Director are listed in the System Requirements.
• Servicing Director requires specific SQL Server settings. The currently required SQL Server settings are described in the Servicing Director SQL Server Required Configuration Settings article.
• Install Microsoft SQL Server according to support instructions provided to you by Microsoft and apply or select the specific SQL settings.

Move the production server databases to the new server:

1. Have all Servicing Director users exit all applications and end any other Service or SvcEventMgr connections.
2. Create Production server database backups of the Service and SvcEventMgr databases using backup methods appropriate for your production SQL server
3. Move the Service database and SvcEventMgr database backups to the new server using methods appropriate for your backup methods.
4. Restore the Service database and SvcEventMgr database backups on the new server.
5. Be sure that the new databases created from restoring the backups have the required names Service and SvcEventMgr respectively.
6. Choose to overwrite the existing databases on the new server if your prior work on the new server has existing databases of the same name.

7. Use Microsoft SQL Server procedures to take the Service and SvcEventMgr databases offline on the old production server. 

Create the SvcData folder on the new server:

1. Create the SvcData folder on the new server using Microsoft file system methods appropriate for your Windows servers. Note: The primary or master SvcData folder is required to be a local folder on the new server. Your institution might choose to create, update and otherwise synchronize a second copy of the SvcData folder, but these steps refer to the required SvcData folder on the new server.
2. Enable network sharing on the new SvcData folder on the new server using Microsoft file system methods appropriate for your Windows servers.
3. Review the Windows Users permissions you have on the production SvcData folder, and grant your Windows Users permission to the new SvcData folder as needed.

1. Move the SvcData folder to the new server by using Microsoft file system methods appropriate for your Windows servers.
2. Copy the SvcData folder from the production server to the new server folder you created in the prior steps above.
3. Be sure to copy all files and subfolders from the production SvcData folder.
4. Use the new SvcData folder location when you install the database product in later steps.
5. Disable network sharing on the old production server SvcData folder.

• If you are using the optional Servicing Director archiver, you can move your archiver folders to the new server.  The archiver folders are network shared folders, and your network location for the folders do not have to be the same server as your Servicing Director SQL server.
• If you want to move the archiver folders, follow the instructions in Moving a Servicing Director Archive Folder.
• If you have moved the optional old archive folders, use Microsoft file-sharing procedures to stop sharing the old archive folders.

Install the Servicing Director database product on the new server:

1. Complete the Servicing Director Installation Guide procedures in the section titled Installing the Servicing Director Databases. You are required to only install the Servicing Director database product on the new server, and the optional Servicing Director applications product is not required. Note: Your source for the Servicing Director database installation program is your current Servicing Director product download.
2. Use the SvcData folder location created in the steps above when prompted for the SvcData folder during the database product installation.
3. If you want to upgrade to a newer version of Servicing Director, install the upgrade version at this point.  You'll be required to upgrade the desktop applications to be on the same version. 
   • This is a required step. If the database product is not installed, your server will be missing required Servicing Director components.
   • If you have the Customer Self-Service add-on product, also install the Customer Self-Service database product.  Only the Customer Self-Service database product is required, and use the current version of the Customer Self-Service Installation Guide to complete this step.

1. Use the Servicing Director LSCNFG application to set new SQL Server login credentials on the new server.
2. Clear the Default check boxes for the Loan Servicing and Reports SQL login section on the LSCNFG application.
3. Enter your choice of unique passwords.
4. Use the LSCNFG run FixRights option by selecting the Run Fixrights checkbox..
5. Review Resetting the Servicing Director SQL Server Logins.

• If you chose to upgrade the Servicing Director databases to a new version above by installed a newer version of the database product above, then skip these steps and upgrade the desktop applications to match the version on the databases. Use the matching version Servicing Director Upgrade Guide and use the procedures in the section titled Manually Upgrading Fusion Servicing Director Applications.
• If the version of Servicing Director is unchanged, then reconfigure the desktop applications.
• Using Microsoft procedures, change the ODBC System Data Sources named Servicing and ServEM to connect to your new server.
• Review Changing the Servicing Director ODBC Data Sources to Use SQL Server Authentication.

• If you upgraded the Servicing Director desktop applications above, skip these steps.
• Use the Servicing Director Change Reports Location application to browse to the RPT folder within the SvcData folder on the new server.
• Review Having the Servicing Director \SvcData Folder on a Server Other Than the Database Server 

Prevent unwanted crossover to the original production server:

• The Event Manager database restored to the new server may have scheduled event data which includes file paths to the original production server.  To prevent unwanted crossover by these events to the original production server, the event criteria may need to change to update the file paths.
• Grant your Windows Users permission to the paths you edit and set in the Criteria as needed.
• Review Changing Event File Paths in the Servicing Director Event Manager Database.

Confirm your custom content is in place:

• Check for any missing custom content your institution purchased or developed, and confirm it is present and working on the new server.

Reconfigure other add-on products:

• If you have other add-on products, then reconfigure them to use the new server as required by the add-on product.
• If you have the Customer Self-Service product, follow the instructions in Changing the Servicing Director Customer Self-Service To Use a Different Microsoft SQL Server.

Set up maintenance tasks on the new server:

1. Configure your backup tools to back up the databases, the SvcData folder, and, if you have them, the optional Archiver folders, on the new server.
2. Reindex and update the statistics on the databases and schedule this periodically.
3. Complete a new set of backups on the new server.

Moving the production server is complete.

ArticleNumber:

000049055