Manage Duet Enterprise backup and recovery (Duet Enterprise)

  • Article

 

Applies to: Duet Enterprise for Microsoft SharePoint and SAP

This article describes the backup and recovery processes that are available for Duet Enterprise for Microsoft SharePoint and SAP. Since Duet Enterprise runs as a Duet Enterprise SharePoint Add-on, the backup architecture and recovery processes depend completely on Microsoft SharePoint Server 2010 and the version of Microsoft SQL Server that you deploy, either SQL Server Standard or Enterprise, 2008 or 2005.

In this article

  • Backup systems available for MOSS_2nd_CurrentVer

  • Special thisProduct_2nd_CurrentVer backup considerations

  • Web application restore considerations

Backup systems available for SharePoint Server 2010

There are two backup systems available in SharePoint Server 2010 -- you can back up the whole farm or you can back up just the specific service application and database, if you need to. A farm backup architecture deploys a SQL Server backup of content and service application databases and also writes configuration content to files. Consider that there are multiple stages involved in planning for backup and recovery of a SharePoint Server 2010 environment. Note also that many service application databases cannot be backed up individually from Duet Enterprise; instead you must use SQL Server backup. See Backup and recovery overview (SharePoint Server 2010) (https://go.microsoft.com/fwlink/p/?LinkId=202093) for more information. Also see Plan for backup and recovery in SharePoint Server 2010 (https://go.microsoft.com/fwlink/p/?LinkID=139025) for more information about how to plan your Duet Enterprise backup and recovery processes. Download the SharePoint 2010 Products backup and recovery planning workbook (https://go.microsoft.com/fwlink/p/?LinkID=184385).

See the following articles for more information about the backup and recovery systems that you can use with SharePoint Server 2010:

After planning which backup and recovery process that you want to use for Duet Enterprise, refer to Backup and recovery for SharePoint Server 2010 (https://go.microsoft.com/fwlink/p/?LinkId=202095) for detailed information.

Special Duet Enterprise backup considerations

There are two specific tasks that the Duet Enterprise administrator may have to back up before upgrading or uninstalling and reinstalling Duet Enterprise.

  • The DuetConfig.exe.config file contains parameters that the administrator specifies when the administrator is configuring the Duet Enterprise solutions. If you have to uninstall and reinstall Duet Enterprise, although usually this is never required, any parameters that are specified in the DuetConfig.exe.config file are deleted. If you want to reuse these specified parameters when you configure the Duet Enterprise solutions again, you should backup the DuetConfig.exe.config file.

  • Duet Enterprise administrators can use the Business Data Connectivity service to define custom actions on entities. For example, an administrator can define that "show related contacts" is a custom action for the "customer" entity. If any custom actions are defined on the Business Data Connectivity service, the administrator must manually copy these custom actions and read them before they import the Duet Enterprise models.

  • There is a possibility that Duet Enterprise solutions will not be restored when the Web applications are restored. Because of this, we recommend that you maintain a list of the solutions that are deployed to each Web application. You can obtain a list of the deployed Duet Enterprise solutions by typing the DuetConfig.exe /CheckConfiguration command in a Command Prompt window and saving the XML output file every time that you change the Duet Enterprise configuration.

For more information about how to back up a Web application, see Back up a Web application in SharePoint Server 2010 (https://go.microsoft.com/fwlink/p/?LinkID=203218).

To view solutions deployed in a Web application

  1. In Central Administration, click System Settings.

  2. Under the Farm Management group, click Manage farm solutions. The Solutions Management page displays the solutions that are currently in the farm.

Web application restore considerations

There are two specific tasks the Duet Enterprise administrator should address after restoring a Web application that has been enabled for Duet Enterprise.

  • After restoring Duet Enterprise enabled Web applications, you may have to redeploy the solutions to the Web application.

  • After restoring Duet Enterprise Web applications, you must reapply the authentication settings to make sure that the settings are restored correctly.

For more information about the solutions provided with Duet Enterprise, see List of solutions (https://go.microsoft.com/fwlink/p/?LinkId=205306).

To deploy Duet Enterprise solutions to a Web application

  1. Open an elevated Command Prompt (Run as administrator) and then go to the Duet Enterprise folder. The default path is C:\Program Files\Duet Enterprise\1.0.

  2. For each solution to be deployed, use the following command:

    DuetConfig.exe /ConfigureSolution "<SolutionName>" /WebAppUrl "<RestoredWebAppUrl>"

    Where:

    • SolutionName is the name of the solution to be deployed. You should maintain a list of the deployed solutions for each Web application when you perform the backup to make this step easier. For more information, see Special thisProduct_2nd_CurrentVer backup considerations.

    • RestoredWebAppUrl is the URL of the Duet Enterprise Web application that was restored.

To reapply authentication settings after a Duet Enterprise restore

  1. In Central Administration, under the Application Management group, click Manage web applications.

  2. Select the Web application, and then click Authentication Providers.

  3. On the Authentication Providers page, click Default.

  4. On the Edit Authentication page, click Save. You do not have to make any changes to settings on this page; saving them will ensure that they are enforced correctly after the Web application is restored.

  5. Close the Authentication Providers window.