Backing Up and Restoring a Content Management Server 2001 Site

Published: May 2001
By Vincent Liew

Microsoft Corporation


This article covers the procedures and practices used to back up and restore a Microsoft® Content Management Server (MSCMS) 2001 site. It specifically outlines the backup and restore process for a Microsoft SQL Server database.

On This Page

Introduction Introduction
Prerequisite Knowledge Prerequisite Knowledge
Options for Backing up a MSCMS 2001 Site Options for Backing up a MSCMS 2001 Site
Additional Backup Considerations Additional Backup Considerations
Restoring a SQL Server Database Restoring a SQL Server Database
Conclusion Conclusion


This article is intended for Microsoft Content Management Server 2001 System Administrators or anyone who is responsible for backing up a MSCMS 2001 site. This includes the backing up of any file structures associated with the site, such as the \NR directory which is a default folder that contains include files and ASP files that the site may reference.

Prerequisite Knowledge

This article assumes an understanding of the following:

  • General Microsoft MSCMS 2001 2001 knowledge

  • General Microsoft SQL Server installation and setup knowledge

  • General knowledge of the Microsoft SQL Server Enterprise Manager

This article also assumes that you have a "newly built" sever, with the necessary operating system (OS) and software to support a MSCMS 2001 site as follows:

  • OS – Microsoft Windows NT or Windows 2000 and specifications listed in the MSCMS 2001 Setup Guide.

  • Database server – Microsoft SQL Server 7 or Microsoft SQL Server 2000

  • MSCMS 2001 and MSCMS 2001 Site Builder

Options for Backing up a MSCMS 2001 Site

The two main methods for backing up or transferring a MSCMS 2001 site are:

  1. Backing up the SQL Server database

  2. Using the MSCMS 2001 Site Deployment Manager to export the site

For simple backup and restore procedures, a SQL server backup is the recommended practice, as it will allow faster backups and restores. Additionally, this is a procedure that your database administrators will already be familiar with. The MSCMS 2001 Site Deployment Manager provides more options for export and import operations, however it requires more time and somewhat greater server overhead to create or import Resolution Object Package (ROP) file. The Site Deployment Manager is generally preferred for performing full or partial-site deployment between different server environments.

Backing up the SQL Server Database

The most important consideration when backing up a MSCMS 2001 site is the SQL Server database, which contains all the data that makes up the site. To back up the site, we will use the SQL Server Enterprise Manager to create a BAK file of the MSCMS 2001 SQL Server database. The following screen shots lead you through creating a SQL Server database backup.

  1. Open a Microsoft SQL Server Enterprise Manager console on the database server used by your Resolution system.

  2. Right-click the database to be backed up. Select All Tasks and scroll to the Backup Database option.

    Figure 1: SQL Server Enterprise Manager: Backup Database option
  3. When the Microsoft SQL Server Backup window opens, select the MSCMS 2001 SQL Database to be backed up.

    Figure 2: SQL Server Backup database selection

We will do a complete database backup and leave all the default settings. Click the Add button to continue.

When the backup destination windows opens, browse to where you want the backup file to be saved. (Here you can specify a destination folder or backup device.) You can either type the direct path to the drive or destination or you can use the browse button.

Figure 3: Select Backup Destination browse button

The Options tab allows for additional customization when running the backup process. You can set verifications, back up expiry times and much more. However, if you are running a basic backup of your database, there is no need to select these additional options.

Figure 4: SQL Server Backup Options

Automating a SQL Server Database Backup

To automate your Microsoft SQL Server database so it is regularly backed up, use the schedule setting in the SQL Server Backup window. Here you can set the frequency and time of backup of the Microsoft SQL Server database.

Figure 5: SQL Server Edit Schedule

Additional Backup Considerations

In addition to backing up the MSCMS 2001 SQL Server database, you will have to consider backing up any essential files or folders associated with your MSCMS 2001 site. Following is a list of considerations:

  • Include files – any include files that may have been added or are being referenced by a template. MSCMS 2001 templates support server-side file inclusions—an inclusion can be specified in a page template, for example <!--#include virtual="/navbar.asp"-->. Page templates can also consist of referenced ASP files.

  • WBC (Web Author) Customizable files – any changes and enhancements to these files by Customer or Professional Services, such as color of menus, font sizes, additional tools, and general look and feel of the editing menus.

  • Hot fixes or Patches – these may have been installed or added to your MSCMS 2001 site, and need to be re-applied when the site is restored.

The following screen shot shows where you would usually find or save your include files and find the Customizable folder. Include files are usually defaulted to the IIS_NR directory; however you can save them wherever you prefer.

Figure 6: WBC Customizable directory

Event Logging

A recorded log of events should be made while backing up a MSCMS 2001 site because there is no built-in log utility to track backup events. The person who did the actual site backup should compose it. This will allow anyone with administrative rights to fully restore the MSCMS 2001 site and prevent problems associated with having missed any key files or folders essential to site functionality.

Restoring a SQL Server Database

When restoring the Microsoft SQL Server database for a MSCMS 2001 site, it would be wise to reference the Event Log to ensure the whole site is restored and the proper files and folders are copied over to the newly setup server. This includes all the include files and customizable files associated with the particular MSCMS 2001 site.

Important: Any Hot Fixes or Patches should be installed or applied after restoring the SQL Server Database.

When you are ready to restore the Microsoft SQL Server database, you do not need to create a new database. You can restore over an existing one. Open the Microsoft SQL Server Enterprise Manager and create a new empty database or overwrite the old one by restoring on top of it. Now select the Restore Database option after right-clicking the database folder and selecting all Tasks. The Restore Database window is displayed.

Figure 7: Restore database

Select the location of the device or source of the backup (.bak) file and add it to the Devices name list.

Figure 8: Choose Restore Devices

After clicking the Add button you can type the full source path, or browse to it.

Figure 9: Choose Restore Destination

When you select the Options tab on the Restore database window, you must select the Force restore over existing database check box. This will force the restore of your backed up data to populate the empty database you created. After clicking OK, the database restore function should start.

Figure 10: Restore Database Options: Force restore over existing database


MSCMS 2001 is compatible with both Microsoft SQL Server 7, and Microsoft SQL Server 2000. There are no major differences between backup and restore interfaces for these two products. The look-and-feel of the menus and windows in Microsoft SQL Server Enterprise Manager is similar.