Cluster1 Migration Update Email

Stephen

US Operations
Staff member
A copy of the mailing sent to resellers



Important Migration Update

Dear Customer,

We are mailing to provide you with a status update concerning the migration of services from Florida to our Texas datacenter facility. In the next days we will be opening new servers for Windows 2008 and SQL 2008 hosting, these will become available automatically as the new servers are added. New Windows hosting accounts will automatically then go to the Windows 2008 platform. We have 2003 Servers still available with legacy ASP Components and Frontpage support, however the 2008 platform will not support them. Microsoft has ended support for Frontpage Server Extensions officially and it is no longer available outside of Windows 2003 Server. Windows 2008 however offers asp.net 4.0 switchable in the control panel, supported URL Rewrite functions, and unprecedented levels of control and flexibility to the user. While we are making 2008 available, we will not be forcing anyone to upgrade, and 2003 servers will continue to run on 2003. We can freely move(with ticket and some caveats) 2008 accounts to 2003 if needing FrontPage or legacy ASP objects, and 2003 to 2008 if wanting to make this change as well.


In migration of servers we have servers known as WinCF and Win22 ready to migrate services during a maintenance window tonight estimated from 10PM EDT until 4am EDT, or when completed fully. During this time control panel services will be unavailable. Also during this time, and in future migrations, you may see some changes required on web services, as this cluster has been running for many years there are some custom modifications that have been made by administrators and unable to be automatically duplicated by the automation systems. We have migrated dozens Hsphere servers in the last month but have seen few issues until the recent server moves. The problems have been notably caused by custom changes that may have been done years ago, some important points to note:
1. Manually set permissions or users, subftp accounts or extensions may not transfer automatically.
2. ASP.NET 2.0 set prior to Hsphere control panel official support, while we make every effort to ensure these sync we have seen a number of times it does not. You may need to create a ticket to request the proper version of ASP.NET be set, or attempt to change it from the control panel first. ASP.NET 4.0 will show up in 2003 servers, but will error if selected.
3. IP addresses of mail servers and SQL servers are changing and may require updates if hard coded into your code. We recommend using DNS based names where possible so auto updates can happen.
4. Custom php settings via ini file, perl modules installed in the past, or other custom scripting options may not carry over and may require a ticket to be installed or otherwise corrected. If using a custom php.ini you may need to request an updated version for the correct paths and versions installed.
5. When linux server migrations occur there may be intermittent downtime during the duration of the migration process due to configuration files being generated
6. Shared SSL may not load after migrations due to incompatibilities with Hsphere, this is also impacting existing customers that make any change. This emails serves as notice of a temporary suspension of shared SSL services.

We also want to remind you that our recommended way of mailing from websites and forms, is to use mail server for the hosted domain, as SMTP with SMTP authentication and port 587.

We make every effort during the migration to ensure your sites are available and working, but there will be some errors the software makes, and some changes required for some sites to make them function.
We will also continue to migrate servers on a nightly basis as file sync and IP addressing permits the updates for such will be made on http://status.jodohost.com and our forums on http://support.jodohost.com will contain additional details of the progress.
In the coming days some Microsoft SQL servers will be migrated and require a downtime of 2-5 hours to complete, we will strive to provide at least 12 hours advanced notice when this will happen on the above listed URLs, these are important to move with the servers most using them as much as it is possible so that you do not have to utilize remote SQL for an extended period of time.

We apologize for the length of this mail but feel it is important to make you aware of the potential issues we have encountered while making recent migration moves and you know the full impact of what could happen during the process.

Regards,


JodoHost
 
Back
Top