I renamed the web.config and replaced it with the simple web.config. I also renamed the global.asax and did not replace it with another global.asax. When I navigate to "backup/BackupScriptRestore.aspx" to initiate the restore, I now get the following error: 

BC30451: Name 'Config' is not declared.
Line 68:             If Config.GetSetting("ServerName") = "" Then

I assume the code behind (BackupScriptRestore.aspx.vb) is compiled in one of the Evotiva DLL's, but am I missing some files? I uploaded the extracted "Resource" files and other Evotiva files to the "backup" directory. As well, the DotNetNuke.dll is in the "backup" directory.

Hopefully, once I get past this the redirect may be gone (wishful tinking), though you're not offering much hope.

I think a FAQ post in this forum may explain the redirect I am experiencing and suggests a similar solution you recommended early on (bravo) yet I'm constrained by the ISP who cannot (will not) restart IIS or recycle the app pool.

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/105609/scope/posts/Default.aspx
The last QA states: "DNN caches the entries in the PortalAlias table, so if the record is added after the first request to the site it will not be seen.
Should this happen (ie, you are redirected back to the URL of the old site), just recycle the app pool, or reset IIS to clear the cache completely."

So, if this is the only solution this scenario if the ISP won't restart IIS, is there a way to cause an IIS restart without appearing malicious?  I could code a page that causes a stack overflow by some recursive pattern that never ends but I'd really rather not have to do that. Possibly someone else on the forum may have some ideas.
Thanks

Well, we've edited the web.config to trigger a recompile, but we are not able to actually cause an IIS restart (unless I were to cause five severe errors that would cause IIS to restart) since the ISP did not consider this an option.

Horatio and I have emailed each other several times since his last post and made progress to resolve other issues. Yet now after a successful restore of the site database and site files, the redirect loop has returned. I am making one last apeal to any who may have insights to how to resolve this problem. At this stage, we are almost ready to hire someone but would hope there would be someone in this community that may have some insights to share.

I have researched this, reviewed the code and made efforts to follow each suggestion I have found with no resolution. Please consider this thread to date to see the variety of efforts made to address the rediredt loop and offer advice if you have clear recommendations of what might resolve this.

Thanks,
King