Farm Recovery

The Farm Recovery is performed to prevent problems that might occur (like data loss or interruptions to organizational operations) and to allow quick recovery.

The following are the files required to be backed up from the folder:

• [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Bin: All the Work Tasks dlls and any custom dlls (if added)

• [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Locales folder: For UI Localization

• [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Web\BPMUITemplates folder

• [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\WorkflowElements folder

• Farm Database

• Repository Data Source Database

Notes:
- The Farm Recovery is supported for both HTTP and HTTPS protocol based sites. The HTTPS sites get recovered if the target machine has the same SSL certificate as in the source machine. Otherwise, the sites will get recovered in HTTP mode. After the recovery, edit the Security Settings page in Farm Configuration Wizard and update the certificate to configure the sites in HTTPS mode.

- After the Farm Backup and Recovery, you need to do the following:
-- Register the token service again and then redeploy the Quickflow application. For information on deploying Quickflow, see Deploy Quickflow. Ensure the primary System Management Server (SMS) is online during token service registration and redeploying the Quickflow application.
-- For OAuth2 authentication, update the Redirection URI in SMTP Settings and POP3 Settings in the Mail Server page with the server name on which the Farm Recovery was performed.

Overview

All AVEVA Work Tasks files are located in the AVEVA Work Tasks folder. If a backup is required for the AVEVA Work Tasks installed server machine then copy all the files located in the AVEVA Work Tasks folder. Before taking a backup, ensure that all the Services (Engine, Task Scheduler, and Communication Service) have been stopped and the product has been deactivated.

Restoring AVEVA Work Tasks Files

Before you restore AVEVA Work Tasks files to a different or on the same machine (from which a backup was taken), the AVEVA Work Tasks has to be installed again and activated. During the installation, AVEVA Work Tasks Web sites will be created again. Ensure that the customized data is replaced correctly.

The Farm database can be connected using the Farm Manager utility and the data source can be updated using the Central Configuration Web site.

After the installation, replace all the existing AVEVA Work Tasks files with the backup files. This will ensure that any customization done for XML files, images and Html templates have been replaced as before. Replacing existing AVEVA Work Tasks files will also ensure that any custom actions or properties or dlls added are replaced correctly. The BPMUITemplates folder must be replaced under the [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Web path.

Note:
- Ensure that the dlls present in GAC and in [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Bin are the same.

-The Central Configuration and the Enterprise Console will always be created under DefaultWebsite/AVEVAWorkTasksSites after the recovery of the Farm database.

Farm Recovery Scenarios

The scenario descriptions have been described under the following sections:

Server

• when the Server machine goes down

• when the Farm Database goes down

• when both machines go down

• when any one machine goes down

Client

• when the Client machine goes down

Recover Client

• Repository database Recovery

Server

• When the Server machine goes down

Recovery of the Services and the Farm database that are on the same machine

Prerequisites: Take a backup the Farm database.

1. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

2. Right-click Farm Configuration Wizard, and then click Run as administrator.

   The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

3. Click AVEVA Work Tasks Farm Recovery.

   The Recovery Type screen appears.

4. Select the Server option to be recovered from Server or Client options displayed on the screen.

5. Select all the recovery types displayed under the Server option:

   • Database Settings

   • Services

   • Central Configuration and Enterprise Console

6. Click Next.

7. After a successful connection to the database, if the current server's name does not exist in the database, enter the Server name to be replaced.

   The Services will get installed and the Central Configuration and the Enterprise Console get created.

   A confirmation message appears.

   Note: Central Configuration and the Enterprise Console are always created under DefaultWebsite/AVEVAWorkTasksSites.

Recovery of the Services and the Farm database on different machines

The Services are installed in machine1 and the Farm database exists in machine2.

Server machine goes down: In this case, only server machine containing the Services is crashed but the Farm database is up.

8. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

9. Right-click Farm Configuration Wizard, and then click Run as administrator.

   The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

10. Click AVEVA Work Tasks Farm Recovery.

11. Select Server from Server and Client options displayed on the screen.

12. Check all the recovery types displayed under the Server option: Database Settings, Services, and Central Configuration and Enterprise Console.

13. Click Next.

    Note: Central Configuration and Enterprise Console will always be created under DefaultWebsite/AVEVAWorkTasksSites.

14. Under Connection string, enter the details for the Farm database stored on machine2.

    After a successful connection to the database, if the current server’s name does not exist in the database, enter the Server name to be replaced. The services get installed and the Central Configuration and the Enterprise Console get created. A confirmation message appears.

Farm Database machine goes down

This section describes the scenario when the machine, on which the Farm database resides, crashes while machine1, where the Services is running, is fine.

Prerequisites: Take a backup of the Farm database.

15. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

16. Right-click Farm Configuration Wizard, and then click Run as administrator.

    The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

17. Click AVEVA Work Tasks Farm Recovery.

18. From the Server and Client options, select the Database recovery check box.

19. Click Next.

20. Provide Connection string details for the Farm database that needs to be restored.

When both the machines go down

Refer to the scenario, Recovery of AVEVA Work Tasks Services and Farm database that are on the same machine.

Moving the Farm database from one machine to another machine

This section describes the recovery in the scenario when you move the Farm Database from one machine (source) to another machine (the destination).

Prerequisites: Take a backup of the Farm Database (from the source machine) and restore it to the destination machine.

21. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

22. Right-click Farm Configuration Wizard, and then click Run as administrator.

    The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

23. Click AVEVA Work Tasks Farm Recovery.

24. From Server or Client options, select the server to be recovered.

25. From the Server options, select the Database recovery check box.

26. Click Next.

27. Provide Connection String details for the Farm Database that needs to be restored.

Any Server machine goes down

In this scenario, temporarily shift the machine to some other machine. After the original server is up, shift back to the original server from the temporary machine.

To recover any server machine

Refer to the scenario, AVEVA Work Tasks Services and Farm database on one machine for Solution.

You must run the Farm Recovery options twice in this situation:

• The first time will be in the temporary machine

• The second time will be on the original machine

Client

28. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

29. Right-click Farm Configuration Wizard, and then click Run as administrator.

    The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

30. Click AVEVA Work Tasks Farm Recovery.

31. From Server and Client options, select the Client to be recovered.

32. Provide Connection String details for the Farm database.

    The Central Configuration and the Enterprise Console get created.

Note: Central Configuration and Enterprise Console always get created under DefaultWebsite/AVEVAWorkTasksSites.

Farm Recovery

This section provides technical specification details for developers in order to provide a solution for Farm Disaster Recovery.

33. On the Windows Start menu, point to Programs, point to AVEVA, and then select Farm Configuration Wizard.

34. Right-click Farm Configuration Wizard, and then click Run as administrator.

    The Welcome to the AVEVA Work Tasks Farm Configuration Wizard screen appears.

35. Click AVEVA Work Tasks Farm Recovery.

36. Choose one of the options displayed on the screen. If you choose server then check one of the options as described below:

    • Recover Database: The Database User Settings page appears. On successful database connection this will create the CentralConfig.xml file.
      
      If the current server's name does not exist in the database, choose the Server Name to be replaced with any server from the Farm Database's Server Collection. This collection will only contain the servers that are currently not running.

      • Database changes

      • SKServer table – Name and Address will get replaced with current server's name.

      • SKService table – WorkflowManagementGlobalSettings – property smtphost, filewatcherip.

      • SKWebsite table – property localURL of each website.

      • SKServicemapping table - SMTPNotificationEngine2 – property listnerip, smtpserverip, pophost.

    • Recover Services: Load the properties of Services from the Farm database and install services.

    • Recover Central Configuration and Enterprise Console.

      • Load the AVEVA Work Tasks Web site properties.

      • If the path of the Web site does not exist then the local URL of the site is changed to the path of DefaultWebSite/AVEVAWorkTasksSites and other properties of the site are updated accordingly.

      • Create Central Configuration and Enterprise Console according to properties from the Farm database.

To recover Client

37. Provide the database connection option.

38. If the current client's name does not exist in the database, choose Client Name to be replaced with any server from Farm Database's Client Collection. SKServer table entry for client will get changed.

39. Recover Central Configuration and Enterprise Console.

    1. Load AVEVA Work Tasks Web site properties.
       If the path of the website does not exist then the local URL of the site is changed to the path of DefaultWebSite/AVEVAWorkTasksSites and other properties of the site are updated accordingly.

    2. Update AVEVA Work Tasks website properties accordingly.

    3. Create Central Configuration and Enterprise Console according to properties from Farm Database.

To recover Repository Database

Repository database information is stored in the Farm database. If the database server is changed, edit the changes from the Central Configuration Web site and update the changes.

To recover Quickflow

Deploy Quickflow again from the Central Configuration Web site to have the Quickflows running.