This page contains step-by-step instructions for migrating Attaché from one server to another. This includes updating ODBC DSN connections and moving custom ClearView reports.
On this page
Note: If you are using Attaché Accounts and Payroll (version 1.x) see How to move Attaché data to a new location (Attaché Accounts tutorial)
Prior to migrating Attaché company data, you need to install Attaché and related products (such as ClearView, Asset Management and ODBC) and the Attaché Database Server on the new server. Follow the standard installation steps and ensure Attaché is working on the new server:
If migrating to Attaché 19.2 (or later): Do not disconnect companies that are connected to Attaché Online organisations prior to migrating. Instead, after migrating you use the Replace function in Cloud Connector to update the connection. See Reconnecting Companies to Attaché Online below. If migrating to Attaché 19.1 or earlier, also see below.
Note: Complete this task on the current Attaché Database Server.
To create a backup of your Attaché companies (datasets) and settings:
Note: Complete this task on the new Attaché Database Server.
To move the companies (datasets) and settings to the new server:
Each workstation that connects with the Attaché application needs to be set up to access the database on the new server. You can use either of the following methods to do this:
(a) From within Attaché on each workstation:
To test each workstation connection, log in to the software.
The server DNS Name and IP will usually be different on the new server. This means that an ODBC DSNs will need to be recreated or edited to reflect the new hostname.
The DSNs will need to be updated on each workstation PC using ODBC to extract data from Attaché BI.
If you have custom ClearView reports, you need to move them to the new Attaché Database Server.
There are two methods of moving custom reports between installations:
(a) Export and then import the custom reports
(b) Copy the PLINK.dat file from the old Attaché program directory to the new one. For example:
If you have Attaché desktop companies that are connected to Attaché Online organisations, you need to update the connections.
Do not disconnect the companies prior to migration. Instead, after you have installed the new Attaché Database Server and application, log in to each connected company and launch Cloud Connector from the desktop menu. Follow the wizard and when asked to connect to an organisation, click the Replace button to update the connection.
Companies need to be disconnected from Attaché Online organisations after final processing has been completed on the old Attaché Database Server. This is to ensure that two identical datasets do not create synchronisation conflict on the online organisation environment.
To confirm the company has been successfully disconnected, login to the Attaché Online Organisation as a user with "Organisation Admin" privileges
To avoid confusion and data being entered in the the incorrect database, it is recommended that your old Attaché Database Server is brought offline at the time of migration, as soon as the final backup is made. This means that there will be some downtime, while restoring data to the new server, as well as connections from workstations are complete. It is reasonable to have the new server setup, and workstations connected, testing on Sample Data before completing the final live data migration, ensuring a smooth transition.
To disable the old Attaché Database Server:
Once a reasonable amount of time has passed, all services have been tested, and running as expected on the new Attaché Database server, a final environment backup can be taken for reference using the site IT's preferred method. Each site can then chose how to proceed with decommissioning the relevant IT Resource, whether a physical server, or virtual machine.
In the case where a server-to-server migration has failed for an unknown reason, these services can be brought back online, and processing can continue as usual.
REF: 192 HL0048 271119