Server Migrations are done by our consulting and services team, this is a billable service.
A support member can pass through your case to the services team if you agree to wanting to book a billable upgrade job.
Alternatively, you can do a self-migration/Installation, but Attaché always recommends and prefers that an Access Attaché Services/Consultant is used for a migration of Attaché as there are many components (ODBC/DSN, Alex Components, ClearView, AV Firewall exclusions, connecting datasets to Attaché Online, or 3rd Party integrations etc.) and each setup can be different from site to site.
If you still wish to proceed with doing your own Migration, Attaché advises this is done at your own risk and that any issues created by self-upgrade will be billable to fix.
Installing Attaché Program files
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. See the links below:
Important notes
This process will use Attaché Backup Scheduler, which is installed as part of the Attaché Database Server installation.
It is essential that the migrating from and to servers have same version of Attaché installed.
Ensure you have applied the Attaché licence on the new server. see Request and install a new or updated Attaché Licence.
All users must be logged out of the software for the duration of the migration process. This can range from one hour to a whole day depending on variables including:
Number of companies to be migrated.
Number of workstations.
Data size of the companies to be migrated.
Specifications of the from and to servers.
Network file transfer speed.
Additional components to set up such as custom reports and external connections.
Problems that may be encountered during setup related to the environment, including firewall, anti-virus and network and computer/server permissions.
Attaché recommends completing a test migration, before a final production migration.
A test migration can use live, or history data. One of the aims is to ensure that the staff completing the migration is comfortable with the process, so that the data can be safely and successfully migrated.
All critical functionality should be tested on the test migration environment before proceeding to a production migration.
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.
Backing up current Attaché companies and settings
Note: Complete this task on the current Attaché Database Server.
To create a backup of your Attaché companies (datasets) and settings:
Navigate to the \AttacheServer\Attache Backup Scheduler\ folder.
Right-click on AttBackupScheduler.exe and select Run as Administrator.
If prompted by User Account Control, click yes.
Select New.
In the Select datasets to backup menu, tick all the companies to be migrated to the new server.
Select a destination for the .zip file that will be created (for example, C:\Temp).
Ensure the Attaché Program Folder is correct (for example C:\Apps\AttacheBI).
Select OK.
Type in a task name and optionally a description (for example, Attaché Server Migration Backup).
Select Next.
Select One Time.
Select Next.
Ensure the Start date is set to the current date and the Time is in the future, generally in the next 5 minutes.
Select Next.
Select Run only when user is logged on.
Select Next.
Select Finish.
Allow time for the scheduled backup to complete. This may take some time, depending on the number of companies and size of data for each company.
Open the created .zip and check that it contains a .dat (data) file.
Moving the companies and settings to the new Attaché Database Server
📌Note: Complete this task on the new Attaché Database Server.
To move the companies (datasets) and settings to the new server:
Copy the saved backup (.zip) file to the new server via your preferred file transfer method, for example Network File Transfer, USB Memory or uploading/downloading via a secure file transfer portal.
Navigate to the \AttacheServer\Attache Backup Scheduler\ folder.
Right-click on AttBackupScheduler.exe and select Run as Administrator.
Select Restore From Location.
Browse to the folder where you copied the backup (.zip) file to in step 1.
Select Next.
Highlight the backup (.zip) file that was copied to the server in step 1 and ensure the file name matches the backup (.zip) file.
Select Next.
Ensure the Attaché Database Server location is correct.
Ensure the Attaché Program Folder location is correct.
Select Next.
Tick all companies which are to be accessible to clients on the new Attaché Database Server.
Open the services console (services.msc) and stop the Attaché Database Server and Attaché API Service. Ensure no one is logged into the software at this time.
Select Next.
Review the details on screen and then select Restore.
Wait for the restore to complete and then select Finish.
Open the services console (services.msc) and start the Attaché Database Server and Attaché API Service.
Pointing workstations to the new Attaché Database 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:
On the Attaché Sign On screen, select Server (F3).
Select the row for the new Attaché Database Server Host Name.
Choose Select.
or
(b) Manual entry of data connection string (Attaché workstation)
To test each workstation connection, log in to the software.
Pointing ODBC DSNs to the new Attaché Database Server
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.
Follow Set up a new ODBC DSN connection to recreate or edit the current DSN.
📌Note: if editing, only the Host field will need to be changed.
Test the DSN is configured correctly. The quickest way to do this is to use Microsoft Excel.
Updating company connections to Attaché Online
Migrating to Attaché 19.2 (or later)
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.
Decommissioning the old Attaché Database Server
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:
Open the services console (services.msc)
Stop the following services, once it has been confirmed all users are no longer processing, or logged into the software:
Attaché Database Server.
Attaché Service API (Attaché 19 and earlier).
Attaché Cloud Connector - Message Processor (Attaché 19 and earlier).
Attaché Cloud Connector - Message Relay (Attaché 19 and earlier).
Attaché API Service (Attaché 20.1 and later).
PLALTSRVBI.
PLEDSSRVBI.
PLHDMSRVBI.
Disable the following services, so that they no longer are able to be started:
Right Click > Properties > Startup Type - "Disabled".
Apply.
Ok.
Attaché Database Server.
Attaché Service API (Attaché 19 and earlier).
Attaché Cloud Connector - Message Processor (Attaché 19 and earlier).
Attaché Cloud Connector - Message Relay (will be decommissioned in Attaché 20.1).
Attaché API Service (Attaché 20.1 and later).
PLALTSRVBI.
PLEDSSRVBI.
PLHDMSRVBI.
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.