r plc Migrating Partner to a New Server

Transcription

1 r plc Migrating Partner to a New Server Version 1 June 2009

2 COPYRIGHT This document and all software products described within it are subject to copyrights with all rights reserved. Under copyright laws, the documentation or the software may not be copied, photocopied, reproduced, translated, or reduced to electronic medium in whole or part, without prior consent of TFB plc. TFB has a policy of constant development and improvement. We reserve the right to alter, modify, correct and upgrade our products and documentation without notice and without incurring liability. Copyright: TFB plc 1-2 Kingdom Close Kingdom Business Park Segensworth East Fareham Hampshire P015 5TJ All Worldwide Rights Reserved All Trademarks Acknowledged Issue Date: June 2009 Version: 1 Author: JAL Approved By: ISW 08/06/09 2

3 Contents 1. Introduction 4 2. Components of a Partner for Windows Install 4 3. Considerations before Migration 4 4. Pre-requisites before Migration 4 5. Carrying Out the Migration Isolating the Current Install so no further work can be carried out Backing up the Database Transfer of Database and Partner Directory Restoring the Database Updating the Partner Database Allowing Access Back to Partner Workstation Setup System Setting Setup 6 6. Summary 7 3

4 1. Introduction This manual outlines all the components which make up the Partner for Windows application and database. It then goes on to describe and provides an example of how Partner for Windows should be migrated from one server to another. 2. Components of a Partner for Windows Install Partner for Windows is essentially made up of a single Database usually hosted on Microsoft SQL Server and a thin client based application stored centrally on a server. The application also outputs and saves multiple files such as Report files and case management templates and documents. These are all saved under the Partner directory usually found on the route of one of the servers hard drives. Users connect to the application and database using a desktop shortcut pointing directly at the application executable (Sp.exe) on the server and the connection to the database is made through a data source (ODBC) which is setup on each workstation. 3. Considerations before Migration Users access the application and database direct from the server so any name change of the server would result in every users Partner for Windows Shortcut and data source (ODBC) being amended to the new server name because the file path will have changed. Also, because Partner stores the location (File Path) of every file it outputs as outlined above you would be required to run both the DOCLU.SQL and the ARCFLU.SQL scripts on the Partner database which alters every file Path in the Database which is linked to a stored file to the new Server name/ Path name. We would recommend where possible to keep the server name and folder structure the same and you would therefore have no need to carry out any of the above. Please Note: If the server name is to change, care should be taken not to increase the character length of the name as this can affect the File Path entries in the database which can become too long for the database fields causing data to be truncated. If the server name length is to be increased please consult with TFB Helpdesk. 4. Pre-requisites before Migration Before the migration takes place an install of SQL server will need to be carried out on the new server. We would advise a standard SQL server install and would only ask to ensure that SQL Mixed Mode 4

5 Authentication is selected and that TFB are informed of the SA password used. (We generally use a SA password of ytrewq). Note: Partner for Windows has not been fully tested on SQL 2008 however we do have sites which are already successfully using this build of SQL and we do not foresee any issues with this version. 5. Carrying Out the Migration In the following walkthrough we will presume that the server name will be changing and will be staying the same character length. We also presume you will be moving both the database and Partner files to the same server and keeping the Partner file structure also the same Isolating the Current Install so no further work can be carried out Firstly we need to ensure no users can access partner to ensure that there is no data loss during the migration. On the original server you need to unshare the Partner directory and this will ensure that no users can run the Sp.exe (Partner Application) Backing up the Database Next a full database backup needs to be carried out on the Partner database using Microsoft SQL Management Tools (Enterprise Manager or SQL Management Studio). Ensure that the file is saved with the extension of (.bak). For assistance on performing a SQL backup please refer to our Carrying out a Database Backup on SQL Manual Transfer of Database and Partner Directory You can now copy the Partner directory and all its contents as well as the backup.bak file you have made across to the new server Restoring the Database Once transferred across the database backup file will need to be restored to the new server. You will need to create a new database and then restore the backup file using SQL Management Tools (Enterprise Manager or SQL Management Studio). If you have upgraded the version of SQL server (i.e. SQL 2000 was installed on the original server and SQL 2005 has been installed on the new server) then at this point you would also need to amend the Compatibility Level of the database as required. If you are unsure how to do this please contact the TFB Helpdesk Updating the Partner Database Once restored then we need to update the database so that there is no trace of the old server in the file path fields in the database. To do this you need to run the doclu and the arcflu scripts which can be located in the Partner/Scripts folder on the server. These scripts will both need to be run using SQL management tools. Both scripts contain the following code which you will need to amend as appropriate. = '\\OrigionalServername\Partner' = '\\NewServername\Partner' 5

6 5.6. Allowing Access Back to Partner Now that the database, the application and its associated files have been copied across you can now reshare the Partner directory so that other workstations on the network can access the application. You must ensure that the folder is reshared with full control (Permissions Button) Workstation Setup Before users will be able to get back into Partner the TFB (Partner for Windows) shortcuts and the data source (ODBC) for Partner on all workstations will all need to be amended to point at the new server. Once his is carried out users should be able to log in to Partner. The reports location in File -> Workstation Settings (within Partner) will also need to be amended as appropriate for each workstation. Workstation settings 9P Page 1 1 Page 2 I Reports ILocation l'aservername \ Partner \ R eports Crystal Reports exe location 1 Extension l. rp 1 Fv-, Preview all reports before printing 5.8. System Setting Setup The last stage of the migration is to amend the system and user settings to reflect the new server name. In Partner you will need to: a. Go to File -> System Settings and amend every file path field as appropriate. MN Cr:Cuctom btrirla settings 9 -' J." to' ' General settings I More I Time I Case I Accounts I ZyLAB I Practice details I Post Room I NLIS File storage locations Case Manager Templates l'aservername \Partner \Templates.Q. I URU 4 I II. I Case Manager Documents l'aservername \Partner \Docs Archive Matters IVServername \Partner \Archive User Defined Reports l'aservername \Partner \UserDefined Optional Scripts l'aservername \Partner \Optional Excel Reports VAServername \Partner \Reports \Excel b. Go to Maintenance -> Core -> Servers and remove the old server name and insert the new server. c. Go to Maintenance -> Users and for each user change the preferred server field found on the General tab to the new server you have just created. In Practices where there are a large number of users this can be done via a SQL script and we would advise speaking to Support team regarding this. 6

7 Please Note: To carry out a migration where the server name will be remaining the same you can carry out the above procedure however you will not be required to carry out steps 5, 7 or Summary Where possible we would advise keeping the Server name and the file structure the same on the new server as this will make the migration much smoother and will mean less downtime for the Practice. If you are unsure of how to carry out the running of any SQL scripts (Such as in step 5.5) and any Partner system setup (Such as in step 5.8) then our support team will be able to advise during normal working hours for no charge. If you require any out of hours support for the migration then this will need to be pre-arranged with support and would generally incur a charge. If you have any further queries please don't hesitate to contact TFB Support. 7