Slashdot Mirror

← Back to Stories (view on slashdot.org)

That Man Who 'Deleted His Entire Company' With a Line of Code? It Was a Hoax (pcworld.com)

Posted by msmash on from the false-alarm dept.

An anonymous reader writes: As many Slashdot readers speculated, the story about a man deleting his entire company with a line of code was a hoax. Marco Marsala, the owner of a Web hosting company claimed on a forum earlier this week that he deleted all the data on his company's server. Stack Overflow, which runs the forum, says that the post was a hoax, and pointed to an article on an Italian news outlet, which describes this whole fiasco as a "marketing effort" (in Italian) to promote Marsala's company. "It was just a joke," Marsala told the paper.

7 of 93 comments (clear)

  1. Interesting tactic by Crashmarik · · Score: 5, Insightful

    "Give us your data we'll delete it"

    I suppose they really really believe, there is no such thing as bad publicity.

  2. Idiot by nukenerd · · Score: 5, Insightful

    describes this whole fiasco as a "marketing effort" (in Italian) to promote Marsala's company

    He tries to get more business by saying he deleted all his customers' data ? What an idiot. And anyone who remains his customer after this is an even bigger idiot.

  3. Good Grief... by Frosty+Piss · · Score: 4, Insightful

    describes this whole fiasco as a "marketing effort" to promote Marsala's company

    How does telling everyone that you are incompetent "promote" your business?

    --
    If you want news from today, you have to come back tomorrow.
  4. Backups are a hoax by Iamthecheese · · Score: 4, Insightful

    The way most companies do backups there's no point. If backups are a checkmark on the official risk management schedule, you're fucked when you need one. I've seen it. To PROPERLY manage backups means you need to dedicate extra man-hours to making sure they can be restored in a wide variety of circumstances. By actually restoring from backup on occasion. Can you restore after you lose a server and the backup software on it? Can you restore after you've had a virus undetected for a week? For a month? Are your incremental backups too unwieldy to work in real life? Does it actually take a full day to pull the reels and get the data back? Do you have offline copies? How sure are you that your encryption can be decrypted?

    Doing backups properly is hard. The story would have had a ring of truth if it included backups that couldn't be restored because the encryption key was the wrong version.

    --
    If video games influenced behavior the Pac Man generation would be eating pills and running away from their problems.
    1. Re:Backups are a hoax by Anonymous Coward · · Score: 2, Insightful

      Former backup/recovery sysadmin here.

      There are two things a company needs to define before they should start looking at solutions: the RPO (Recovery Point Objective), and the RTO (Recovery Time Objective). Recovery Point Objective basically means, "How much data can you afford to lose in the event of a disaster? A second or less? An hour? A week? A month?" Recovery Time Objective basically means, "How long do you have to get that data back onto an operational system? How long can you afford for your system to be down?"

      Those two figures then let you say, "Okay - so what do we need to do to meet those objectives?"

      Traditional backup-to-tape-and-ship-the-tapes-offsite methods generally give you a recovery point of up to twenty four hours back (depending on how you do it). The recovery time is usually measured in days. Which is fine as a last resort, but may not be adequate from a general point of view.

      Conversely, if you take disk snapshots, and synchronise them to some site elsewhere that's running warm, you have a very low RPO and RTO. But malicious damage in this case is harder to defend against.

      Generally speaking, I advocate using both methods for hypercritical systems. The snapshot/synchronise system gives you the low RPO and RTO; the tape backups give you a modicum of protection against malicious damage.

      How much should you spend on the system? Now there's the million dollar question, and again, it comes down to the business tradeoffs.

      I've had companies ask me if I can recover their data in the event of a disaster. My usual response is, "probably." They generally don't like that answer, and ask me why I'm not certain. "Have you run a recovery test to verify that everything works as expected? No? Then you don't know, and you don't have reliable backups." Sure, if you run a recovery test, you only know that that data is recoverable, but it does give you a modicum of certainty that other backups using the same methods will be recoverable. And if you run a recovery test and it fails, well... fix the problems that caused it to fail, and try again until it works.

      It astounds me that companies will spend a fortune on backup systems, and then not bother running recovery tests because it's too hard. Tell that to the regulators when your financial system is toast, and can't be restored from backups...

  5. Re:Stupid is as stupid does by sumdumass · · Score: 4, Insightful

    Your right. Bad publicity can be good "free publicity" in some cases but this guy basically said "look at me, I'm a moron". You can recover from accidents and other misfortunes but pretending to be an idiot is sort of a lot more difficult.

  6. Or maybe it wasn't a hoax by Anonymous Coward · · Score: 2, Insightful

    He got lucky, fixed it, and acted like it was a joke. Remember don't suspect !malice when it could be stupidity...