Note that these methods (HPA/DCO and AMA) are mutually exclusive. A drive that
supports HPA/DCO will not support AMA, and a drive that supports AMA will not
support HPA/DCO. Also, while HPA and DCO are related features for a given
drive, HPA has a unique attribute (volatile, or temporary, removal) that
distinguishes it from DCO and AMA. For that reason, this section will cover volatile
HPA removal as a separate topic before addressing non-volatile (permanent)
removal of HPA/DCO or AMA.
TD4 also provides the ability to “shelve” a DCO or AMA, which means disabling a
source drive DCO or AMA for the purposes of evidence duplication and then
putting the same DCO/AMA back after the job is complete. See “Duplicating”
on page 53 for more details on shelving a DCO.
4.6.2.2 Volatile HPA removal
HPA can be disabled without making a permanent modification to the drive. This is
known as volatile, or temporary, removal of the HPA configuration. When a drive
that has had its HPA removed in this manner is removed from TD4 (or is otherwise
powered down) and then reconnected, it will always come back in its original state
(with the original HPA configured and enabled). Since this is a temporary drive
configuration change only (not a change to the data stored on the drive), TD4
automatically disables HPA on any drive connected to one of its source ports. Since
DCO and AMA settings can only be disabled on a permanent basis, TD4 does not
automatically disable them on connected source drives.
In the case of an automatic, volatile HPA removal from a connected source drive, the
TD4 user interface makes it obvious what has occurred by stating how many HPA
sectors have been exposed, as shown in the following screenshot.
Chapter 4 Using TD4
42
OpenText™ Tableau™ Forensic TD4 Duplicator
ISTD230100-UGD-EN-1