Bob
03-29-2006, 02:33 PM
When: Mar 30, Mar 31, Apr 1, 2006
Duration: Less than 10 minutes per domain
All MySQL Databases currently residing on the MYSQL06 Server will be distributed across a number of new servers.
The move for each domain should not take more than 10 minutes to complete. However, it is important to note that while the databases for the domain(s) listed above are being moved, their MySQL services will not be available.
### IMPORTANT NOTES TO MINIMIZE SERVICE DISRUPTION ###
If your scripts use the recommended hostname to connect to the MySQL Server, and FutureQuest manages the DNS for your domain, then the move should not have any adverse affects.
The recommend hostname looks like:
## MySQL.example.com
You should use the recommended hostname at all times wherever possible. However, if your scripts are not using the recommended hostname, e.g. they use the Server IP Address (69.5.6.126) or the Server Name (MySQL06.FutureQuest.net) instead, then you should update them NOW to prevent failures after the move.
If there is a reason you are unable to use the recommended hostname, such as the DNS not yet being modified, you will need to make note of the following changes and implement them within your scripts after the move has been completed.
Current MYSQL06 Server Info:
Hostname: MySQL06.FutureQuest.net
IP......: 69.5.6.126
After the move you will find the new information in your CNC, under the Server Info section or in your MySQL Manager.
If you manage your own DNS and you are using the recommended hostname to connect to MySQL you will need to update the DNS entry to reflect the IP address for the new server. You may also send an email to Service@FutureQuest.net requesting a specific date and time frame to be assigned to your account for the move to be completed if you manage your own DNS.
This Notice is also being sent via email to the currently listed contact email address for each account that has databases on the MySQL06 server.
-Bob
Duration: Less than 10 minutes per domain
All MySQL Databases currently residing on the MYSQL06 Server will be distributed across a number of new servers.
The move for each domain should not take more than 10 minutes to complete. However, it is important to note that while the databases for the domain(s) listed above are being moved, their MySQL services will not be available.
### IMPORTANT NOTES TO MINIMIZE SERVICE DISRUPTION ###
If your scripts use the recommended hostname to connect to the MySQL Server, and FutureQuest manages the DNS for your domain, then the move should not have any adverse affects.
The recommend hostname looks like:
## MySQL.example.com
You should use the recommended hostname at all times wherever possible. However, if your scripts are not using the recommended hostname, e.g. they use the Server IP Address (69.5.6.126) or the Server Name (MySQL06.FutureQuest.net) instead, then you should update them NOW to prevent failures after the move.
If there is a reason you are unable to use the recommended hostname, such as the DNS not yet being modified, you will need to make note of the following changes and implement them within your scripts after the move has been completed.
Current MYSQL06 Server Info:
Hostname: MySQL06.FutureQuest.net
IP......: 69.5.6.126
After the move you will find the new information in your CNC, under the Server Info section or in your MySQL Manager.
If you manage your own DNS and you are using the recommended hostname to connect to MySQL you will need to update the DNS entry to reflect the IP address for the new server. You may also send an email to Service@FutureQuest.net requesting a specific date and time frame to be assigned to your account for the move to be completed if you manage your own DNS.
This Notice is also being sent via email to the currently listed contact email address for each account that has databases on the MySQL06 server.
-Bob