To back up and restore IIS configuration and websites, use the appcmd tool for server-level settings, manually copy critical files, and separately back up website content and databases. 1. Back up IIS config using "appcmd add backup" in Command Prompt as Admin. 2. Store backups in default history folder and version them. 3. Manually copy web.config, logs, SSL certs, and site directories. 4. Restore via "appcmd restore backup" after listing available backups. 5. Reinstall website files and databases separately during restore. 6. Ensure matching IIS versions on source and target machines. 7. For dynamic sites, back up databases using SQL tools. 8. Automate with scripts or third-party tools if needed. 9. Test backups regularly on a test server. 10. When migrating, install same IIS version, copy files and DBs, restore config, and re-link databases. 11. Adjust file paths if different between servers.

If you ever need to move your IIS setup, recover from a failure, or just want to be prepared for the unexpected, knowing how to back up and restore IIS configuration and websites is essential. It’s not complicated, but it does require attention to detail so nothing gets missed.

How to Back Up IIS Configuration

The easiest way to back up IIS settings is by using the built-in appcmd tool that comes with IIS. This saves the entire server-level configuration, including application pools, sites, and bindings.

• Open Command Prompt as Administrator
• Navigate to %systemroot%\system32\inetsrv
• Run: appcmd add backup "YourBackupName"

This creates a snapshot of the current IIS configuration. The backups are stored in the C:\inetpub\history folder by default. You can create multiple backups, and they’re versioned so you can roll back if needed.

Also, don’t forget to manually copy important files like web.config, custom logs, SSL certificates, and website content directories. These aren’t always included in the appcmd backup depending on where they’re located.

How to Restore IIS Configuration from Backup

Restoring IIS configuration is just as straightforward using the same appcmd tool.

• List existing backups with: appcmd list backup
• Restore a specific one using: appcmd restore backup "YourBackupName"

Keep in mind, this only restores the configuration — not the actual website files or databases. If you’ve moved servers or lost data, you’ll need to have your website content and databases restored separately before restoring the configuration.

Also, make sure the same version of IIS and related modules are installed on the target machine. Restoring to an older or different version might cause issues or missing features.

Backing Up Website Files and Databases

While backing up IIS config is important, you also need the actual website files and any associated databases.

For static sites:

• Just copy the site root directory (usually under C:\inetpub\wwwroot or a custom path)

For dynamic sites (like ASP.NET with databases):

• Copy all website files
• Back up the database using SQL Server tools (BACKUP DATABASE command or SSMS)
• Store connection strings and other config values safely

You can automate this process using scripts or tools like Windows Server Backup, robocopy SQL dumps, or third-party solutions that support consistent snapshots.

It's a good idea to test your backups regularly. Try restoring them on a test server to make sure everything works as expected.

Moving IIS to a New Server

When migrating IIS to a new server, the steps are basically a combination of the above:

1. Back up IIS configuration on the old server
2. Install the same version of IIS and required features on the new server
3. Copy over website files and databases
4. Restore the IIS configuration using appcmd
5. Re-link databases and verify permissions

Some things may not transfer perfectly — especially custom modules or URL rewrite rules — so double-check those after migration.

Also, watch out for differences in file paths or drive letters. If your original site was on D:\websites, and the new server uses E:\sites, you'll need to adjust those paths manually before restoring or update them after.

That's the basic flow. It’s not overly complex, but it does require some planning and verification. As long as you cover both configuration and content, you're in good shape.

The above is the detailed content of Backing Up and Restoring IIS Configuration and Websites. For more information, please follow other related articles on the PHP Chinese website!