ViSi Commander Disaster Recovery Planning

Database Server

• SQL Server

Daily Full Backup of the VISICMDR Database
Backups must not be stored locally on the same server. It is recommended to have the backup file stored on another host server.

Reporting Server

• SQL Server Reporting Services (SSRS)

Option 1

Go with this option, if you have a DBA experienced with SSRS Configuration, Backup and Restore. MathCraft doesn't provide support on Disaster Recovery restoration for SSRS or SQL Server.

Daily Full Backups of the ReportServer and RepoerServerTempDB databases.
Backups must not be stored locally on the same server. It is recommended to have the backup file stored on another host server.

Ensure you have backed up the Encryption Key via the SSRS Configuration Manager.

Option 2

Recommend taking a backup/snapshot of the Virtual Machine/Server once every month and every time a new Report Template is deployed or SSRS Web Portal has changes made.

Application Server

• IIS

• ViSi Commander Application and API

  • Eureka

  • Zuul Gateway

  • Auth Server

  • Report Service

  • API

  • ViSi Commander

Recommend taking a backup/snapshot of the Virtual Machine/Server once every month and every time a new version has been deployed or a patch has been deployed.

Scenario 1

Database was restored to a new Server and DNS/Machine Name has changed

1. DBA restores the VISICMDR database to the new server

2. Login to the SSRS Web Portal via the browser

3. Edit the VISICMDR_DS Data Source under VCReports Folder and update the Connection String

4. Stop ViSi Commander services and IIS Site in the Application Server

5. Navigate to ViSiCmdrTC\visicmdr\conf directory and edit the common.properties file using NotePad++

6. Update the Database Server Name in the variable property jdbc.url

7. Save the File

8. Navigate to AccessCommanderAPI\Configuration\ReportServer directory and edit the application.properties file using NotePad++

9. Update the Database Server Name in the variable property spring.datasource.url

10. Save the File

11. Start API-ACv4-Eureka; API-ACv4-Zuul; API-ACv4-ReportService; and API-ACv4-APIService services

12. Turn on the ViSi Commander site in IIS only.

Scenario 2

Database was restored to a new Server and DNS/Machine Name was not changed

DBA restores the VISICMDR database to the new server

Scenario 3

Reporting Server was restored to a new Server and DNS/Machine Name has changed

1. Launch SQL Server Management Studio and restore the ReportServer and ReportServerTempDB databases

2. Launch SSRS Report Server Configuration Manager and point to the restored database and proceed with configuration of Web Service URL and Web Portal if applicable. Restore the Encryption Key as well.

3. Stop Report Service in the Application Server

4. Navigate to AccessCommanderAPI\Configuration\ReportService directory and edit the application.properties file using NotePad++

5. Create an account for SSRS User/Admin either locally or via Active Directory.
   The previously used account credentials (Active Directory or Local Account) can be found in the property variables ssrs.userid and ssrs.pwd

6. Update the Database Server Name in the variable property ssrs.wsdl
   If you make changes to the credentials, update the respective property variable values ssrs.userid and ssrs.pwd

7. Save the File

8. Start API-ACv4-ReportService servics

Scenario 4

Reporting Server was restored to a new Server and DNS/Machine Name was not changed

Option 1

Your DBA will need to perform the restore actions

Option 2

Restore the Virtual Machine/Server

Scenario 5

App Server was restored to a new Server and DNS/Machine Name(s) has changed

1. Restore the Virtual Machine/Server

2. Stop all ViSi Commander services and IIS Sites in the Application Server

3. Navigate to ViSiCmdrTC\visicmdr\conf directory and edit the common.properties file using NotePad++

4. Update the FQDN in the variable property visi.hostname

5. Save the File

6. Start ViSiCommander service

7. Start the IIS Site

Scenario 6

App Server was restored to a new Server and DNS/Machine Name was not changed

Restore the Virtual Machine/Server