Strategy for transitioning existing ServiceDesk to another server and drive location.
Is this a valid strategy for transitioning ServiceDesk to a new physical server with minimal downtime?
Strategy: Changing from on physical server to another. Install path is on different drive. ServiceDesk version is the same on both servers. No upgrades occurring.
- HelpDesk is primary linked to a remote SQL server using the ServiceDesk database.
- HelpDesk2 is the new server. Both servers are the same OS.
- During the day, install the same version of ServiceDesk onto HelpDesk2. It is ok to install it on a different drive. Use the local database during the install.
- While HelpDesk is still online and in use, point the Helpdesk2 install to the ServiceDesk database. Both servers should now see the same information (except for attachments). NOTE: No one will enter any information into CCIHelpdesk2 until after go live.
- Using a file sync utility or RoboCopy, copy the 4 necessary directories to the HelpDesk2 server. These should be synced at the time of transition.
- At implementation time, shut down the ServiceDesk services on HelpDesk. Make sure that the 4 directories are synced to the new server.
- Rename the HelpDesk server to HelpDesk_Old, and change the IP Address.
- Rename the HelpDesk2 server to HelpDesk and change the IP to the original value.
Thank you for your help.
New to ADSelfService Plus?