What Needs Backing Up
The complete IIS server configuration lives in a small set of XML files, mainly applicationHost.config, stored in the inetsrv config folder inside System32. This covers sites, bindings, application pools and server level settings. Your website content and SSL certificates are stored separately, so a complete recovery plan needs three parts: IIS configuration, site files, and certificates.
Creating a Configuration Backup
IIS includes a built-in backup command. Open an elevated command prompt, change into the inetsrv folder inside System32, and run:
appcmd add backup PreChanges2026
Use a meaningful name, ideally with a date. The backup is stored as a folder of config files under the inetsrv backup directory. List existing backups any time with appcmd list backup. We strongly recommend taking a named backup before installing modules, editing bindings, or making bulk changes.
Restoring a Backup
To roll back, run:
appcmd restore backup PreChanges2026
IIS applies the saved configuration immediately. Site content is not touched, only configuration. If IIS Manager was open during the restore, close and reopen it to see the restored state.
Do Not Forget These Items
- Website files. Copy the inetpub folders or your custom site directories to a second drive or offsite storage on a schedule.
- SSL certificates. Export each certificate with its private key as a PFX file from the certificates console and store it securely. A config restore alone cannot recreate lost private keys.
- Shared configuration. If you use IIS shared configuration across multiple servers, back up the network share as well.
- Automatic history. IIS also keeps automatic snapshots in the config history folder, which can rescue you after an accidental change, but never rely on it as your only backup.
Customers on Tech Guru managed Windows plans already receive scheduled backups. Confirm your coverage from the client area or ask us through a support ticket.
