Backing up and Restoring IIS configuration - Revision history

Joel: /* Set IIS automatic backup location to d: */

2018-06-04T11:28:38Z

Set IIS automatic backup location to d:

← Older revision		Revision as of 11:28, 4 June 2018
Line 54:		Line 54:
	%windir%\system32\inetsrv\appcmd list backup		%windir%\system32\inetsrv\appcmd list backup

	=== Set IIS automatic backup location to d: ===		=== Set IIS automatic backup location to D: ===

	By default, Windows automatically backups the last 10 IIS configurations		By default, Windows automatically backups the last 10 IIS configurations
Line 63:		Line 63:
	We need to:		We need to:

	1. Change the location of the automatic backups since NEOSYS backup procedures ~~dont~~ backup C: drive. ESSENTIAL		#Change the location of the automatic backups since NEOSYS backup procedures do not backup C: drive. ESSENTIAL
	2. Increase the number of backups. OPTIONAL		#Increase the number of backups. OPTIONAL

	Configure the new backup location on d: and increase the number of historical backups kept from 10 to 100		Configure the new backup location on d: and increase the number of historical backups kept from 10 to 100, by entering the following commands in command prompt.

	mkdir d:\inetpub\history		mkdir d:\inetpub\history
Line 74:		Line 74:
	appcmd.exe set config -section:system.applicationHost/configHistory /maxHistories:"100" /commit:apphost		appcmd.exe set config -section:system.applicationHost/configHistory /maxHistories:"100" /commit:apphost

	Check that automatic backups are in fact now going to D: by making some		Check that automatic backups are in fact now going to D: by making some trivial change in IIS and waiting 2 minutes to see the backup appear in D:
	trivial change in IIS and waiting 2 minutes to see the backup appear in D:

	=== Using other IIS configuration commands ===		=== Using other IIS configuration commands ===

Steve: /* Backing up certificate bindings */

2016-05-21T20:01:32Z

Backing up certificate bindings

@@ Line 201: / Line 201: @@
   netsh http add sslcert ipport=0.0.0.0:4474 certhash= 06249326271595871fd935a37bd1334bb761e519 appid={4dc3e181-e14b-4a21-b022-59fc669b0914}
   netsh http add sslcert ipport=0.0.0.0:4475 certhash= 06249326271595871fd935a37bd1334bb761e519 appid={4dc3e181-e14b-4a21-b022-59fc669b0914}
 === Restoring certificate bindings ===

Steve: /* Restoring certificate bindings */

2016-05-21T15:36:57Z

Restoring certificate bindings

← Older revision		Revision as of 15:36, 21 May 2016
Line 204:		Line 204:
	=== Restoring certificate bindings ===		=== Restoring certificate bindings ===

	~~If you dont have~~ the ~~backup file then you can just import the~~		Import the certificate(s) first.
	certificate ~~and redo the bindings without much effort anyway. This~~
	~~process is more to enable automated restores on warm backup servers~~.

	This will only ADD bindings, it will not delete, nor overwrite any		#IIS
	existing bindings so you might have to delete bindings first to allow		#Server item
	changes.		#Server Certificates
			#Import
			#Certificate File D:\hosts\CERTIFICATES\hosts.neosys.com.pfx
			#Password 1fd...
			#Allow to be exported. NO

			Bind the certificate to the https ports

			If you dont have the binding backup file (bindcerts.sh) then you can just redo the bindings one by one on each website without much effort anyway. This process is more to enable automated restores on warm backup servers.

			This will only ADD bindings, it will not delete, nor overwrite any existing bindings so you might have to delete bindings first to allow changes.

	Get the bindcerts.sh file from the restore stage		Get the bindcerts.sh file from the restore stage
Line 218:		Line 226:
	chmod +x bindcerts.sh		chmod +x bindcerts.sh
	./bindcerts.sh		./bindcerts.sh

			or just cut and paste the contents of the file into a windows command console

			==== "SSL Certificate add failed, Error: 1312" ====

			A specified logon session does not exist.
			It may already have been terminated.

			You didnt import the certificate first OR the HASH in export wasnt correct (doesnt match the imported certificate)

	If you get a message "parameter incorrect" then check that your hash is		If you get a message "parameter incorrect" then check that your hash is
Line 226:		Line 243:
	The parameter is incorrect.		The parameter is incorrect.

	~~If you get a message~~ "~~already exists~~" ~~then perhaps you have already~~		==== "SSL Certificate add failed, Error: 183" ====
	~~bound the port to the right certificate .. or a wrong/old certificate~~

	SSL Certificate add failed, Error: 183		SSL Certificate add failed, Error: 183
	Cannot create a file when that file already exists.		Cannot create a file when that file already exists.

			perhaps you have already bound the port to the right certificate .. or a wrong/old certificate

	... delete the binding and try again. Here is an example of deleting		... delete the binding and try again. Here is an example of deleting

Steve: /* Restoring IIS backups */

