Migration of windows 2008 server
* we've sent an email on 03 Jan 2014 to all clients on this server regarding this server migration
As a part of our continued efforts in providing up-to-date industry-leading solutions, we have prepared a top of the line hardware configuration to migrate clients on your server to. Data transfer to new server has already been started and migration will be completed in a week or two. Benefits include:
We look forward to helping you out in making the move as painless as possible. Please remember we are doing this for the overall betterment of services and the improved network and performance of your hosting account. Once migration is done, if you have any issues, please Open a support ticket ( Client area >> open ticket ) of receiving effective support in regards to this:
Things to consider:
Shared IP of new server is 23.91.121.104.
NOTE: You will need to change the IP Address ONLY once the migration is completed.
Added Features:
The new server will be setup with Windows Server 2012 so that you can benefit from new services that run on the OS (such as IIS 8.5, etc.). In addition to Windows 2012, we will be offering SQL Server 2012 Standard Edition and the latest .NET Framework on this new server.
Removed Features:
.NET Framework 1.1 and Microsoft Frontpage Extensions both have reached EOL (End Of Life) and Microsoft has not made them compatible with Windows Server 2012. This is why on new Windows Server 2012, .NET Framework 1.1 and Microsoft Frontpage Extensions will not be available. Sites requiring .NET Framework 1.1 will need to be made compatible with higher .NET Framework versions. Microsoft Frontpage can still be used but instead of Frontpage Extensions, publishing needs to be done through the FTP Upload method (and aspects requiring the frontpage extensions re-done).
Connection Strings:
New server is setup with SQL Server 2012 so connection strings using ".SQLExpress" or "localhostSQLExpress" will not work. Connection strings will need to be updated to just localhost. We will mass update the connection strings in web.config files but if any of the site is still producing database connectivity error after migration, please verify the connection string.
If the connection strings were encrypted in web.config, those will need to be re-encrypted on new server.
WebDeploy Publishing Login:
After migration, WebDeploy publishing login will need to be re-setup. This can be easily done from WebSitePanel > Website > Web Publishing tab.
As the data transfer is resource intensive operation so you may experience slightly sluggish performance during the migration. We understand that this might be troublesome and we look forward to helping you out in making the move as painless as possible. We will send migration completion notice once the migration is completed.
Thank you for your cooperation,
Update 1 : [2014-01-15 ]
Initial sync has been completed for users and mailserver data. We have started the data re-sync so that the updated data is copied over to new server.
Update 2 : [2014-01-17 ]
Migration for server will be completed on 20th January 2014.
Before switching services to new server, services will be taken offline for couple of hours so that final data sync can be done. We understand that this will cause downtime but this is necessary so that all updated data is copied over to new server.
Update 3 : [2014-01-20 ]
According to the tech division at the datacenter, Final step of migration currently in progress and the server taken down, therefore all services not funtioning at the moment. we'll update this annouincement once we receive more details
Update 4 : [2014-01-20 ]
Services have been switched to new server. All sites should be pointing to new server by now.
All sites are using the new server's MsSQL, IIS, Mail, MySQL, FTP, etc now or very shortly as long as the DNS is pointed properly. (it can take upto 24 hours )
Those who use a third-party DNS must change the "A record" to the new IP.
