Deleting a lockfile

Richard Kreiss rkreiss at gccconsulting.net
Wed Apr 6 10:52:02 PDT 2011



> -----Original Message-----
> From: Kenneth Brody [mailto:kenb at fptech.com]
> Sent: Wednesday, April 06, 2011 1:22 PM
> To: rkreiss at gccconsulting.net
> Cc: 'filePro Mailing List'
> Subject: Re: Deleting a lockfile
> 
> On 4/5/2011 5:17 PM, Richard Kreiss wrote:
> [...]
> >> My shot-in-the-dark out-of-the-blue guess...
> >>
> >> They shift-clicked on "lockfile", thereby selecting everything from
> >> the currently-selected item (which defaults to the first filename)
> >> through the lockfile.  And, given that there probably weren't any J,
> >> K, or L files
> > (aside from
> >> "lockfile"), that could be seen as "everything in that folder
> >> starting
> > with A
> >> through I".
> >
> > I think you are correct.
> >
> > I was able to reinstall most of what was deleted except some new
> > selection sets that I don't normally copy to my test bed.  Looks like
> > I will have to start copying these also.
> >
> > If they had caught this early enough and the person who deleted the
> > files had not logged off of his terminal server session, we might have
> > been able to recover these files.
> 
> And people say there's no use for a data ("starts with 'a' through 'l'")
> segment.  :-)

Interesting aside to all of this, when they checked with their outside
service, who manages their system, they found that the last good backup was
from December 2010.

Someone messed up the configuration of the backup software when they
switched from tape to their NAS drive, so it was not being done.

I would suggest to all, check to insure that backups are being done and then
make sure it can be restored especially if backing up to tape. 

Richard 



More information about the Filepro-list mailing list