Use this procedure to move your Servicing Director production server to an existing disaster recovery server, when your production server has suffered a disaster or failure.
Your existing disaster recovery server would have been prepared in advance, remaining upgraded and updated, but offline, until you needed to switch to it as the replacement for a failed production server.
The procedure below is 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 will become effective on the new server.
Review the following:
- The Servicing Director System Requirements. You will find the System Requirements on the Customer Center Knowledge Center web site in the System Requirements articles.
- The Servicing Director Installation Guide. You will find the Installation Guide on the Customer Center Support Center web site in the Solutions for Servicing Director. Review the Installation Guide sections titled "Installing Microsoft SQL Server or SQL Server Express" and "Installing the Servicing Director Databases".
- The article Servicing Director Backups. You will find this article on the Customer Center Knowledge Center web site by searching with the key words Servicing Director Backups.
- The article Moving Data and Configurations from one Servicing Director Server to Another. You will find this article on the Customer Center Knowledge Center web site by searching with the key words Servicing Director Moving Data.
- The article Preparing a Servicing Director a Disaster Recovery Server. You will find this article on the Customer Center Knowledge Center web site by searching with the key words Servicing Director Preparing Disaster Recovery.
Confirm the failed production server and the disaster recovery server are the same version:
- Confirm the failed production server version. If you are not sure of your production server version, and the production server has failed, you can inspect the version information of the Servicing Director applications on a desktop which was configured to use to your failed server. Use the Microsoft Windows procedures to view the file properties of any of the Servicing Director application programs (.EXE) files and view the version property tab.
- Confirm the disaster recovery server version. To view the version history of your disaster recovery database upgrades, updates, and fixes, search the Knowledge Center for the related article using the key words Servicing Director Version History. Perform the procedures in the article on the disaster recovery server.
- If the disaster recovery server is an older version than your failed production server, first upgrade or update the disaster recovery server using the upgrade or update instructions provided for the versions you need to apply to the disaster recovery server.
Move the production server data and configurations to the new server:
-
In these steps, you will be replacing the data on disaster recovery server with the latest production server data and configurations. Until the move is complete, the disaster recovery server will have the older copy of the data used to setup the disaster recovery server.
-
The production server data for your new server consists of the two databases named Service and SvcEventMgr, the SvcData network shared folder, and possibly the optional archive folders if you have them.
-
You will redirect all the exiting Servicing Director desktop applications to connect to the disaster recovery server.
-
Perform all the procedures in the article Moving Data and Configurations from One Servicing Director Server to Another.
Disable the old production server:
- If the old production server is somehow still online, use Microsoft SQL procedures to take the Service and SvcEventMgr databases offline.
- On the old SvcData folder, use Microsoft file-sharing procedures to stop sharing the old \SvcData folder.
- If you have the optional old archive folders, use Microsoft file-sharing procedures to stop sharing the old archive folders.
Setup maintenance tasks on the new server:
- Configure your backup tools to backup the databases, the SvcData folder, and if you have them, the optional Archiver folders, on the new server.
- Complete a new set of backups on the new server.
Moving a Servicing Director production server to a disaster recovery server is complete.
ArticleNumber:
000045036