http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/ Engadget Comments for Alaska Department of Revenue vaporizes $38 billion account http://www.engadget.com/media/feedlogo.gif http://www.engadget.com en-us Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 5:50AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 6:12AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 6:10AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
]]>Mar 22nd 2007 6:19AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/


...holy crap I'm poor...]]>Mar 22nd 2007 6:26AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/If they held accounts details for that amount of money on one disk and one backup tape, they deserve to lose it.

EXACTLY! Such fools! My lil 10 year old cousin Jasmine knows how to make multiple copies of her work, why can't they? SAD!!

"Da da da da DAMN!!" - Fabolous]]>Mar 22nd 2007 6:33AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
I wonder whose account it was. I wonder if that oil money has something to do with Dick or his buddies.]]>Mar 22nd 2007 6:37AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 9:01AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 6:47AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 6:55AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 7:12AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Hmm... Where did I put that 38 billion dollar hard drive? I swear it was right here. Oh well, I'll just use the backup. Wait, where's the backup? Hey Bill! I thought that 38 billion dollar backup was on here but I can't find it.

Bill: Oh. Whoopsy-daisy. Guess I erased it. I also erased this hard drive. Anything else you want me to erase, boss? I seem to be pretty good at it.

-Yeah...I don't quite believe any person or buisiness could be that stupid or careless with 38 billion. Did that 220 grand to fix it come out of the 38 billion account? Sounds fishy. And No One got fired?! People where I work get fired for only being 99.999% accurate instead of 100% accurate with our numbers. I think someone needed work and -Whoops!- a hard drive gets erased and the friggin backup and look here! We've got 220 grand of work to do. I've seen it done consistently in construction and other contracting jobs.]]>Mar 22nd 2007 7:15AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 8:04AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 9:22AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 8:32AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 8:31AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
The information lost, was the names and accounts of where the dividend money goes when it gets paid out quarterly or yearly. The only money that was lost, was the money to pay the data entry people.

When governmental agencies say erase, they mean it. Erase, over-write and randomize. There was no "going back." Besides they had the paperwork and it's probably cheaper to pay people to re-enter it than go through the futility of trying to recover it.

The cynic in me says someone this admin knows is getting rich after the data is re-entered. "Sis, it looks like you hit it big this year."]]>Mar 22nd 2007 9:13AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 9:15AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
no one ever just erases a RAID5 array, unless it's a decommissioned server, and if they didn't migrate and verify before decommissioning, well, you get what you get.]]>Mar 22nd 2007 10:11AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
And at any rate, firing the tech - or holding him or her responsible in some way - would not solve the management problem that resulted in a crappy backup system. Ever heard of a no-blame corporate culture? It makes a lot of sense. If people aren't constantly in terror of getting fired, they are much more likely to own up to and fix their mistakes swiftly.]]>Mar 22nd 2007 10:53AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/Mar 22nd 2007 11:34AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
Uh, are you serious? Even on a SAN it's easy to wipe out the data. I've had to redo cross-site data mirrors and migrated terabytes of data between two SAN fiber attached servers, trust me, it's very easy to wipe out the data (alto this situation was preventative maintenance not an "accident"). The moral of this story is not to let idiots administer critical data.

I don't think they only had it on one HD and one tape. The way I read it, they had the info copied to two HDs (which both got wiped for some reason) and the tape backup was corrupt (this, unfortunately, is not at all uncommon, tape backup sucks).

I am surprised that they were not able to recover the data. The only time I haven't been able to recover data off of a reformatted drive with a recovery program is when I do DOD wipe (I was testing the DOD wipe, it works). Very fishy this story, I wouldn't have been surprised if the hard documents had also spontaneously combusted.
]]>Mar 22nd 2007 11:13AMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
# mkfs -F ufs /dev/rdsk/c0d0s3

Crap!!! I meant to type c1!!!]]>Mar 22nd 2007 12:49PMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
This is Alaska we are talking about here folks. The land of fake-it-til-you-make-it. I've experienced way too many I.T. and Data Processing idiots in charge. Then it gets worse, idiots tend to hire idiots so that they don't look bad. The rest of the folks blindly trust the decisions made by people who I wouldn't trust choosing my lunchtime sandwich. There are so many one-off solutions, proprietary backends, abandoned but still functioning services, lightning strikes that take out entire State of Alaska communications, etc. that it would behoove a major company who knows how to handle tens of thousands of employees, security, computers, phones, and so on to come up here and take the reigns. The poor horses are getting whipped from too many directions for this coach to ride smooth. ]]>Mar 22nd 2007 2:29PMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
If this dummy doesn't lose his job due to some miracle, then the ADoR aren't doing their job.]]>Mar 22nd 2007 3:49PMhttp://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/http://www.engadget.com/2007/03/22/alaska-department-of-revenue-vaporizes-38-billion-account/
OnTrack couldn't touch it - they tried.

The business would have been more fortunate had they had a fire. Really.

The budget for computer equipment was increased shortly afterward...]]>Mar 26th 2007 9:03AM