How to move the Archive Manager 5.x Databases to a new SQL Server. (4278259)

Before you start, it is recommended to take a full backup of the Archive Manager Databases.

STEP 1

Stop all Archive Manager services and the Archive Manager Website

STEP 2

Take your current database off-line and copy your database and maintenance jobs to the new server.

• Open SQL Management Studio on your Current SQL Server
• Take your Current Archive Manager and AfterMail_Temp databases offline.
  • Right-Click on the Database | Tasks | Take Offline

  

• Copy the Archivemanager.mdf file/s and Archivemanager_log.LDF file/s to your new SQL Server.
• Copy the AfterMail_TEMP.mdf file/s and AfterMail_TEMP_log.LDF file/s to your new SQL Server.

Note:  Current location of the files can be found by right-clicking on the Database | Properties| Files.  Scroll to the right and find the Path:

• Copy the Archive Manager Jobs
  • In SQL Management Studio, expand SQL Server Agent | Jobs

• For each of the following jobs:
  • CleanTempTable
  • Mailbox Maintenance - Link Embedded Messages - Archivemanager
  • Mailbox Maintenance - Populate Virtual Mailboxes - Archivemanager
  • Rebuild Index - Archivemanager

• Right-click on each job and select --> Script Job as | Create To | File

• Copy the resulting files to your new SQL Server.

Note: If you have any custom Archive Manager jobs, copy them as well.

STEP 3

Attach your Archive Manager databases to your new SQL Server.

• Log into your New SQL Server and open SQL Management Studio
• Right-click Databases and select Attach
• Attach the ArchiveManager and AfterMail_Temp database.

• Change the Compatibility Level to your current version of SQL Server, for both the ArchiveManager and AfterMail_Temp database
  • Right click and select properties | Options
  • Set the SQL Compatibility Level to the highest available level on your SQL Server. 

Example:

If your new SQL Server is SQL 2016, then set the compatibility level to "SQL Server 2016(130)".

STEP 4

Create your SQL Jobs from the job scripts that you copied over from your old SQL Server.

• For each of the .sql job files copied from the old server:
  • Click File | Open | File, to open the .sql script then click Execute

  

  • Expand SQL Server Agent | Jobs to verify the jobs have been created.

STEP 5

Set Security for your Archive Manager Accounts.

• Right Click Security | Logins
• Add the following Accounts:
  • ArchiveMgr_ESM
  • ArchiveMgr_Service
  • ArchiveMgr_Journal
• For Each account, click the User Mapping tab and for the ArchiveManager and AfterMail_Temp ad db_owner and public for role membership.
• Click the Server Roles tab and add the accounts to bulkadmin

Note: Any user that will be operating the Configuration Console will also need the db_owner permission to the ArchiveManager database.

STEP 6

Modify the connection String in Configuration Console.

• After the databases have been attached to the new server and permissions applied, on your AM Server
  • Open the Configuration Console
  • You will get an error connecting to the database, Click Ok

  

  • Under Settings, enter your new server name, click the dropdown and select the ArchiveManager database.

  

  • Click Next, verifying your settings, and close the configuration console.

Note: Archive Manager 4x used a setting in the configuration console "Full Text Index Temp Path" pointing to a share on the SQL server.  This setting is no longer used in Archive Manager 5.x and can be ignored.

STEP 7

Start the Archive Manager services and website and watch the event log for errors relating to SQL.

Note: If you are moving from one SQL server to another SQL server, the collation settings of the Aftermail_temp table and the Archive Manager database itself must match what existed when the Archive Manager database was first created.