Layton ServiceDesk - Installation - Migration
(→Procedure) |
m (Completed section) |
||
(23 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | <p align="right">[[File:btn_back_up.png|link=User Guide for Layton | + | <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> |
__FORCETOC__ | __FORCETOC__ | ||
+ | =Overview= | ||
+ | We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues. | ||
+ | |||
+ | ==Version== | ||
+ | Check the '''[[Layton ServiceDesk - Procedures - General - How to Find the Version Number|application version]]''' on your live installation. Check '''[[LSD Current Version|here]]''' for the latest version. | ||
+ | |||
+ | If you are not running the latest version on your source installation, please contact Support for the version you are running. You will be provided with a link to the latest full version for use in the below procedures. | ||
+ | |||
=Migrating the Application Only= | =Migrating the Application Only= | ||
==Use Case== | ==Use Case== | ||
Line 6: | Line 14: | ||
==Procedure== | ==Procedure== | ||
− | + | '''[[Layton ServiceDesk - Installation - Migration - Application Only|Migration - Application Only]]''' | |
− | + | ||
− | + | =Migrating the Application Only (Direct Update to Latest Version)= | |
− | + | ==Use Case== | |
− | + | If you need to move the application to a new server, but leave the database on the existing SQL server. You would follow this version of the procedure if the currently installed version on the source server is earlier than the '''[[LSD Current Version|current version]]'''. | |
− | + | ||
− | + | ==Procedure== | |
− | + | '''[[Layton ServiceDesk - Installation - Migration - Application Only (Direct Update to Latest Version)]]''' | |
− | + | ||
− | + | ||
− | + | ||
=Migrating Application and Database= | =Migrating Application and Database= | ||
Line 23: | Line 28: | ||
==Procedure== | ==Procedure== | ||
− | + | '''[[Layton ServiceDesk - Installation - Migration - Application and Database|Migration - Application and Database]]''' | |
− | <p align="right">[[File:btn_back_up.png|link=User Guide for Layton | + | =Migrating Database Only= |
+ | ==Use Case== | ||
+ | When you need to move just the database to another SQL server. | ||
+ | |||
+ | ==Procedure== | ||
+ | '''[[Layton ServiceDesk - Installation - Migration - Database Only|Migration - Database Only]]''' | ||
+ | <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> |
Latest revision as of 12:00, 29 August 2023
Contents |
[edit] Overview
We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues.
[edit] Version
Check the application version on your live installation. Check here for the latest version.
If you are not running the latest version on your source installation, please contact Support for the version you are running. You will be provided with a link to the latest full version for use in the below procedures.
[edit] Migrating the Application Only
[edit] 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.
[edit] Procedure
[edit] Migrating the Application Only (Direct Update to Latest Version)
[edit] Use Case
If you need to move the application to a new server, but leave the database on the existing SQL server. You would follow this version of the procedure if the currently installed version on the source server is earlier than the current version.
[edit] Procedure
Layton ServiceDesk - Installation - Migration - Application Only (Direct Update to Latest Version)
[edit] Migrating Application and Database
[edit] Use Case
When you need to move both application and database to another or other servers.
[edit] Procedure
Migration - Application and Database
[edit] Migrating Database Only
[edit] Use Case
When you need to move just the database to another SQL server.