I'd only do this if you're running many queries on the database, have a huge database, or are noticing performance issues that aren't caused by too little RAM. Since you have both servers available, if things don't go well you can always revert back to your current one and contact support or provide further details as to the issue you've ran into here.Īs for separating the help desk from the database, there're many ways to do this with plenty of different reasons. Note that each part should be done on the server using the localhost url instead of the designated DNS that you may have given it. Activate the license on the new server once complete.Start the new help desk and run the upgrade when prompted.Migrate the database to the new server.Stop both help desks, this way new tickets won't be generated in the old help desk and the new one won't prevent the database from being modified.Deactivate the license on the old server.Take a backup of your current help desk and database (this can be a snapshot if this is a vm).Once the new help desk is running and all seems okay, stop both help desks.Install the version you're upgrading to on the new server.This way if something goes wrong you can uninstall the new version, install the old one and then restore the backup (if you are using a VM, you can take a snapshot beforehand and revert back).Īs you have both servers available, here are some instructions tailored to your scenario: You shouldn't rely on support to assist with upgrades, to revert back to the version you were on you'll need a backup BEFORE you proceed with upgrading. You could log a call and hope to arrange something with one of the team if this is necessary. You are correct to presume SolarWinds phone support won't be available on the weekend unless you're lucky.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |