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

Comments

Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure”

I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps.

Remove all relevant namespace files from data-file route path..Now repair mongo instance using mongod process.mongod --repair ////////// execute command from bin folder path Then start server using mongd process, if started server successfully then ..mongod  ////////// execute command from bin folder path Restore last backups as normal process.Now check database by connecting mongo shell. Thanks for reading, 
Please comment your experience if you faced and also share knowledge if you have better steps to resolve...


https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option.

After connecting to SQL Azure portal when operation started to deployment below errors occurs.

Validation of the schema model for data package failed. Error SQL71562: Error validating element xx.xxx.xx:function .dbo.xxx has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform.



Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming.

Solution : I suggested him to create those function to locally on local database what…

How to recover msdb database from suspect mode

It was Monday 9th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server.
“MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..