Skip to end of metadata
Go to start of metadata

QUESTION

How do I move my Argos 7 installation to a new server?

ANSWER

The Argos 7 Database is built on the robust foundation of Microsoft SQL Server 2008 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 7 Database using Microsoft SQL Server Management Studio Express (SSMSE), a free tool provided by Microsoft.

Warning

Incorrect migration of the Argos 7 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 HOWTO 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 NT 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 2008 Express.

Phase 1 - Install Argos 7 on Server B

  1. Apply all Microsoft recommended Windows service packs and critical updates from Windows Update 
  2. Download the latest release of Argos 7 from http://www.sepialine.com/get
  3. Run UnpackArgos7xx.exe to unpack the latest version of Argos
  4. Follow the standard installation steps to install all desired components on the new server
  5. Open the Argos Manager to verify that the installation was successful. Note that any changes you make in the Manager will be erased.
  6. Open the Communication Service health page on Server B to verify that the installation was successful. Make sure that "Last jobs synchronization result" is set to "Success": http://SERVERB:7080/cs/health
  7. Download and install SQL Server Management Studio Express on Server B

Phase 2 - Backup Database on Server A

The Argos 7 database from your old server can be backed up using SSMSE. Alternately, you can use standard SQL statements to create a backup through SQLCMD, however, this method is not covered in this article.

  1. Open SSMSE on your new server. At the connection prompt, use the following settings:
    1. Server type: Database Engine
    2. Server name: SERVERA\Argos (replace "ServerA" with the name of your old server)
    3. Authentication: SQL Server Authentication
    4. Login: sa
    5. Password: s3p14_lin3

      Note: the default installation of Argos 7 installs a SQL Express instance called "Argos". If you installed in an existing SQL Server instance, your name may vary.

  1. Click "Connect"
  2. Expand "Databases" to display the Argos7 database
  3. Right-click on Argos7, choose Tasks>Back Up
  4. Make a note of the Destination settings. Argos 7 creates a nightly backup of your SQL database, typically in one of the following locations:
    1. Server 2008/Windows 7/Vista: C:\ProgramData\Sepialine\Argos7\Backup\Argos.bak
    2. Server 2003/XP: C:\Documents and Settings\All Users\Application Data\Sepialine\Argos7\Backup\Argos.bak
  5. Click "OK" to perform another backup to the same location
  6. When finished, you will see a message that states "The backup of database 'Argos7' completed succesfully."
  7. If you have admin access to the file structure of Server A, browse to the backup location (for example, \\SERVERA\c$\ProgramData\Sepialine\Argos7\Backups) and copy Argos.bak to a location on Server B, such as c:\Argos.bak. If you do not have admin access from Server B to Server A, log on to Server A and copy Argos.bak to a folder on Server B.

Phase 3 - Restore Database on Server B

At this point, you are ready to move the Argos 7 database from your old server to your new server. But first, you will need to remove the empty Argos 7 database installed on Server B during Phase 2.

  1. Use SSMSE to connect to Server B with the following credentials:
    1. Server type: Database Engine
    2. Server name: ServerB\Argos (replace "ServerB" with the name of your new server)
    3. Authentication: SQL Server Authentication
    4. Login: sa
    5. Password: s3p14_lin3
  2. Click "Connect"
  3. Expand "Databases" to display the Argos7 database
  4. Right-click Argos7 and choose "Delete"
  5. The Delete Object screen will appear. Check the "Close existing connections" box and click "OK".
  6. Your Argos7 database will disappear from SSMSE
  7. Right-click "Databases" and choose "Restore Database"
  8. Type "Argos7" in the "To Database" field
  9. Select "From device" radio button and click the Ellipsis (...) button
  10. The "Specify Backup" dialog appears. Click "Add" and locate your Argos.bak file created during Phase 1

  11. Click "OK"
  12. A list of available backup sets will appear. Choose the most recent "Full" backup from the list and click "OK"
  13. You will receive a message confirming that your database restoration was successful
  14. Open the Argos Manager to confirm that it successfully communicates with the new database.
  15. Click View>Settings and click "Database Connection..."
  16. Verify that the Server field is pointing to the database on your new server

Upgrading from a previous version

If you upgraded to a newer version of Argos while migrating, you'll receive the following error when you launch Manager:

To upgrade the restored database to the current Argos version, run SetupLauncher.exe from the Argos7Installers folder on the new server. 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 on the new server

Any workstations that connected to the Communication Service on Server A will need to point to Server B. We recommend redeploying the client using whichever tool was initially used to deploy the client, such as SMS, Active Directory Group Policy, Sepialine Deployment Center, etc.

If you have additional servers with Argos 7 components (Communication service, Print Tracking, etc), the simplest method for pointing these at the new server is to modify the database configuration settings. This method can be used on workstations to repoint the Desktop Client, if desired.

  1. On the server, browse to C:\Program Files\Sepialine\Argos7 and open ArgosDatabase.config using Notepad
  2. Locate the "Data Source" value within the config
  3. Change this to point to Server B. Make sure to leave the SQL Instance name (Argos) and do not change any other settings
  4. Go to Start>Run and Type "Services.msc" to bring up the Services window
  5. 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 Client when printing, and new print jobs appear in the Manager on the new server.

 

Phase 5 - Retire old Argos Integration Services

The final step in the migration is to make sure that the task executor from Server A is retired. Task executors (AKA integration services) handle tasks like device-based tracking and project imports, so it's very important these tasks are mapped to an active server. 
  1. Open Argos Manager on the new server
  2. Go to View>Settings>Task Executors
  3. Select the old server (in this case shown as last seen 2 hours ago)
  4. Click the "Retire..." button
     
  5. 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. 
     

 

A Task Executor cannot be removed until it has been inactive for 15 minutes.