[This is preliminary documentation and subject to change]
IIS provides three methods to back up the metabase. Using Configuration Backup/Restore, you can create a secure backup or insecure backup of your metabase. With the new functionality to Configuration Backup/Restore in the IIS snap-in, Web site administrators can also restore copies of the metabase to other computers. These back up methods provide a way to restore only your metabase settings, not your content files. As with previous versions of IIS, you can programmatically create a legacy backup of the metabase; however, you can not restore legacy backups of the metabase to other computers.
Secure Backup
Using this method, the Web site administrator provides a password
that is then used to encrypt the metabase backup. Password
information is stored in the metabase backup header, which
indicates a password was used to create the backup. After the
password is encrypted and stored in the metabase backup, the
password cannot be changed. Only administrators who know the
password can restore the metabase backup. See the To create a
secure backup (Password Required) section below.
Insecure Backup
Using this method, the Web site administrator chooses not to supply
a password. The metabase backup is encrypted with a blank password
and anyone can restore the metabase backup. See the To create an
insecure backup (Password Not Required) section below.
Legacy Backup
Using this method, the Web site administrator can create metabase
backups programmatically. However, legacy back ups must be restored
either programmatically or by using Configuration Backup/Restore
from the IIS snap-in.
Important
The legacy back up method is not recommended
and therefore not described. When you create backups
programmatically, IIS implements the legacy method used in IIS 5.0.
Therefore, you can only restore legacy metabase backups to the
operating system on which the backup was created.
\Winnt\System32\Inetsrv\MetaBack directory.Related Topics