How to Move the Archive Manager SQL Database from One SQL Server to another. (4218480)

How to Move the Archive Manager SQL Database from One SQL Server to another.

N/A

Moving the Archive Manager Database (AM) will require the move of the actual files, keeping the security permissions, and moving of the jobs associated with this database.
The location of the MDF and LDF files for both the Aftermail_Temp and the Archive Manager Databases can be found under each of their property pages in Enterprise Manager (SQL 2000) or Management Studio (SQL 2005).

IMPORTANT: Do not move the AM Database to a Server that has a different Collation than the original Server/Database. This WILL cause issues and be unsupported.

Please note: When upgrading/reinstalling/moving Archive Manager, on the "Archive Manager Installation Targets" window of the installer, you are given three options under "What do you wish to do?".

Be sure to select "Install a new Archive Manager instance in my company" and choose "Full (All Options - Advanced Installs)" from the drop down menu.
 

1. Ensure that the new database server is available to the current AM system. Same domain and such.
2. Stop all Archive Manager Services. Stop the IIS server.
3. Detach both Archive Manager Databases.
4. Run the Archive Manager installer from the current Archive Manager Server.
5. Keep the same installation parameters during the installation, except for the SQL server information. Change this to reflect the new DB Server. NOTE: You must UNCHECK "Start Services After Installation" You do not want the services starting once the installer is finished.
6. Detach the Databases on the new server that were created by the Installer.
7. Move the original database MDF and LDF files of the recently detached Databases (done in step 3) and overwrite the files that were created by the installer.
8. Attach the old DBs.
9. Create a new share on the new SQL server called "FTITempPath". Grant all Archive Manager user accounts full permissions to this folder.
10. Update the "Full Text Index Temp Path" in the Archive Manager Configuration Editor. This should point the to UNC path of the newly created share, for example \\SQLServer\FTITempPath.
11. Start the Archive Manager services and watch the event log for errors relating to SQL.

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. As long as the two settings are maintained as specified for Archive Manager, the SQL server that houses the Archive Manager database may have a different collation setting that may be needed for other purposes on that machine. The supported collation setting is: SQL_Latin1_General_CP1_CI_AS

Additionally, if using a multi domain model and use a Domains.xml/ADCConfig file, it will need to be edited to reflect the location of the new server.

If there are any issues after this process contact Quest Software Technical Support.