New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
What will happen if they admit that? Will you sue them in Ukraine? Push your disaster recovery button and that’s it.
So what? War is “force majore” and if you knew that - then you accepted the fact that at any moment bombs can fel in and that’s it.
“Others already restored” - why are you not with them?
Again - hosting critical data in country where active war action takes place is beyond idiotic.
Manager from Vsys and Assistant from elon kurvaovic
If you don't have any useful information, don't go around telling people what they should or shouldn't do—it's none of your damn business.
Great advice for you, stop telling vsys what to do
Any méi jī jī who wants to get a working metal server back up within 3 days of the drone strike needs to learn 2 new and useful words for them: backup and dolboyob
Overheard from friends in the music piracy community (not involved myself):
Apparenlty, there are two prominent sites (pillows.su and leaked.cx) which are popular DMCA-resistant filehosts/file sharing platforms for leaked and pirated music. Well, a few days ago (I believe on the 25th) both sites went down with no notice.
No error message on Pillows but on Leaked:
https://web.archive.org/web/20260925142838id_/https://leaked.cx/
https://web.archive.org/web/20260926184421id_/https://leaked.cx/
I guess we now know who is hosting these sites!
It's almost as if high explosives cause more damage the closer you are.
Did you ever think that, perhaps, VSYS got unlucky and had many of their servers closer to the explosion?
Wouldn't you do things the way they are saying they are doing things, if you were them?
the amount of lack empathy is something else. i refuse to acknowledge mjjs are human.
There's strong financial motivation. If they're able to put the nuance over the service rendered deemed not fit for purpose/described. They may file to a third party and do chargeback.
Or it's just straight, "IDGAF what it takes, make it happen. I've paid the for the service"
Well, the mjj is human at its core, but it is without penis. Peniless human. It may affect them and their perception of reality.
You've been given good advice already: Activate your disaster recovery plan and restore your backups to another location.
There will be no useful information from this host for a long time for the reasons they've already explained clearly. Comparing them to other hosts is a worthless exercise, as every company might have experienced different levels of damage, and not all of them have spare capacity to restore to another location.
My dedicated servers are still showing as “Awaiting Inspection.”
I completely understand that VSYS has many servers to inspect and that safety must come first. However, there is one important detail about my servers that I have already reported to support, and I would really appreciate it if VSYS could make sure this information is passed to the technical/recovery team performing the inspections.
According to the timeline of the incident, the attack had already occurred by approximately 11:30 Kyiv time.
Despite this, my servers continued to operate normally until approximately 16:30 Kyiv time, several hours after the attack. My understanding is that the facility continued operating on supplementary/emergency generator power until that power was eventually exhausted.
Only after approximately 16:30 did my servers become unreachable.
Now the servers are awaiting inspection because of possible water exposure.
I am not claiming that this proves the servers or drives were not subsequently exposed to water. I simply believe that the fact that they remained fully operational for approximately five hours after the attack could be relevant information for the technicians inspecting the hardware.
I have already provided this timeline to support, but I would just like confirmation that this information has been added to the technical notes for my specific servers and communicated to the recovery team.
At this point, my main priority is not even restoring the complete servers. I primarily need access to my data, particularly one important SQL backup.
If someone from VSYS here could please make sure this information is attached to my case before the hardware inspection, I would greatly appreciate it.
That's good info. The problem is VSYS's responses they're not giving any clarity, not answering anyone, and not updating the threads they created and called official. I've always been in favor of waiting and being patient because this isn't their fault, but they aren't doing their part to give users peace of mind. They just keep sending canned responses to everyone. What happened is unfortunate, but the way they're handling the situation is even worse.
Exactly. I completely understand that this was an exceptional event and that inspecting potentially water-exposed hardware takes time. I don’t blame VSYS for what happened, and I am prepared to wait if necessary.
The difficult part is having no visibility at all.
My servers have been showing “Awaiting Inspection” for days, and support cannot tell me whether they are 10th or 500th in the inspection queue, whether inspections are currently taking place, or even approximately how many dedicated servers have already been inspected.
Even something as simple as:
“Inspections have started, X servers have been checked so far, and we are processing approximately X servers per day”
would make a huge difference.
I don’t need a guarantee or an exact ETR. I just need to know that the process is actually moving forward.
In my particular case, I don’t even need the entire server restored. I mainly need one SQL backup from the storage.
I really hope VSYS starts providing some concrete progress updates, even if the news is simply that recovery will take longer than expected.
Your situation is the same as many others, and what you're proposing would be the smartest move. The problem and what worries me is that if VSYS isn't doing it, there must be a reason, and while I don't want to say it out loud yet, we all know what it is. Doing what you suggested isn't hard at all.
I think everyone with a dedicated server would be willing to wait months for the servers to work again if they were at least given the option to recover their data, but they aren't offering any clarity on that either. The way they are handling this situation is just tragic.
You guys are dense. Vsys already said what is the plan. No STUF and wait, stop whining like a bunch of little pussboys.