1. If you want to immediately upgrade Servicing Director in combination with the migration, then 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 recovery server.
2. Servicing Director System Requirements. You will find the System Requirements on the Customer Center Knowledge Center website in the System Requirements articles.
3. Servicing Director SQL Server Required Configuration Settings. You will find the Servicing Director SQL Server Required Configuration Settings article on the Customer Center Knowledge Center website. Please search the Knowledge Center for the related article using the keywords Servicing Director SQL Required Settings.
4. Servicing Director Installation Guide. You will find the Installation Guide on the Customer Center Support Center website in the Solutions for Servicing Director.
5. 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.

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

1. The only versions of Microsoft SQL server supported for Servicing Director are listed in the System Requirements.
2. 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.
3. Install Microsoft SQL Server according to support instructions provided to you by Microsoft and apply or select the specific SQL settings.

1. Using backup methods appropriate for your production SQL server, create Production server database backups of the Service and SvcEventMgr databases.
2. Move the Service database and SvcEventMgr database backups to the recovery server using methods appropriate for your backup methods.
3. Restore the Service database and SvcEventMgr database backups on the recovery server.
4. Be sure the new databases created from restoring the backups have the required names Service and SvcEventMgr respectively.
5. Choose to overwrite the existing databases on the recovery server if your prior work on the recovery server has existing databases of the same name.

1. Using Microsoft file system methods appropriate for your Windows servers, create the SvcData folder on the recovery server.
2. The primary or master SvcData folder is required to be a local folder on the recovery 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 recovery server.
3. Using Microsoft file system methods appropriate for your Windows servers, enable network sharing on the new SvcData folder on the recovery server.

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

1. If you are using the optional Servicing Director archiver, you can move your archiver folders to the recovery 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.
2. If you want to move the archiver folders, please search the Knowledge Center for the related article using the keywords Servicing Director Moving Archive.

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 recovery server, and the optional Servicing Director applications product is not required.
2. Your source for the Servicing Director database installation program is your current Servicing Director product download.
3. You must use the SvcData folder location created in the steps above when prompted for the SvcData folder during the database product installation.
4. This is a required step.  if the database product is not installed, your server will be missing required Servicing Director components.
5. 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 recovery server.
2. On the LSCNFG application, clear the Default check boxes for the Loan Servicing and Reports SQL login section, and enter your choice of unique passwords.
3. You must use the LSCNFG run FixRights option by selecting the Run Fixrights checkbox..
4. Search the Knowledge Center for the related article using the keywords Servicing Director Resetting Logins.

1. To test the recovery server, select a specific test desktop to reconfigure the Servicing Director desktop applications.
2. Using Microsoft procedures, change the ODBC System Data Sources named Servicing and ServEM to connect to your recovery server.
3. Please search the Knowledge Center for the related article using the keywords Servicing Director Changing ODBC.
4. If the recovery server ever becomes the production server, you can use these steps on any desktop to use the recovery server.

1. Use the Servicing Director Change Reports Location application to browse to the RPT folder within the SvcData folder on the recovery server.
2. Please search the Knowledge Center for the related article using the keywords Servicing Director SvcData.

1. The Event Manager database restored to the recovery 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.
2. Please search the Knowledge Center for the related article using the keywords Servicing Director Changing Event File Paths.
3. if the recovery server ever becomes the production server, these steps must be completed.

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

1. If you have other add-on products, then review and document how to reconfigure them to use the recovery server as required by the add-on product.
2. If you have the Customer Self-Service product, please search the Knowledge Center for the related article using the keywords changing customer self-service different 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 recovery server.
2. Reindex and update the statistics on the databases and schedule this periodically.
3. Complete a new set of backups on the recovery server. 

1. From a Servicing Director desktop which has been redirected to the recovery server, open the System Administration application.
2. Click Table Setup.
3. Select Company.
4. On the Setup tab, change the Company Name to a name of your choice to identify the recovery server.

1. Once the procedures in this article have been performed and the recovery server is operational, you can move as many new copies of the production server as you would like to the recovery server in order to keep this server with a recent set of data. To do so, repeat the move procedures above. Reset the Servicing Director SQL logins using the LSCNFG application after each restore.
2. If you upgrade your production server to a new version of Servicing Director or apply an update for Servicing Director, be sure to upgrade or update recovery server and any desktop applications connected to the recovery server at the same time.
3. If your production server suffers a disaster or failure, perform all the procedures in the article. Reconfigure all the Servicing Director desktops applications to use the recovery server and reconfigure any add-on products.

ArticleNumber:

000050759