[COMPLETED] WINVPSNJS42 AND NJS46 to WINVPSNJS54 migrations - April 29th

[Voicu Rogojan]

Hello,

In a constant attempt to improve the quality and reliability of our service, we will be transferring your VPS to one of our newer nodes.

This is being scheduled for Sunday, April 29th, between 1:00 AM EST and 7:00 AM EST
We will also reserve Monday, April 30th, between 1:00 AM EST and 7:00 AM EST for maintenance (in case it's necessarry) and for continuing migrations that could not be done on April 29th.

A forum topic has been opened on the SolarVPS forums regarding this:
http://www.solarvps.com/forums/index.php?topic=838.0

which will be use for announcements and updates about the progress of the migrations.

Downtime for each customer will vary, though we do not anticipate that anyone will be down for longer than 90 minutes.

If your VPS has been down longer than that since you notice it first going offline, please open a Support ticket with the Support => Virtualization department at https://mymanagedsupport.com and request a status update for your system. Please also use that link to send any issues that might appear after this maintenance.

Please also feel free to contact us by telephone in case of emergency, by using the data from the following link:

http://www.solarvps.com/contact.php

Thank you for your continued patience and understanding while we continue our ongoing commitment to improve the infrastructure and quality of services we offer you!

Best Regards,
The FortressITX Team

[Tudy]

Greetings,

The maintenance is currently underway. We'll keep you updated on the progress.

[Chris]

The maintenance for today is complete, and half of the containers have been migrated to the new node.
The remaining containers will be migrated tomorrow.

In order to see if your VPS has been migrated to the new node, please run a traceroute to your VPS IP.

If the hop before your VPS is returing as:
TTLs  winvpsnjs54.fbyneserv.com [69.194.198.3]

followed by your VPS IP, then this means that you're running on the new node - WinVPSNJS54.

Any other values will mean that your container hasn't been migrated yet.

Chris Valean

[Tudy]

Greetings,

The maintenance has been resumed as scheduled.

[Tudy]

Hello everyone,

The containers from WINVPSNJS42 have been transferred successfully.

We have however identified an issue with WINVPSNJS46 preventing some of the containers on that node to be migrated, and we're working on finding a fix for that. The migrations from that node are currently suspended, until a fix is in place.

Thank you for your patience and understanding!

[Chris]

The remaining containers have been migrated by now and the customers have been updated in individual tickets about this.

At this point all containers from WINVPSNJS42  and WINVPSNJS46 are running on the new hardware node - WINVPSNJS54.

[CamKrist]

I sent you in pm