EmailDiscussions.com - View Single Post

rmannam · 12 Mar 2015, 04:53 PM

I Received this message from VFEMail

Thanks again for being a being a member of VFEmail!

We've secured a new colocation facility and will be moving in by April 1st.

As we're planning to physically relocate the servers soon - the question is: Can you accept a few hours of downtime, or do we need to engineer a mirrored site?

A mirrored site would require a new server for the primary data, and we'd add an additional VM to get the database data over. Then when the DNS is changed, the new location would proxy until the records are propagated. We'd have to figure out how to securely connect both sites, it would probably require a full site to site VPN and entirely new subnetting at the new site. More moving parts means more chance for errors. But, potentially no actual downtime. Anyone pointing to the old site after the DNS change will simply be proxied.

A shutdown would just be powering down the servers, and taking them to the new location. As only the primary data store is not mirrored, half of the servers could already be ready and waiting. I would expect less than 2 hours of downtime on a Saturday (CST) night. This method less chance of problems, no funky re-configurations. No additional equipment saves about a month's worth of hosting costs. The proxy from the old site can still be done in this configuration.

Please vote ASAP! ow.ly/JfW5q

Please let me know if you have any questions,

Thanks,
Rick Romero

12 Mar 2015, 04:53 PM	#3
rmannam Senior Member Join Date: Jun 2004 Posts: 143	I Received this message from VFEMail Thanks again for being a being a member of VFEmail! We've secured a new colocation facility and will be moving in by April 1st. As we're planning to physically relocate the servers soon - the question is: Can you accept a few hours of downtime, or do we need to engineer a mirrored site? A mirrored site would require a new server for the primary data, and we'd add an additional VM to get the database data over. Then when the DNS is changed, the new location would proxy until the records are propagated. We'd have to figure out how to securely connect both sites, it would probably require a full site to site VPN and entirely new subnetting at the new site. More moving parts means more chance for errors. But, potentially no actual downtime. Anyone pointing to the old site after the DNS change will simply be proxied. A shutdown would just be powering down the servers, and taking them to the new location. As only the primary data store is not mirrored, half of the servers could already be ready and waiting. I would expect less than 2 hours of downtime on a Saturday (CST) night. This method less chance of problems, no funky re-configurations. No additional equipment saves about a month's worth of hosting costs. The proxy from the old site can still be done in this configuration. Please vote ASAP! ow.ly/JfW5q Please let me know if you have any questions, Thanks, Rick Romero