OpenText Tableau TD2u Forensic Duplicator
The Information Company
23
A .LOG file is generated by the TD2u for each disk-to-file acquisition.
yyyy-mm-dd hh-
mm-sec
is the duplication task start date/time. The last part of the filename is the name of
the type of task.
4.4 Preconditions checking
Before starting a duplication, the TD2u automatically checks for a number of
preconditions. Some preconditions are warnings, and you can choose to continue or
cancel after viewing each one. Two preconditions (destination filesystem check and
locked encryption) pause the process and prompt you to intervene to clear the flagged
condition before automatically continuing. The following table summarizes the
preconditions checked by the TD2u prior to duplication:
Name
Clone or
Image
Destinations Type
Explanations
Source Hidden
Data Areas
Both
Warning
Reports that a DCO or AMA is in use on
the source disk.
The TD2u does not automatically
remove DCO or AMA on the source
disk, as doing so requires a permanent
modification of the source disk. You can
cancel the duplication and manually
remove the DCO or AMA using the Disk
Utilities option under the Main menu.
Source Fits into
Destination
Both
Fatal/Warning For Clone destinations, the destination
disk must be at least as large as the
source disk. For Image destinations, the
TD2u checks the available space on the
destination disk.
If it is possible that the source may not
fit on the Image destination
(compression permitting), this warning
informs the user. If it is certain that the
source will not fit on the Image
destination, this precondition is fatal.
Source Not Blank
Both
Warning
The TD2u checks select sectors on the
source disk looking for non-blank data
patterns. If all the checked sectors
appear to be blank, the TD2u warns
that the source might be blank. This
does not mean the source is
necessarily blank, but it could mean the
source has been partially wiped or that
hardware-based encryption (such as
OPAL SED) is present.