Layton ServiceDesk - Installation - Migration

From Layton Support
(Difference between revisions)
Jump to: navigation, search
(Procedure)
(Procedure)
Line 23: Line 23:
  
 
==Procedure==
 
==Procedure==
Using Microsoft SQL Server Management Studio, back up and restore the database to the new SQL Server. Follow '''[[Layton ServiceDesk™ - Installation - Clean Reinstallation|Clean Reinstallation]]''', connecting to this restored database.
+
#Backup the existing application installation directory. The default path is: ''C:\Program Files\Layton Technology\Layton ServiceDesk\''
 +
#Backup the existing database using Microsoft SQL Server Management Studio (SSMS)
 +
#Restore the database backup to the new SQL Server using SSMS
 +
#Install the application on the new server as per '''[[Layton ServiceDesk™ - Installation - New Installation|New Installation]]'''
 +
#When the Database Tool opens, choose '''[[Layton_ServiceDesk™_-_Installation_-_Connect_to_Existing_Database|Connect to an existing database]]''' and point it to your ServiceDesk database restored on the new SQL Server in Step 3
 +
#Copy the needed files from the backup made in Step 1 to your new application installation directory. Some common items that may need migrated are:
 +
#*''Application_Images\'' - If custom images were added to any forms in '''[[Layton_ServiceDesk™_-_Configuring_the_System_-_Form_Design|Form Design]]'''
 +
#*''HB_Data\ChangeAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Change#Change_Logging|Changes]]'''
 +
#*''HB_Data\EmailBodies\'' - Email notifications configured in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Email_Settings_%26_Bodies|Email Settings & Bodies]]'''
 +
#*''HB_Data\MailIn\'' - File attachments for emails in the '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Converting_an_Incoming_Email_into_a_Request|Incoming email queue]]'''
 +
#*''HB_Data\ProblemAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Problem#Problem_Logging|Problems]]'''
 +
#*''HB_Data\RequestAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Overview|Requests]]'''
 +
#*''HB_Data\LogFiles\'' - Application log files
 +
 
 
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p>
 
<p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p>

Revision as of 17:37, 2 February 2015

Btn back up.png Back to Contents

Contents

Migrating the Application Only

Use Case

This would be when you need to move the application to a new server, but leave the database on the existing SQL server.

Procedure

  1. Backup the existing application installation directory. The default path is: C:\Program Files\Layton Technology\Layton ServiceDesk\
  2. Install as per New Installation
  3. When the Database Tool opens, choose Connect to an existing database and point it to your ServiceDesk database
  4. Copy the needed files from the backup made in Step 1 to your new application installation directory. Some common items that may need migrated are:
    • Application_Images\ - If custom images were added to any forms in Form Design
    • HB_Data\ChangeAttach\ - File attachments for Changes
    • HB_Data\EmailBodies\ - Email notifications configured in Email Settings & Bodies
    • HB_Data\MailIn\ - File attachments for emails in the Incoming email queue
    • HB_Data\ProblemAttach\ - File attachments for Problems
    • HB_Data\RequestAttach\ - File attachments for Requests
    • HB_Data\LogFiles\ - Application log files

Migrating Application and Database

Use Case

When you need to move both application and database to another or other servers.

Procedure

  1. Backup the existing application installation directory. The default path is: C:\Program Files\Layton Technology\Layton ServiceDesk\
  2. Backup the existing database using Microsoft SQL Server Management Studio (SSMS)
  3. Restore the database backup to the new SQL Server using SSMS
  4. Install the application on the new server as per New Installation
  5. When the Database Tool opens, choose Connect to an existing database and point it to your ServiceDesk database restored on the new SQL Server in Step 3
  6. Copy the needed files from the backup made in Step 1 to your new application installation directory. Some common items that may need migrated are:
    • Application_Images\ - If custom images were added to any forms in Form Design
    • HB_Data\ChangeAttach\ - File attachments for Changes
    • HB_Data\EmailBodies\ - Email notifications configured in Email Settings & Bodies
    • HB_Data\MailIn\ - File attachments for emails in the Incoming email queue
    • HB_Data\ProblemAttach\ - File attachments for Problems
    • HB_Data\RequestAttach\ - File attachments for Requests
    • HB_Data\LogFiles\ - Application log files

Btn back up.png Back to Contents

Personal tools
Namespaces

Variants
Actions
Main Page
Online User Guides
General Support
Release Notes
Toolbox