(no subject)

From: ~~~YPD~~~ (Back@One.com)
Date: 11/06/02 

From: ~~~YPD~~~ <Back@One.com>
Date: Wed, 06 Nov 2002 01:57:30 GMT

We have a setup in our company where our network is run by the main
Windows NT server which has one large hard drive partitioned into five
drives.

The data files for a scheduling program is on the "X" drive. There is
an irreplaceable amount of important data in the data file.

There are also several backup data files but they are stored in the same
directory on the X drive that the current data file is stored.

Several days ago an employee attempted to delete several of the older
backups but mistakenly highlighted all the data files (current and all
backups) and deleted them.

When others tried to access the scheduling program the next day they
obviously could not do so and it was determined that the files were
mistakenly deleted.

During the time between deletion and discovery several employees used
the X drive to do some word processing work.

Upon discovery, a boss installed a data recovery tool (backtolife??) but
could not get it to work. He then installed a second one with the same
result. He then deleted both programs.

I then found UnDelete 2.0 from Executive Software (could not find 3.0)
and used Executive's "Deleted File Analysis Utility". We were able to
see some of the files from the recently deleted programs referenced
above but could find no data files from the scheduling program.

Is there any software we can try to recover these 'lost' files?

If not, is there any company that would be able to do so?

Is it true that once you write over deleted files they are deleted for
good and would the boss' install and uninstall of the recovery apps have
done more harm than good?

Relevant Pages

  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... You'll not be using most of the system databases intensively so you don't need to seperate them, I mean locating them on different physical disks. ... If it's being used intensively in your environment then you should locate it's log and data files on different physical disks. ... For this question you must understand the reason why we should seperate data and log files. ... Of course these drives must be physically seperated so that you'll gain performance benefits. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... However for the Install I don't see that the actual core db components there ... According to the database files, you can create your database files on ... Of course these drives must be physically seperated so that ... We are physically separating log and data files on separate disks. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... However for the Install I don't see that the actual core db components ... databases/log files on a separate drive, ... Of course these drives must be physically seperated so that ... We are physically separating log and data files on separate disks. ...
    (microsoft.public.sqlserver.setup)
  • Re: tempdb on C drive?
    ... performance from having the tempdb data files, User db data files and Log ... files all on different physical drives or drive arrays. ... While adding more log files to the log drive array decreases the ...
    (microsoft.public.sqlserver.setup)
  • Re: HELP! on Recovering Data - Corrupt System File
    ... > As long as you set the jumpers on the hard drives correctly (either ... > take ownership of the old files and folders. ... >> Hoping to get some pointers on recovering some large data files and old ... >> previous restore points manually via XP's Recovery Console, ...
    (microsoft.public.windowsxp.configuration_manage)