In my previous article I described the steps to upgrade a 32 bit Web Central Control installation to version 7.
Since the latest version of EVault Reports (2.71a) is only supported on 64 bit platforms, you will want to have your Web CentralControl running on the same platform.
The steps in this article describe migrating your existing 32 bit installation to a new 64 bit server.
Prepare WebCC databases
On your old WebCC server, shut down the Proxy services, AMP Redirector, Propagation, Task Service.
Backup your existing WebCC databases (SiteManagement, UserManagement, WebCC)using SQL Server Management Studio or another tool.
Take the WebCC installation down by taking the website down in IIS manager.
Prepare EVault reports databases
Launch SQL Server Reporting Services Configuration Manager. Connect to the server and select Encryption Keys. Select Backup, provide a password and a file location. Press OK
Copy the encryption key to the new server.
Launch SQL Server Management Studio and connect to the default instance. Right click on the VaultReporting,database and select Tasks > Backup. Back up the database to a file.Repeat procedure for ReportServer and ReportServerTempDB databases.
Next, detach the databases.
Right-click the ReportServer database and select Tasks then choose Detach and press OK. Wait for the task to complete. Repeat procedure for ReportServerTempDB and VaultReporting databases.
Note Your EVault reports database may be under a different name than VaultReporting.
Restore WebCC databases
Copy the database backup files from the 32 bit machine to the 64 bit machine. Then open SQL Server Management Studio and connect to the new SQL Server instance that the Web CentralControl 64 bit installation was targeting on the 64 bit system.
Select the SiteManagement database (which should be present from the fresh installation of Web CentralControl). Right-click, then select Tasks > Restore > Database making sure that SiteManagement is selected for the To database destination.
Under Source for restore, select From device. Browse to the file where the 32 bit SiteManagement database was backed up and select the most recent backup. (There should be only one backup in the file.)
Select Options from the left menu. Select Overwrite the existing database (WITH REPLACE).
Verify that the Restore As path is correct for your system then run the restore.
Repeat this procedure for the UserManagement and WebCC databases.
Migrate EVault Reports
Delete old databases
On the 64-bit server, go to Start > Administrative Tools > Services and stop the SQL Server Agent and SQL Server Reporting Services services.
Open SQL Server Management and connect to the local instance. Expand the databases and delete the following databases: EVaultReporting, ReportServer and ReportServerTempDB
Next, you have to move the 2.70 EVault Reports Database to the new server. The Databases must be moved to the new server, Not backed up and restored
Copy the detached databases from this step, both mdf and ldf files.
Back in SQL Management Studio, expand the instance and right click on Databases, and select Attach.
Select the VaultReporting, ReportServer and ReportServerTempDB .mdf file database in the Databases to attach field (select each individually).
Go to Start > Administrative Tools > Services. Start the SQL Server Agent and SQL Server Reporting Services services.
Change SQL Database Compatibility Mode
Open SQL Server Management and connect to the local SQL instance.
For each of the VaultReporting, ReportService and ReportServiceTempDB databases, right click and select Properties. Select Options and change the Compatibility Level to SQL 2008 (100) and save the changes
At this point, if you try and connect to the ReportServer URL (accessible through the Web Service URL field in the Reporting Services Configuration Manager), you may see an error like this: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is ‘C.0.8.40’. The expected version is ‘147’. If you see a different error than this please consult the EvaultReports migration guide.
Change SQL Database Network Service and System Users
Connect to local instance using SQL Server Management Studio then open the ReportServer database and go to the Security/Users section.
Remove the NT AuthorityNetwork Service and NT AuthoritySystem users. Click “Yes” at the prompt to remove the schemas as well as the users.
Right-click on the Users folder and select to add a New User. Select the NT AuthorityNetwork Service user for the login name (use the browse button).
Give the same name for the User Name. For the default schema, select dbo.
Under Database role membership select both db_owner and RSExecRole and click OK to save the user.
On the Schema folder, right-click to add new schema. For the schema name, use NT AuthorityNetwork Service. For the schema owner, select NT AuthorityNetwork Service. Click OK to save the user.
Repeat steps above for the NT AuthoritySystem user on the ReportServer and ReportServerTempDB databases
At this point, if you connect to the ReportServer URL you will see an error message like: The report server installation is not initialized.
Restore the Encryption Key
Open SQL Server Reporting Services Configuration Manager and connect to the SQL instance and select Encryption Keys. Select Restore then browse to the location where the Key file is that you backed up on the old server.
Provide the same password that was used when backing up the encryption key and click OK.
At this point, if you connect to the Report Service URL, you will likely see the error: The feature: “Scale-out deployment” is not supported in this edition of Reporting Services.
Remove erroneous encryption record
Open SQL Server management console and connect to the local instance.
Select the ReportServer database. Edit the top 200 rows of the Keys table. There will be two key records there. One with the name of the new system and one with the name of the old system. Remove the record with the name of the old system.
Repair Evault Reports
Run the EVault Reports 2.71 install kit Select Repair to update the restored database.
Complete the Install wizard to update the database to the 2.71 version.
At this point If you go to your SQL Server Agent, you should see the GUIDs for your Subscriptions. If this is not the case then your subscriptions were not migrated and you should double check each step.
Reassign External Addresses and Domains
At this point you should reassign the old IP/DNS name to the new server in order for the agent to connect to the same server.
Proceed to the next article if you are interested in upgrading EVault Director.