Share via

IIS backup is backing up old history not new live data from IIS (All sites and Pools not new)

carrzkiss 0 Reputation points
2023-01-26T00:58:27.34+00:00

Windows 2016 Core Servers / IIS10  

==IMPORTANT==  

The backup seems to be backing up OLD data.  

It seems that it is picking up on history instead of backing up the LIVE data.  

This will explain WHY it is not getting all the sites and pools during the backup of either of the two methods below.  

Looking in the

C:\Windows\System32\InetSrv\config

Folder, I see that all the files here are from 2020, so it backs this information up.

I also looked in

C:\Inetpub\history

These files are identical to the ones above as well.

Why is it not showing updated files in this location?

Also, from what I read here on Stackoverflow, the 64-bit version of the file is not being seen.  

C:\Windows\SysWOW64\inetsrv  

When viewing this location, there are NO files here.  

So, what am I missing?  

Using the CMD line  

c:\windows\system32\inetsrv\appcmd.exe add backup "WebCore-01 - 1-261-2023"

Using the PS

backup-WebConfiguration -Name "WebCore-01 - 1-261-2023"

I never really noticed this issue in the past until I brought in new webcore servers and added them into the IIS Server Farm and synced them with the primary server, and noticed that all other web servers were working, but two sites were not working on the two new VM servers. So I chased down the issue, or one of the issues was the BINDINGS were all from months ago. Several bindings were removed mid-summer of 2022, but that is the period backed up during the above two mentioned methods.

Thank you.  

Wayne

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,436 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. carrzkiss 0 Reputation points
    2023-01-27T06:29:41.17+00:00

    Found the issue.

    So, if anyone has this issue while running a Web Farm with IIS, and you are running Shared config files, the primary server will have its config files stored in the location you designated during the Shared Config setup.

    In my case, there is

    G:\IIS_Config

    This was annoying, now I need to share this location with the two new servers, and we are good to go.

    0 comments