- Beardie name(s)
- Cailyth, Pinky, & Brain
No, there will be no temporary page. The hosting provider does not manage the system beyond basic network, power, and rack space. They do not manage the DNS domains, nor other things. All of that for the sites this server is handled BY this server. For their Virtual Host environments, they were able to make a fairly seamless transition. For their shared hosted accounts, they could control all of that. But with dedicated servers, we lease a server. What we use it for, what domains that are handled by it, etc... that's up to us, and not something they are involved with (or really all that aware of).
It's POSSIBLE, that I could setup Solutions (man, I need to remember to transfer the domain away from them) to have some alternate system manage the DNS servers and put up a temporary page. But then I'd have to have access to another DNS server (which I could borrow a friend's server for, if needed). But then when the servers came back online, I'd have to switch things back myself being much more closely coupled to the physical server's move schedule.
We don't run in a redundant mode (too costly). I probably should at least setup DNS to use my friend's server as one of the available servers for domain resolution, anyway. And that would have made the change a little easier. But still would require me to manually do more work and be up at the wee hours on a Wednesday night just waiting for a server to come back online.
I think we'll just have to deal with it "missing". That's kind of why I put the notice up early.
As for having server 1 and server 2... that doesn't address data. Data is not replicated, and in order to have that kind of redundancy between servers, you'd have to have them both be able to access common network storage space (harder to do when spanning data center). And if they didn't, they'd be responsible for ensuring data was in sync (also harder to do with a dedicated server). I don't let them login to the box. First thing I did when the server account was ready was to change the root password and lock down the server.
So, anyway... it's a complicated thing to do a server move without having fairly complex infrastructure already in place to support that... and that's some VERY expensive stuff. We're just a little ol' website operating off what ad money and donations we get. heh.
-Alex
It's POSSIBLE, that I could setup Solutions (man, I need to remember to transfer the domain away from them) to have some alternate system manage the DNS servers and put up a temporary page. But then I'd have to have access to another DNS server (which I could borrow a friend's server for, if needed). But then when the servers came back online, I'd have to switch things back myself being much more closely coupled to the physical server's move schedule.
We don't run in a redundant mode (too costly). I probably should at least setup DNS to use my friend's server as one of the available servers for domain resolution, anyway. And that would have made the change a little easier. But still would require me to manually do more work and be up at the wee hours on a Wednesday night just waiting for a server to come back online.
I think we'll just have to deal with it "missing". That's kind of why I put the notice up early.
As for having server 1 and server 2... that doesn't address data. Data is not replicated, and in order to have that kind of redundancy between servers, you'd have to have them both be able to access common network storage space (harder to do when spanning data center). And if they didn't, they'd be responsible for ensuring data was in sync (also harder to do with a dedicated server). I don't let them login to the box. First thing I did when the server account was ready was to change the root password and lock down the server.
So, anyway... it's a complicated thing to do a server move without having fairly complex infrastructure already in place to support that... and that's some VERY expensive stuff. We're just a little ol' website operating off what ad money and donations we get. heh.
-Alex
