Oopsy.
'Not Fade Away'
Buffistechnology 3: "Press Some Buttons, See What Happens."
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
Jesus fuckers. There are protocols, people! And wouldn't that be covered by some sort of regulatory board that would audit and make sure shit is backed up properly, above and beyond the department itself?
The technician is in hot water, but everyone above him in the org chart should be slapped around severely too.
ita, that's from the state with the Senator who believes that the Internets are a series of tubes.
But yeah, damn sure there are protocols, and good reasons not to skip on them.
At least they had their hard copies.
There are protocols, people! And wouldn't that be covered by some sort of regulatory board that would audit and make sure shit is backed up properly, above and beyond the department itself?
According to department staff, they now have a proven and regularly tested backup and restore procedure.
The technician is in hot water, but everyone above him in the org chart should be slapped around severely too.
Former Revenue Commissioner Bill Corbus said no one was ever blamed for the incident.
"Everybody felt very bad about it and we all learned a lesson. There was no witch hunt," Corbus said.
Governments jobs are the best...
they now have a proven and regularly tested backup and restore procedure.
It's 2007. Now they have one? Hopefully this'll prompt other groups to test their disaster recovery procedure.
At my last job, every system owner was required to test both disaster recovery and business continuity for not just data but business processes. So if hard copy it was, you had to show the process for resuming business that way too. Once a year. Because the Feds could come looking at any time.
Quis custodiet ipsos custodes?
At my job, in a University library, we had a hardware failure and then discovered that the backup procedure had failed and nobody had noticed. We lost 6 weeks of work by ca. 120 people. Nobody was fired. I was pretty shocked.
At my job, in a University library, we had a hardware failure and then discovered that the backup procedure had failed and nobody had noticed.
Was that the day I happened to see you first thing and you said "THEY DELETED THE CATALOG!", or was there some other 6-weeks-of-work disaster that I missed?
No, just the one time. So far. September 11, 2004, and we're still fixing problems from it.
I was surprised by the question they didn't address was "did they even bother to send the formatted drives to a recovery service?"
Sure they got people in there from Microsoft and Dell, but how about Ontrack?
OK, WinXP client, Win2003 (I think - maybe 2000) server - is there a simple way to tell from the client machine if a file on the server is locked, and what type of locking it is? I mean, I know you do those things with API calls, but absent that, can you tell?
eta: I suppose attempting to rename a file would tell you if there's any sort of lock, right?