Obtaining a Rekey Report
LDT generates a report automatically after completion of a key rotation. The report lists the files in the GuardPoint and the key and version of the key applied to each file. This kind of report may be a common compliance requirement.
The administrator can also request a rekey report during rekey, if the need to see the partial transformation results so far.
About the rekey report
On Linux hosts, LDT writes rekey reports to a local file on the agent host in /var/log/vormetric/. The file name begins with ldaudit-log-. It is followed by the file system directory name, GuardPoint directory name, and a timestamp. For example, for a GuardPoint at /oxf-fs2/gp2 with rekey completed on November 19, 2016, just after 2:00 p.m. (hour 14), the rekey report file name would be ldtaudit-log-_oxf-fs2_gp2-2016111914917.
The report includes:
-
Total number of files in the GuardPoint
-
Number of files transformed
-
Rekey start and end times
-
List of all files transformed
-
Applied key and key version for each file (for example, files in different resource sets might have used different keys)
Manually generating a rekey report
To generate a rekey report manually, use the following command:
voradmin ldt rekey report <GuardPoint> [<logfile>]
In <GuardPoint>, type the GuardPoint path. In <logfile>, you can optionally direct the output to a file. If no logfile is specified, the report displays on stdout.
