Migrating the Aralco Server
If you don’t feel comfortable migrating the Aralco server by yourself, this is available as an add-on service. Please contact the Aralco Help Desk at firstname.lastname@example.org for a quote.
Please contact the Aralco Support Department in advance of making the switch in order to confirm the process, and to find out if there is any additional information that you may need before proceeding.
Once the system is prepared, along with Microsoft SQL Server and SQL Management Studio, here are the steps to follow for migrating the Aralco server:
- Ensure all users are out logged out of both Back Office, and Point of Sale. This is absolutely critical so that the backup of your database includes ALL transactions;
- If possible, change the IP address and name of the old server;
- Also, if possible, change the new server to the previous IP address and name of the old server. Changing the name is only applicable if you use names rather than IP addresses to identify the server;
- Within Back Office, go to Utilities » Backup Database and create a current backup of the database. Be sure to note the location and file name of the backup file that will be created – usually something like C:\ARALCO\BACKUP\AralcoBOSyyyymmdd@hhmmss;
- Once started, you’ll see an icon on the right side of the Window’s Taskbar – note that it can take a while for it to start. Hovering the mouse over the icon will display a progress %;
- If the backup does not start this usually means the sync_server is not running and needs to be started;
- Transfer the entire ARALCO directory and the newly created backup file from step 4 to the new server;
- Login to the new server as a user with administrative privileges;
- Set User Account Control to its lowest setting, and disable Smart Screen (applies to Windows 8.x, 10, and certain version of Windows Server);
- Within your Anti-Virus / Security Software, add an exception or exclusion for the <drive>\ARALCO folder;
- Using the Microsoft SQL Server Management Studio application, restore the file created in step 4. Unless it was different on the old server, the database should be named AralcoBOS;
- Start up sync_server application on the new server;
- If the new server has a different IP address and/or name (if applicable), follow these instructions for migrating your workstations over;
- If Point of Sale is run on the server, follow steps 6 onward to get it setup;
- On a workstation test to make sure it can load Back Office, and that the Point of Sale is communicating with the server.
If you have any questions regarding this process please contact the Aralco Support Desk at email@example.com.