2016-05-21T15:23:23Z

Restoring IIS backups

← Older revision		Revision as of 15:23, 21 May 2016
Line 96:		Line 96:
	=== Restoring IIS backups ===		=== Restoring IIS backups ===

	~~IIS backups can be listed, restored~~ and ~~deleted.~~		Copy the last backup directory (eg CFGHISTORY_0000000913) from d:\inetpub\history to c:\inetpub\history eg using cut and paste

			Get to the directory where the APPCMD program is stored

	c:		c:
	cd %windir%\system32\inetsrv		cd %windir%\system32\inetsrv

			List available backups and check your backup is available

	appcmd list backup		appcmd list backup
	~~appcmd restore backup SOMEBACKUPNAME~~
	~~appcmd delete backup SOMEBACKUPNAME~~

	Each backup is stored in a separate directory and you can rename them by		Perform the restore
	simply changing the directory name.
			appcmd restore backup CFGHISTORY_0000000913

			Note that restoring will also set the backup directory to whereever it was in the backup (ie d:\inetpub\history)

			Each backup is stored in a separate directory and you can rename them by simply changing the directory name.

	The list of available backups is a merged set from the default automatic		The list of available backups is a merged set from the default automatic

Steve: /* Backing up certificate bindings */

2016-05-21T14:39:09Z

Backing up certificate bindings

@@ Line 165: / Line 165: @@
   awk -v CERTHASH="$CERTHASH" '{print "netsh http add sslcert ipport=" $3 " certhash= " CERTHASH " appid={4dc3e181-e14b-4a21-b022-59fc669b0914}"}' \
   | tee bindcerts.sh
 === Restoring certificate bindings ===

Steve: /* other IIS APPCMD config commands */

2016-04-22T15:13:41Z

other IIS APPCMD config commands

← Older revision		Revision as of 15:13, 22 April 2016
Line 134:		Line 134:
	=== other IIS APPCMD config commands ===		=== other IIS APPCMD config commands ===

			c:
			cd %windir%\system32\inetsrv
	appcmd list site		appcmd list site
	appcmd list site demo		appcmd list site demo

Steve: /* Restoring IIS backups */

2016-04-22T15:13:24Z

Restoring IIS backups

← Older revision		Revision as of 15:13, 22 April 2016
Line 98:		Line 98:
	IIS backups can be listed, restored and deleted.		IIS backups can be listed, restored and deleted.

			c:
			cd %windir%\system32\inetsrv
	appcmd list backup		appcmd list backup
	appcmd restore backup SOMEBACKUPNAME		appcmd restore backup SOMEBACKUPNAME

Steve: /* Backing up and Restoring IIS configuration */

2016-04-22T15:12:49Z

Backing up and Restoring IIS configuration

← Older revision		Revision as of 15:12, 22 April 2016
Line 52:		Line 52:
	or all in one line		or all in one line

	%windir%\system32\~~inetsrvz~~\appcmd list backup		%windir%\system32\inetsrv\appcmd list backup

	=== Set IIS automatic backup location to d: ===		=== Set IIS automatic backup location to d: ===

Steve: /* Set IIS automatic backup location to d: */

2016-04-22T15:11:49Z

Set IIS automatic backup location to d:

← Older revision		Revision as of 15:11, 22 April 2016
Line 63:		Line 63:
	We need to:		We need to:

	1. Change the location of the automatic backups since NEOSYS backup		1. Change the location of the automatic backups since NEOSYS backup procedures dont backup C: drive. ESSENTIAL
	procedures dont backup C: drive. ESSENTIAL
	2. Increase the number of backups. OPTIONAL		2. Increase the number of backups. OPTIONAL

	Configure the new backup location on d: and increase the number of		Configure the new backup location on d: and increase the number of historical backups kept from 10 to 100
	historical backups kept from 10 to 100

	mkdir d:\inetpub\history		mkdir d:\inetpub\history
			c:
			cd %windir%\system32\inetsrv
	appcmd.exe set config -section:system.applicationHost/configHistory /path:"d:\inetpub\history" /commit:apphost		appcmd.exe set config -section:system.applicationHost/configHistory /path:"d:\inetpub\history" /commit:apphost
	appcmd.exe set config -section:system.applicationHost/configHistory /maxHistories:"100" /commit:apphost		appcmd.exe set config -section:system.applicationHost/configHistory /maxHistories:"100" /commit:apphost

Priyanka: /* Set IIS automatic backup location to d: */

2016-01-18T13:15:41Z

Set IIS automatic backup location to d:

← Older revision		Revision as of 13:15, 18 January 2016
Line 58:		Line 58:
	By default, Windows automatically backups the last 10 IIS configurations		By default, Windows automatically backups the last 10 IIS configurations
	to c:\inetpub\history, looking for changes every 2 minutes.		to c:\inetpub\history, looking for changes every 2 minutes.

			Below steps are already done on win3/win4

	We need to:		We need to: