Share via

Backing Up and Restoring Workflow Applications

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Backing up and restoring the workflow application components on your server makes it possible to safeguard the information in your application in case problems occur. When you create a backup, you get a copy of the current state of the database and Web files at the time of backup. Then, you can use that copy to restore the application to that state if any part of the application is lost or corrupted.

Because a workflow application consists of two types of components, a database and a Web site, you have two areas to back up.

Tip   For an easy way to back up your application, you can create templates that include all data and all users. Then, by exporting the template to a file, you have a template file that can be used to recreate your application.

Backup of SQL Server Databases

Your workflow application consists of the modSystem database and the individual workflow-enabled databases. The modSystem database stores information about each of your workflow applications. For best results, you should back up all of your databases regularly using standard database backup tools. For detailed information about creating back up copies of Microsoft® SQL Server™ databases, see "Backing Up and Restoring Databases" in the SQL Server Books Online.

**Note   **Whenever you back up a workflow-enabled database, you also should back up the modSystem database. If you do not back up the modSystem database, you might lose information about any applications added since the previous backup.

Restoration of SQL Server Databases

When you restore a database associated with a workflow application from a backup, you must use the original database name. If you restore to another name, the Web site and internal workflow tables will not recognize the database.

Backup of Web Sites

Because the Web site is made up of a number of standard files stored on the server, you can use any file system to back up the Web site. In addition, because the majority of the Web pages are static HTML files that display dynamic data, it is not as important to back up the pages regularly. It is recommended you make a backup whenever you make any changes to the Web pages.

See Also

Managing the Server | Managing Workflow Applications | Creating New Applications from Templates | Moving a Workflow Application to a Different Server | Removing a Workflow Application from the Server | Managing Users and Roles | Synchronizing User Information | Editing User Information | Managing Templates