- Data Migration
- Legacy Data Remediation
- Restoration, Extraction & Culling
- Expert Opinion
- IT Archeology
- TapeErase Software
The term indexing of data can be somewhat misused in certain parts of discovery. In a very generic sense we see it used as a means for obtaining some information about a population of data than is immediately obvious by a volume name or file name. In a truer sense indexing relates to an in depth crawl of all of the data at a file and text level to enable a content understood query about that population of data. Here SullivanStrickler makes use of a variety of levels of inquiry into a data population as a means of providing the client with information that will enable the most economic course of action to take regarding a particular matter. We provide the following levels of interrogation.
At SullivanStrickler we do not supply Project Management for discovery matters at the point of hosted review. We do supply Project Management at a strategic point where the data is initially being discussed as being potentially required. We believe that this stage is critically important to the resulting overall costs incurred for the matter and to provide the decision makers with a better understanding of the likely outcome from discovery. If the right data is targeted for collection, collected in the right way and culled appropriately then the amount of waste or junk data is reduced. If junk data is reduced to the minimum then the discovery and review costs are reduced, and better decisions will be made. Quite simply, get it right at this stage and you save big on the subsequent stages.
Indexed Content - Involves the complete running of the whole tape enabling queries to be applied in search of targeted content such as an .EDB.
Restored Tape - Involves the running of the whole tape with a logical read of the complete data sets resulting in the data landed to disk such that the contents can be read through a normal folder structure.
Forensic Scan - Involves the running of the complete tape extracting key metadata and populating a database with that metadata to enable the understanding of the tapes contents for later interrogation and targeted extraction. Metadata will include filename, path, extensions, backup time, creation/last accessed and modified times etc.
Session Scan - Involves the running of the complete tape to ascertain backup session information and server ID's that were employed in the backup of the tape.
Header Scan - Involves a brief run of the tape to ascertain header information such as backup time and the amount of data residing on the tape.
A general understanding of the corresponding run times can be seen in the table below, but the run times can change considerably by factors such as whether the tape is part of a multiplexed data set, the number of files present, the block sizes employed, firmware cache and other factors. Costs can be understood to vary accordingly.