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.
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:
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.
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.
STEP 5
Set Security for your Archive Manager Accounts.
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.
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.
© ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center