Metabase Import and Export (IIS 6.0)
The metabase import and export feature enables administrators to create an export file, named MetaBase.xml by default, which contains specifically selected elements of a metabase configuration file. This export file can later be imported into the metabase configuration file of the same computer, or to another computer running Windows Server 2003.
Additionally, you can use the metabase export feature to create a metabase template, which can be used to configure multiple computers with the same IIS configuration settings, excluding machine-specific and system-specific information. For more information about metabase templates, see Restoring a Section of the Metabase.
Metabase export does not replace the functionality of metabase backup. You use metabase backup to create a backup file of the entire metabase configuration and schema, which can be restored only in its entirety (including encrypted properties). Metabase export does not export the metabase schema.
Neither metabase backup nor export can be used to save or copy content files, scripts, or binaries. To back up your entire server — including content files, scripts, and binaries — use Windows Backup. To simply copy these files to a new location, use Windows Explorer or the Windows xcopy command. Remember to reregister any components that you copy to a new computer.
Specifying Metabase Elements for Import or Export
You can import and export the following metabase elements:
Importing and Exporting a Metabase Element
To import or export a metabase element, you can use any of the following:
Regardless of whether you use a programmatic interface, a script, or IIS Manager to import and export metabase elements, there are specific choices you must make. The following list outlines both the required and optional steps needed to import and export a metabase element. The inheritance and merge options are discussed after the list. When a metabase element is exported, IIS creates an XML file that contains the exported element.
Before exporting a metabase element
Before importing a metabase element
Setting Inherit and Merge Flags
If you set the inherit flag during a metabase export, inheritable properties that are applicable to the metabase element are saved as part of the export file. If the inherit flag is set during an import operation, these inheritable properties are imported into the metabase.
The behavior of importing inheritable properties differs, depending on whether the merge flag is used along with the inherit flag.
Inherited properties in the destination metabase affect the configuration of all sites. Use caution when you import a metabase element without using the inherit flag. To avoid unintended changes to other sites, import to a unique location that has no child nodes.
Exporting Lower-Level Child keys
When specifying a metabase element to export, you can optionally export lower-level child keys. If an element is exported by using this option, you can optionally import the element and all recursive child keys.