retep
09-27-2004, 05:21 AM
Summary
Host19 is having hardware problems. We are copying your VPS to a new server. Your new VPS will have a new IP address. You need to change your DNS to point to that new IP. There will be a one week transition period where both the new and old IP address will work.
The detail follows...
Host19 Having Problems
Over the last couple of weeks we have been having issues with host19. The symptom is a kernel error that prints out. And then certain things stop working (e.g. the ps command 'hangs'). We rely on commands like ps to be able to stop/start the VPSs. So when the problem strikes we have needed to restart the host server.
We have attempted to resolve the problem on this host server:
~ We have updated the kernel to the latest version. This kernel version is running on other, identical host servers with no problems.
~ We have replaced the memory (all 4GB) in the server with new memory.
The problem persists. And is likely hardware related.
About the VPS Moves
To resolve the problem for customers we will be moving your VPS to a new host server.
The new host server happens to be in a different data center (Colo4Dallas per http://rimuhosting.com/datacenters.jsp) from the current one in New York. Both data centers have excellent networks, high reliability and good bandwidth. The new data center is one we have been setting up new server for the last few months.
The VPS Move Steps
The process will be as follows:
1) We will copy your VPS's file system to the new server. To do this we pause your VPS for a few minutes, copy its file system, resume the VPS, then scp the backup over to the new server. The pause/resume of the VPS does not require a VPS restart. And typically network connections to the VPS during the pause/resume are not even affected (they just block for a few minutes).
2) On the new server we will change the VPS's IP. Since you are moving data centers, we need to re-assign your VPS's IP.
3) We will start up your VPS on the new server. At this point you can SSH to it (using the new IP). And it should be an exact copy of your original VPS at the time the backup was made. e.g. same databases, same passwords, same files, etc, etc.
4) When you are happy with the new VPS, change your DNS to point to the new IP.
5) After a transition period we will shut down the VPS on the old server. We hope to decommission host19 by the end of this week. Though we may extend this date if there is a customer need to keep the old IP/VPS working for a while.
Move VPS Move Info
In order to minimize the differences between your original VPS and the copy we put on the new server, we encourage you to change your IP over to the new server as soon as possible.
You will be able to access both servers during the transition period. If you need to copy data from one to the other, you can (e.g. using scp or rsync). If you need us to run another backup of your original server, we can do this for you (just put in a support ticket).
We are beginning the copying process now. We will post again when the VPSs are available to be used.
If you have any questions or concerns you would like me to address directly please post a comment here or email peter at rimuhosting.com. If you need support during the move, just pop in a support ticket here: http://rimuhosting.com/ticket/startticket.jsp
What You Need to Do
1) Wait for us to setup your new VPS. We are working on this now and will post in this topic when your VPS has been copied to the new host server. If you register on these forums you can subscribe to get a notification of any new post here.
2) Check your new VPS is OK, then change your IP address to point to the new VPS. Please do this this before the end of the transition period (i.e. end of this week).
Host19 is having hardware problems. We are copying your VPS to a new server. Your new VPS will have a new IP address. You need to change your DNS to point to that new IP. There will be a one week transition period where both the new and old IP address will work.
The detail follows...
Host19 Having Problems
Over the last couple of weeks we have been having issues with host19. The symptom is a kernel error that prints out. And then certain things stop working (e.g. the ps command 'hangs'). We rely on commands like ps to be able to stop/start the VPSs. So when the problem strikes we have needed to restart the host server.
We have attempted to resolve the problem on this host server:
~ We have updated the kernel to the latest version. This kernel version is running on other, identical host servers with no problems.
~ We have replaced the memory (all 4GB) in the server with new memory.
The problem persists. And is likely hardware related.
About the VPS Moves
To resolve the problem for customers we will be moving your VPS to a new host server.
The new host server happens to be in a different data center (Colo4Dallas per http://rimuhosting.com/datacenters.jsp) from the current one in New York. Both data centers have excellent networks, high reliability and good bandwidth. The new data center is one we have been setting up new server for the last few months.
The VPS Move Steps
The process will be as follows:
1) We will copy your VPS's file system to the new server. To do this we pause your VPS for a few minutes, copy its file system, resume the VPS, then scp the backup over to the new server. The pause/resume of the VPS does not require a VPS restart. And typically network connections to the VPS during the pause/resume are not even affected (they just block for a few minutes).
2) On the new server we will change the VPS's IP. Since you are moving data centers, we need to re-assign your VPS's IP.
3) We will start up your VPS on the new server. At this point you can SSH to it (using the new IP). And it should be an exact copy of your original VPS at the time the backup was made. e.g. same databases, same passwords, same files, etc, etc.
4) When you are happy with the new VPS, change your DNS to point to the new IP.
5) After a transition period we will shut down the VPS on the old server. We hope to decommission host19 by the end of this week. Though we may extend this date if there is a customer need to keep the old IP/VPS working for a while.
Move VPS Move Info
In order to minimize the differences between your original VPS and the copy we put on the new server, we encourage you to change your IP over to the new server as soon as possible.
You will be able to access both servers during the transition period. If you need to copy data from one to the other, you can (e.g. using scp or rsync). If you need us to run another backup of your original server, we can do this for you (just put in a support ticket).
We are beginning the copying process now. We will post again when the VPSs are available to be used.
If you have any questions or concerns you would like me to address directly please post a comment here or email peter at rimuhosting.com. If you need support during the move, just pop in a support ticket here: http://rimuhosting.com/ticket/startticket.jsp
What You Need to Do
1) Wait for us to setup your new VPS. We are working on this now and will post in this topic when your VPS has been copied to the new host server. If you register on these forums you can subscribe to get a notification of any new post here.
2) Check your new VPS is OK, then change your IP address to point to the new VPS. Please do this this before the end of the transition period (i.e. end of this week).