David
Wed Nov 30 00:10:59 CST 2005
It still depends. For example:
1. Website configuration (the mapping of IP:Port:Host to a root application)
is IIS Configuration. However, the files on the filesystem that the root
application points to is NOT IIS Configuration
2. Virtual directory configuration (the mapping of URL namespace to physical
namespace) is IIS Configuration. However, the files on the filesystem that
the physical namespace points to is NOT IIS Configuration
3. Security settings (choice of authentication
[anonymous/basic/Integrated/etc authentication], authorization
[Read/Write/DirBrowse/ScriptSource/etc], and execute mode
[none/script/executables]) are IIS Configuration. NTFS ACLs on files are NOT
IIS Configuration
4. SSL consists of certificates (these are owned by the OS and not part of
IIS Configuration) and SSL Bindings between IP:Port and Certificate (these
are part of IIS Configuration).
What this means is that copying the metabase only takes care of backing up
"IIS Configuration". You still need to take care of your non-IIS
dependencies such as:
- files on the file system
- file system ACL
- Registry keys and ACLs used by 3rd party components
- COM+ components
- Server-Side ActiveX controls
- The SSL Certificates used by SSL-enabled websites
- etc
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Bob" <spamfree@nospam.com> wrote in message
news:udXmHQ%237FHA.2152@TK2MSFTNGP10.phx.gbl...
I mean backing up the IIS configuration of websites, virtual directories,
security settings, cert settings, etc.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:eHz6HOa7FHA.3864@TK2MSFTNGP10.phx.gbl...
> Can you define what exactly you mean by "backing up the IIS" since it has
> very little practical meaning.
>
> Are you talking about IIS configuration (which includes the IIS website
> definitions, bindings, URL-to-Physical mappings, redirections), COM+
> configuration, FileSystem configuration (this includes the content for
your
> website, ISAPI Filters/Extensions, etc), any dependent COM components/DLLs
> that webpages on your websites require, etc.
>
> If you want a sure way to backup everything, then use tools like NT Backup
> to backup the entire system.
>
> If you want to partially backup a server, then you need to define what
> exactly you want to backup and then just do that.
>
> For example, backing up IIS Configuration is a simple matter of copying
> %systemroot%\system32\inetsrv\metabase.bin . However, realize that the
> backup files become invalid if you subsequently reinstall IIS or change
the
> machine key (like via DCPROMO) since the configuration file contains
secured
> values (like user passwords used for UNC User, Anonymous User, etc). And
> backing up IIS Configuration does not mean any other dependencies of your
> website (like files, Components, etc) are accounted for -- you have to
> determine and back them up somehow as well.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Bob" <spamfree@nospam.com> wrote in message
> news:uaZ5u4R7FHA.808@TK2MSFTNGP09.phx.gbl...
> Can you suggest a "best practice" way of backing up the IIS?
>
> Thanks!
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:eHCrH8L7FHA.3684@TK2MSFTNGP12.phx.gbl...
> > Did you "corrupt" the metabase such that you cannot retrieve
configuration
> > stored within it, or is the metabase contain invalid values such that
IIS
> > does not function properly.
> >
> > The only way to "uncorrupt" something is to replace it with a known good
> > backup.
> >
> > --
> > //David
> > IIS
> >
http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > //
> > "Bob" <spamfree@nospam.com> wrote in message
> > news:OrFlExL7FHA.2692@tk2msftngp13.phx.gbl...
> > Is there a way to uncorrupt an IIS 5.0 metabase? We somehow corrupted
it!
> > :-(
> >
> >
> >
>
>
>