Migration of SCP from one server to another

Migration of SCP from one server to another

1. Stop the application on the production server.

2. Take a trimmed backup of the application (backup without attachments) if you are using the default PgSQL database. If you are using MSSQL, you can take a SQL backup (.bak).

3. Download and install the same build of the application on the new server. Start the application and check by connecting to the UI. 

4. Stop the application.

5. If the DB is PgSQL, restore the backed-up data (.data file). 

6. If the DB is MSSQL, and if the database is going to be on a different server as well, you can create a new database, restore the SQL data (.bak) and map the database with the new installation. If the database is going to be on the same SQL server, simply map the existing production database to the new installation. Please ensure that you have a proper SQL backup whatsoever before performing the migration.

- > To map the database with the new install, go to supportcenter/bin, and execute changedbserver.bat. Mention the SQL server details and save. 

7. Start the application, connect to the UI and check if the data is fine.

8. Once the connection is established on the new server, stop the application. And move the below folders from the old server to the new server under supportcenter directory.

archive
custom
inlineimages
index
fileAttachment


Note : By default, fileAttachments get saved under supportcenter folder. If you have specified a different path for file attachments, move the folder to the correct file path. You shall find the file attachment path in Admin - > Global settings - > Settings - > Other settings - > file attachments path.


9. Once done, start the application.



                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • Database migration from MySQL to Postgres/MSSQL in SCP 8.1

                        We no longer support the use of MYSQL as database in SupportCenter Plus. Hence, we request our users to migrate to Postgres (which is in-built) or Microsoft SQL. Please follow the below steps to carry out the database migration: 1. Shutdown the ...
                      • SCP upgrade from 11.0 to 14.0 prerequisites

                        Before migration to scp version 14 below 2 points has to be done in scp 11027 1. Back up password should not be default i.e SCP123!, it should be updated 2. TLSv1, TLSv1.1 has to be added under the file /home/jre/lib/security/java.security file ( ...
                      • Round Robin in SCP

                        Here is the custom trigger plugin for round robin auto assign feature Steps to follow 1. Extract the attached zip 2. Copy the Last_Assigned_Tech.txt and Round_Robin_Assign_Tech.json files to C:\\ManageEngine\\SupportCenter\\integration\\conf folder ...
                      • SCP 11.0 and Jira integration

                        Integration Steps   In SCP 11.0, JIRA administrator credentials and server URL configuration fields will not be available in the Jira.xml file. They must be configured on the current integration page. Follow the below steps to move the integration ...
                      • Inline images broken after SCP Upgrade

                        We suspect that this issue may arise if the migration schedule has not been run post-upgrade. To troubleshoot this issue further, we kindly request the output of the following query. Please connect to the database of the working build and execute the ...