FH-John
02-16-2006, 09:16 PM
The following notice was sent to customers with a database on db2.
Dear Valued Customer,
We are scheduling a maintenance work on this coming Monday, February 20, 2006 at 4 AM Eastern Time (GMT -05:00). During this maintenance window, we will migrate one of our database servers, db2.fluidhosting.com (also known as mysql2.fluidhosting.com or pgsql2.fluidhosting.com), to a more powerful server. You are being contacted because you have at least one MySQL and/or PgSQL database on this server.
The new database server will be equipped Xeon 2.4 GHz, 3 GB of memory and 2x36 GB U320 10000 rpm drives in RAID 1 configuration. We believe the new database server will perform better on this new server. Unfortunately, this maintenance work will involve a service interruption to the MySQL/PgSQL services on this server. We estimate a maximum of one hour of service interruption for the time it takes to synchronize the old db2.fluidhosting.com server with the new one. No other services (Web, FTP, Mail, etc) will be affected and we expect no other complications from this maintenance work.
Please note that because of this migration, a new IP (204.14.91.12) will be assigned to the new db2.fluidhosting.com server. This change of IP should not affect you if you are connecting using host name (db2.fluidhosting.com, mysql2.fluidhosting.com, or pgsql2.fluidhosting.com). If you are connecting using the IP address, please make sure you change the connection string to the new IP address. We strongly recommend you to change your connection string to the host name instead. The host name will always be the same, independent of the IP address.
Also, as per our company policy, we have never allowed remote connection to our database servers, except connection from our own webservers. This is simply because the control panel is unable to keep track of the traffic usage on the database servers. Currently, due to an overlook on our part, db2.fluidhosting.com is set to allow remote connection. Thus, together with this database migration, we will again close the remote connection to the new db2.fluidhosting.com server. Only connections from our webservers will be allowed to connect to our database servers. This should not affect you in any way or form, except if you have been connecting to our db2.fluidhosting.com remotely.
Please plan accordingly for this maintenance window. Should you have any questions and/or concerns regarding this migration, please do not hesitate to contact us at support[at]fluidhosting.com.
Sincerely,
System Administrators
Fluid Hosting, LLC
Dear Valued Customer,
We are scheduling a maintenance work on this coming Monday, February 20, 2006 at 4 AM Eastern Time (GMT -05:00). During this maintenance window, we will migrate one of our database servers, db2.fluidhosting.com (also known as mysql2.fluidhosting.com or pgsql2.fluidhosting.com), to a more powerful server. You are being contacted because you have at least one MySQL and/or PgSQL database on this server.
The new database server will be equipped Xeon 2.4 GHz, 3 GB of memory and 2x36 GB U320 10000 rpm drives in RAID 1 configuration. We believe the new database server will perform better on this new server. Unfortunately, this maintenance work will involve a service interruption to the MySQL/PgSQL services on this server. We estimate a maximum of one hour of service interruption for the time it takes to synchronize the old db2.fluidhosting.com server with the new one. No other services (Web, FTP, Mail, etc) will be affected and we expect no other complications from this maintenance work.
Please note that because of this migration, a new IP (204.14.91.12) will be assigned to the new db2.fluidhosting.com server. This change of IP should not affect you if you are connecting using host name (db2.fluidhosting.com, mysql2.fluidhosting.com, or pgsql2.fluidhosting.com). If you are connecting using the IP address, please make sure you change the connection string to the new IP address. We strongly recommend you to change your connection string to the host name instead. The host name will always be the same, independent of the IP address.
Also, as per our company policy, we have never allowed remote connection to our database servers, except connection from our own webservers. This is simply because the control panel is unable to keep track of the traffic usage on the database servers. Currently, due to an overlook on our part, db2.fluidhosting.com is set to allow remote connection. Thus, together with this database migration, we will again close the remote connection to the new db2.fluidhosting.com server. Only connections from our webservers will be allowed to connect to our database servers. This should not affect you in any way or form, except if you have been connecting to our db2.fluidhosting.com remotely.
Please plan accordingly for this maintenance window. Should you have any questions and/or concerns regarding this migration, please do not hesitate to contact us at support[at]fluidhosting.com.
Sincerely,
System Administrators
Fluid Hosting, LLC