How to backup IIS 6.0 Configuration to work across different Servers?

Question

Ok. Cloud Computing is the new kid in the block. And Our company is getting into it really quickly. Not so much for the price benefit, but for the process management perspective. I am in the process of moving an IIS 6.0 server running in Windows 2003 Server. The IIS Engine has many Web Sites adn each Web Sites has Virtual Hosts configured, with Application Pools and all that good stuff.

I am backing up the IISPUB directory but since everything is running in the cloud now, I will like to make sure that if one day I come in and the server is completely gone. So the only thing that I have is the backups, I can recreate fairly easy the full scenario. I am trying to bind all Websites to All IPs so If the IP gets reassigned all will still works.

I know that the MetaBase is the file holding the configuration, what I don't know is how to backup that file often. Has any of the fellow IT Admin gotten into this situation before?

Solution 1

The IIS metabase inn IIS6 is part of the servers system state, so to back it up, backup the system state, which you are most likely doing anyway.

If you want to just backup the metabase file on its own, you can do so using IIS manager, or by using the IISback.vbs script. See this Microsoft KB article for instructions.

Solution 2

if you want to schedule the backup the metabase, you can use IISBack.vbs script that should have been installed at /System32 folder.. backup to a file and make sure you're backups slurp up the metabase backup.

edit: on a side note - don't forget to backup certificates and, depending on the age of your applications, any COM+ components as well.

Comments

[bassen]

I tried the command below: C:\WINDOWS\system32>IIsCnfg.vbs /export /f d:\Configuration-Backup\metabase-export.xml /sp /lm/root /children /inherited And I get the following message: Connecting to server ...Done. Error while exporting configuration. The system cannot find the path specified.

[Mike Fiedler]

Apologies - I mistyped the syntax of the /sp (SourcePath) argument. Fixing in topic