Quoted from my provider:
Part 2:
Sending this message, primarily to make a general explanation, and a public apology.
Last night was a scheduled a VM reboot (all normal), however, the node was not restarted because of problems with the boot.
That's when the trouble started as we got in touch with them (VPS.net) (with all the ticket additions as absurd as, priority response and on-demand ticket, etc..) and still had no response.
Some time later a response: Problem with boot, we proceed to do a "fsck".
Well, then, do it!, 20 minutes later (we were told 20 minutes were more than enough), it was not so. Six hours later,they contacted us saying that the process should be repeated.
We think: What could be worse? ... and incredibly (yes, really), another six hours later, they contacted us, saying it was necessary to return to a previous restore point.
I thought that was crazy, insane, I was on a plane flying into the city, 40 thousand feet high blood boiled I am furious with these people, we pay A LOT (we have the number of nodes corresponding to several quadcore servers, more than 120 nodes) and should fail?.
Please all customers I honestly say that I'm doing everything possible to have this resolved, if there is delay in the stand, it is not our fault, we do see the tickets, but we just do not want update them with the same content (we are working on it, its in progress, etc.)
We are currently looking for ways to re-establish the last backup available (Yesterday -14 January), but to our surprise, they say it is corrupted, and have re-established a very old one.
This is something that has never happened in our 4 years online, we have always had confidence on our providers and we never had presented a similar situation.
My request to our dear users are:
- Please do not create support tickets, please start a online chat with an agent available.
- If your site does not work, but the server is online, do not worry, it's likely that another restore point (the newer one) is activated, in some moments.
Finally, I urge patience. I have spoken with the CEO in VPS.net, and I really do not understand why these guys do not give importance to our requirements, our investment on them and costs were high. And indeed: The error is the least of the problem, delay getting their support is the big problem.
As I said before, I have spoken directly to the CEO, and support has been properly addressed, and I hope so, I'm sorry this happened, It really could have happened, (well, it is a common issue!), but the response time from VPS.net was awful.
Part 2:
Hello,
Finally, we have been treated successfully (after many hours).
The server is Online not so long ago, the problem is that it uses a relatively old restore point.
We have already begun to investigate whether we can restore the backup done YESTERDAY.
During this period, try not to make many changes because we could restore the new backup.
Please wait until further notice.







