Protecting Teradata Appliances
Data on a Teradata appliance can be protected using LDT or IDT GuardPoints. In a Teradata appliance, the disks used by the database cannot be resized. So, when they are guarded as an IDT or LDT capable device, the metadata for those disks is stored externally in a directory on the local file system.
Based on your use case, fulfill the LDT or IDT requirements before proceeding. Refer to the following documentation:
-
The CipherTrust InPlace Data Transformation for Linux section of the CTE Agent for Linux Advanced Configuration document.
-
CTE Live Data Transformation document. To protect a raw device mounted on a Teradata appliance using an LDT GuardPoint, the linked LDT policy must use an XTS key only.
To protect a Teradata appliance:
-
Register the Teradata node with the CipherTrust Manager. Refer to the CTE Agent Quick Start Guide for details.
After registration, you can apply GuardPoints to the data stored on the device, for example,
/dev/sdb. -
Make sure the path
/opt/vte/vte-metadata-direxists. Create, if it does not. -
Apply a Standard GuardPoint to
/opt/vte/vte-metadata-dir. Refer to Creating Standard GuardPoints for details. -
Configure the device as IDT/LDT capable. Run the command:
voradmin idt config -external xform /dev/sdb -
Apply an IDT or LDT GuardPoint to the device, as appropriate. Refer to the following sections: