Jump to content

How long 'til the 'fi is operating normally again?


Iron_Dreamer

How long 'til the 'fi is operating normally again?  

  1. 1. How long 'til the 'fi is operating normally again?

    • <24 hours from now (time of posting)
      0
    • 1-3 days "
    • 3-5 days "
    • 5-10 days "
    • 10 days to 1 month "
    • over 1 month "
    • never


Recommended Posts

  • Replies 58
  • Created
  • Last Reply

Top Posters In This Topic

I have no desire to pour salt in Jude's wound. He's a man down right now and shit, I hope he can get his life back up and running soon. I am somewhat surprised to learn that Head-Fi and his businesses shared server/drive space since I thought that the equipment that Head-Fi ran on was paid for by a donation from Meier (the headfive, IIRC). Anyone else remember reading a post about that?

Link to comment
Share on other sites

I have no desire to pour salt in Jude's wound. He's a man down right now and shit, I hope he can get his life back up and running soon. I am somewhat surprise to learn that Head-Fi and his businesses shared server/drive space since I thought that the equipment that Head-Fi ran on was paid for by a donation from Meier (the headfive, IIRC). Anyone else remember reading a post about that?

The impression I get is that the nas device was just used to back up the servers, but they were in the process of rebuilding headfi in a clustered environment, so they'd probably wiped the servers. Then the nas had problems, causing a world of poop.

Link to comment
Share on other sites

Have you seen the price on hard drives lately??

No one in their right mind would ever wipe a server when they can throw

in a brand new drive or set of drives at $100 each.

I'll quit now, i've picked on jude enough for today.

I guess I'm not in my right mind. I wipe servers for upgrades with some regularity. I back up the stuff I will need, and wipe.

Link to comment
Share on other sites

The impression I get is that the nas device was just used to back up the servers, but they were in the process of rebuilding headfi in a clustered environment, so they'd probably wiped the servers. Then the nas had problems, causing a world of poop.

Thanks for explaining that Dan, that makes a lot more sense now.
Link to comment
Share on other sites

The impression I get is that the nas device was just used to back up the servers, but they were in the process of rebuilding headfi in a clustered environment, so they'd probably wiped the servers. Then the nas had problems, causing a world of poop.

If that was the case, then only head-fi would have gone down. Lots of other stuff went down

at the same time.

Link to comment
Share on other sites

Based on my limited understanding of it it's all the same nut to crack. The NAS was just a large storage device setup with a RAID array to self protect itself. The device controlling the RAID array and therefore what data was stored where since multiple drives were used to ghost a single large volume (or something like that) went tits up. When it did it probably lost the allocation table or the address configuration or something along those lines. So all the data is probably sitting there and just fine but has no way of reconnecting itself. The fact that the first recovery process didn't work is a pretty bad omen in my book.

So all you computer experts out there...

what do you figure the chances are that they'll be able to recover it? After all of this time?

I would guess that the client sites will come first.

Link to comment
Share on other sites

So all you computer experts out there...

what do you figure the chances are that they'll be able to recover it? After all of this time?

I would guess that the client sites will come first.

It is all the same thing - most likely tits up in a total scramble. This is where the data recovery guys might be smelling a really fat payday, because even a 99.9% recovery, depending on the data lost, will still be totally unacceptable. Lawyers at dawn action.

This really freaks me out, as I have a 128 Tb SAN, and have paid a lot of $$$ for redundancy, monitoring and backup systems - just no way to REALLY test a complete disaster recovery in our topology.

This is a real world case study for my Product Manager. My responsibility is the code, but if the data gets whacked... there but by the grace of God (and MOM / StoreVault) go I.

Link to comment
Share on other sites

What if headfi would go back up but in future time, like in the spaceballs movie...

"wtf am i looking at?"

"your looking at a post your typing right now. its a new thing where the reply is posted before you even think of it."

"so where am i now in posting on headfi?"

:your looking at your typing now sir"

"what happened to then?"

"when?"

"now?"

"wtf?"

ok i messed that movie quote up but you get the idea...

Link to comment
Share on other sites

Pretty, are you already drunk on your birthday?

sadly no...but thanks for asking.

i am so tired cause i drove Todd around record shopping today..from the southside to the northside 3 times over.

the hotel is so stacked! Vicki you and the flori gang should come down..dont worry you can stay at Rays place for free...

just dont tell him i told you..ssshhhh

Link to comment
Share on other sites

Yeah, I'm kind of with Grawk - the best rebuild is a clean one from a virgin wipe. The problem is that Jude had so much crap built on top of things with all that advertising, there's probably no way to re-create things in a stable manner. The further away you get from the base forum software, the harder it will be to re-create it in a stable state.

Did anyone notice that d*mn "Intellitext" that went on in the last few months? That stuff is a virus all on its own.

Link to comment
Share on other sites

This really freaks me out, as I have a 128 Tb SAN, and have paid a lot of $$$ for redundancy, monitoring and backup systems - just no way to REALLY test a complete disaster recovery in our topology.

Yes there is a way to test it, but it gets very expensive. You get a complete second copy of

the hardware to do a disaster restore from tape, and then check to see that it works.

Although i only have a few Tb, i have done this test on my hardware stack 3 times now, every

time a firmware upgrade happens.

This is why you buy EMC, IBM, or SUN. Not a toy running rom based linux.

Even so, 6 years back EMC had a bad batch of boards, did not tell anyone, and ended up

in a gigantic lawsuit. Tape backups removed to secure locations are absolutely necessary.

Jude's plans for world domination of the headphone world have been canceled.

And yes payback is a bitch.

The creator says not to gloat in the misery of others, but what jude has done to me and

my friends, and the way he treats everyone is so condecending that he deserves this and

much more.

Jude needs to stop lying and look in the mirror for the source of all his trouble. He believed

too much of his own bullshit.

Link to comment
Share on other sites

This really freaks me out, as I have a 128 Tb SAN, and have paid a lot of $$$ for redundancy, monitoring and backup systems - just no way to REALLY test a complete disaster recovery in our topology.

Well I think the problem your seeing in this case is that the live data and the backups were kept on the same NAS device this is a major no no. I'll assume in your case that you'd be a little smarter and not keep live data and backups on the same device :). Hardware fails it's the nature of the beast which is why backups should always be on a different device and/or off-site depending on the importance of the data.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.