The Argos Database is built on the robust foundation of Microsoft SQL Server 2017 technology. The convenience and flexibility of design allows for recommended Microsoft migration procedures to be utilized. This article describes the process of moving the Argos Database using Microsoft SQL Server Management Studio Express (SSMSE), a free tool provided by Microsoft.
 |
Warning Incorrect migration of the Argos database can cause serious problems that may lead to loss of data. Sepialine cannot guarantee that problems resulting from an incorrect migration and/or conditions specific to your database can be solved. Furthermore, Sepialine service contracts DO NOT include directly-assisted database migrations. Sepialine provides Argos database migration as a separate service. Please contact the Sepialine sales department for more information about Sepialine-assisted migration support services. |
INSTRUCTIONS
The following Argos Migration documentation is designed for information technology professionals planning to move their own Argos database. It is strongly recommended that the individual(s) performing the upgrade be familiar with Microsoft SQL database technology and administration. In addition, a Windows Domain account that is a member of the Local Machine and/or Domain Administrators group is required.
For the content of these instructions, the source server will be referred to as Server A and the new host server will be called Server B. The instructions specifically cover the migration between machines running the Sepialine install of SQL 2017 Express.
Phase 1 - Install Argos on Server B
- Apply all Microsoft recommended Windows service packs and critical updates from Windows Update
- Download the latest release of Argos 7 from http://sepialine.com/argos/download.html
- Run ArgosInstall.exe to unpack the latest version of Argos
- Follow the standard installation steps to install all desired components on the new server
- Open Argos Manager to verify that the installation was successful. Note that any changes you make in the Manager will be erased.
- Open the Communication Service health page on Server B (http://SERVERB:7080/cs/health) to verify that the installation was successful. The Last update result for the Billing coordinator component should read Success after 5 seconds.
- Download and install SQL Server Management Studio Express on Server B
Phase 2 - Backup Database on Server A
The Argos database from your old server can be backed up using SSMSE. Alternately, you can use standard SQL statements to create a backup through other ODBC tools, however, this method is not covered in this article.
- Open SSMSE on your new server. At the connection prompt, use the following settings:
- Server type: Database Engine
- Server name \ db instance name: SERVERA\ARGOS (replace ServerA with the name of your old server; the default instance name for Argos 7 is ARGOS.)
- Authentication: SQL Server Authentication
- Login: sa
- Password: s3p14_lin3
- Click Connect
- Expand Databases to display the Argos7 database (this DB name will be the same for Argos 8)
- Right-click on the Argos7 database, click Tasks > Back UP
- Make a note of the Destination settings. On most DB servers, Argos 7 creates a nightly backup of your SQL database, typically in C:\ProgramData\Sepialine\Argos7\Backup\Argos.bak
- Click OK to perform another backup to the same location
- The backup of database 'Argos7' completed successfully, click OK
- Log on to Server A and copy the fresh copy (verify modified date) of Argos.bak to a folder on Server B.
Phase 3 - Restore Database on Server B
Remove the empty Argos database installed on Server B during Phase 1:
- Open SSMSE on your new server. At the connection prompt, use the following settings:
- Server type: Database Engine
- Server name \ db instance name: SERVERB\ARGOS (replace ServerB with the name of your new server; the default instance name for Argos 7 is ARGOS.)
- Authentication: SQL Server Authentication
- Login: sa
- Password: s3p14_lin3
- Click Connect
- Expand Databases to display the Argos7 database
- Right-click Argos7 and choose Delete
- The Delete Object screen will appear. Check the Close existing connections box and click OK. Note: In some cases, you may need to close Argos Manager, stop all Argos Services, and then restart the SQL (ARGOS) service in order to be able to drop the database.
- Your Argos7 database will disappear from SSMSE
- Right-click Databases and choose Restore Database
- In the Restore Database window, select Device and click the ellipse button.
- In the Select backup devices window, click the Add button
- In the Locate Backup File window, browse to the location where the backup file is located, highlight the .bak file and click OK.
- In the Select backup devices window, click OK
- In the Restore Database window, click OK.
- Database 'Argos7' restored successfully, click OK.
- Close SSMS. Open Argos Manager, click View > Settings.
- In the Argos Manager Settings window, click the Database Connection... button.
- Verify that the Server field contains the new server and instance name. Click the Test connection... link.
- Connected successfully, click OK.
- Click Save
Upgrading from a previous version
If you upgraded to a newer version of Argos while migrating, you'll receive an error about a "database version mismatch" when you launch Manager.
To upgrade the restored DB to the current Argos version, simply run SetupLauncher.exe from the ArgosInstallers folder on the new server, then follow the prompts to upgrade the database to match the other components on the server:
Phase 4 - Redirect other servers and workstations to use the Argos Communication Service or Database on the new server
Workstations and server print tracking components (both Argos Agent installations) that connected to the Communication Service on Server A will need to be redirected to Server B. We recommend redeploying the client and/or print tracking using whichever tool or method was initially used to deploy the client, such as SMS, Active Directory Group Policy, Sepialine Deployment Center, etc.
This will cause those Argos Agents to have the updated server URL for the Communication Service connection as long as the installation configuration is updated. (setup.ini file for manual installs)
If you have additional servers with Argos 7 App Server and Manager components, the simplest method for pointing these at the new server is to modify the database configuration settings.
- On the server, browse to C:\Program Files (x86)\Sepialine\Argos7 and open ArgosDatabase.config using Notepad
- Search the file text for Data Source and update the value with the new database server and instance names
- Go to Start > Run, type Services.msc and click OK to bring up the Windows Services window
- Right-click on each Argos service and choose Restart
At this point, all Argos components should be pointing to the new server. Send test prints from all print servers and verify that users continue to receive the Argos Desktop Billing Client when printing, and new print jobs appear in the Manager on the new server.
Phase 5 - Retire old Argos Integration Services
- Open Argos Manager on the new server, select Settings from the left menu
- On the Task Executors tab, highlight the old server and click Retire...
- If any Integration tasks (project import, user import, HP Designjet integration, etc) are still using the old integration server, you will be prompted to reassign them to the new server. Select the new Integration server from the drop down list and click OK.
 |
A Task Executor cannot be removed until it has been inactive for 15 minutes. |
0 Comments