Skip to main content

Metabase and IIS 6.0 Backup-Restore


Metabase (IIS 6.0)


The metabase is a structure for storing Internet Information Server (IIS) configuration settings. It performs some of the same functions as the Windows system registry but is specific to Internet Information Server version 4.0. New keys and values have been added for finer and more flexible control of IIS.
Like the registry, the metabase is organized in a hierarchical structure that mirrors the structure of your IIS installation. It is made up of nodes, keys, and subkeys. The main organization is by node, with each node in the metabase structure representing a site or directory. Beneath the nodes are keys that may contain one or more IIS configuration values called metabase properties. The metabase keys correspond to individual configuration elements of IIS; each key contains properties that affect the configuration of its associated directory or site.
Many of the metabase parameters can be configured from the Internet Service Manager snap-in for the Microsoft Management Console (MMC). Additional tools are also available for further tuning of the metabase.


Backing Up and Restoring the Metabase in IIS 6.0 

We can create backup files using IIS Manager or a programmatic administration script. The backup files are copies of the metabase configuration file (MetaBase.xml) and the matching metabase schema file (MBSchema.xml). Using the metabase configuration backup and restore feature, the metabase can be restored from the backup files.

To create a  backup 
  1. In IIS Manager, right-click the local computer, point to All Tasks, and click Backup/Restore Configuration.
  2. Click Create Backup.
  3. In the Configuration backup name box, type a name for the backup file.
  4. Click OK, and click Close.


To restore the metabase backup

  1. In IIS Manager, right-click the local computer, point to All Tasks, and click Backup/Restore Configuration.
  2. In the Backups list box, click the version of the Automatic Backup file that you want to restore, and click Restore. If prompted for a password, type the password you chose to secure the backup.
  3. When a confirmation message appears, click Yes.
  4. Click OK, and then click Close.

Thanks and Regards
@sumanJha
Labels:

Comments

Post a Comment

Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...
34 comments
Read more

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription 
29 comments
Read more

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.
28 comments
Read more