Unix Permission Problem After a CPU Crash

[Jay R. Ashworth]

On Sun, Apr 20, 2008 at 07:45:00AM -0400, Del wrote:
> Thanks for the replies to this problem.  As it turned out, two files, the 
> open order file and the order archive, were completely trashed beyond 
> repair.  We could not back them up and when we ran fsck, it just deleted 
> them.  We restored the files from his most recent backup (three weeks old) 
> and are manually rebuilding them to the point of the crash.  Fortunately, he 
> has paper records of all incoming orders, and we have other files in the 
> system that have records of activity since the last backup, so we are 
> optimistic about being able to manually recover the missing data (most of 
> it).
> 
> This is the first time in twenty-six years that any customer of mine has 
> actually lost data.  The customer admits that it is his fault for not moving 
> fast enough to get the failed tape drive replaced.  When it rains, it pours.

Yeah; we haven't lost any to anything except customer stupidity since
we started speccing BackupEdge.  Thanks, Tom.  :-)

FWIW, one of my clients has a directory (on another filesystem, and now
on another drive) that he backs all his key segments up to every night
from cron; rolling 7 day cleanout.

This might be a useful thing for you to consider as well; second line
of defense.

Depending on your recovery needs, you could also just tar all the keys
up into one big tgz-ball.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

	     Those who cast the vote decide nothing.
	     Those who count the vote decide everything.
	       -- (Joseph Stalin)