Backing up and restoring the team solution components on your server makes it possible to safeguard the information in your solution 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 solution to that state if any part of the solution is lost or corrupted.
Because a team solution 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 solution, 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 solution.
For best results, you should back up both your solution and system databases regularly using standard database backup tools. For detailed information about creating back up copies of SQL Server databases, see "Backing Up and Restoring Databases" in the SQL Server Books Online.
Your team solution consists of the modSystem database and the individual solution databases. For best results, back them all up at the same time to avoid loss of data. The modSystem database stores information about each of your team solutions.
Warning Whenever you back up a solution database, you should also back up the modSystem database. If you do not back up the modSystem database, you may lose information about any solutions added since the last backup. If you lose information about any solutions, use the Access Workflow Designer to register them again.
Because the Web site is 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-displaying 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.