[This is preliminary documentation and subject to change]
IIS provides new functionality to Configuration Backup/Restore located from the IIS snap-in. Web site administrators can restore copies of a secure or insecure backup of the metabase to other computers. You can also restore the metabase using the legacy method.
Restoring a secure backup The password is stored within the metabase backup and used to encrypt the session key. This password cannot be changed, and if forgotten, renders that metabase backup un-usable.
Restoring an insecure backup Metabase backups are not password protected. Anyone can restore an insecure backup to any computer.
Restoring a legacy backup The legacy methodology uses the machine key (unique to a particular installation of the OS) and the system key (generated by IIS) to encrypt the backup. Therefore, legacy metabase backups can only be restored to the same installation of the operating system (OS) that they are created from.
Content Files Configuration Backup/Restore does not save your content files. When restoring the metabase backup to a different server, you must copy your content files as well. Also, the content files must exist on the same drive letter that was used by the original server.
SSL Certificates If you use an SSL (secure socket layer) Certificate on your Web server and restore the metabase backup to a different installation of the OS, an error occurs if the certificate is not available or installed. If a site's SSL Certificate is missing, connections are dropped, and IIS displays a "page unavailable" error. The server logs the following warning in the event log: The solution is to reinstall the certificate into the same certificate store and restart IIS. Failure to restart IIS after reinstalling the certificate results in continued error logs and dropped connections. For more information about installing SSL Certificates, see Setting Up SSL on Your Server.
Related Topics