How would you move an IIS workload from on site to a VPS
-
@bbigford said in Website internal/external:
@scottalanmiller said in Website internal/external:
@jaredbusch said in Website internal/external:
@tim_g said in Website internal/external:
I don't see why that's causing issues. Is this a problem specifically with Cisco stuff... or something extra you need to pay for that everything else "just does"?
It is not restricted to Cisco. It is also not a new thing. It has always been an issue. But in today's world, almost no one hosts public sites on internal networks, so many people have no idea what this is.
Yeah, we used this in the 1990s, I'm pretty sure, but back then so much was hosted in house. Now it's a very rare problem to have.
There's a good chance I'll be putting this out on a VPS when their server ages out. So hopefully won't be an issue for too long. I haven't done that on Vultr yet (I'll probably have to fork this). But do you have to use a V2V converter from somewhere like 5nine or is there something Vultr might offer when that bridge is met?
Moving to a VPS is not a P2V or V2V process.
I would spin up your IIS instance on Vultr (or wherever) and configure it all and then simply move the data base and application folder.
-
I would take the chance to either script the deployment or, better, use a tool like Ansible or Salt to deploy in an automated, repeatable way. Had that been done initially (which probably wasn't possible as this is likely an ancient system) there would be no need for a P2V today. Then moving anywhere is transparent.
-
Also a good chance to look into if IIS is really needed, moving off of that could be a big benefit of this move as well.
-
@scottalanmiller said in How would you move an IIS workload from on site to a VPS:
Also a good chance to look into if IIS is really needed, moving off of that could be a big benefit of this move as well.
I'll have to look into that, as I'm not sure how I can just copy the application folder though since it's an install on Windows. I tried that once before with a different application years ago and nothing worked, with lots of errors. I was still learning the differences between how applications are installed on Windows vs. Linux at the time; my mentor back then had informed me I couldn't just move application folders the same way.
-
@bbigford said in How would you move an IIS workload from on site to a VPS:
@scottalanmiller said in How would you move an IIS workload from on site to a VPS:
Also a good chance to look into if IIS is really needed, moving off of that could be a big benefit of this move as well.
I'll have to look into that, as I'm not sure how I can just copy the application folder though since it's an install on Windows. I tried that once before with a different application years ago and nothing worked, with lots of errors. I was still learning the differences between how applications are installed on Windows vs. Linux at the time; my mentor back then had informed me I couldn't just move application folders the same way.
IIS apps aren't "installed" at all. They just exist. The concept of installation is not generally applicable to web workloads. Not installation in the "Windows or Linux" sense, at least. You might consider it "installed to the web server", but that's not the same. Apache installations are identical on Windows or Linux, for example.
-
@bbigford said in How would you move an IIS workload from on site to a VPS:
I'll have to look into that, as I'm not sure how I can just copy the application folder though since it's an install on Windows.
Normally it is just a folder that contains the app. Presumably the app needs a datasouce as well, though. Where is that located?
What kind of web app is this? ASP.NET? PHP? Java?
