Clean up data after a Hyperscale job execution

You can cancel a job execution and use Execution Status to track the cancellation process. If a load or post-load procedure fails, or if an execution is canceled, the job execution can be restarted.

During execution, the system creates data files and objects. After a Hyperscale execution completes, clean up generated data to free storage space and remove sensitive information.

After a Hyperscale execution completes, clean up the following items:

  • Data and masked files on the file server
    The unload service creates data files, and the masking service creates masked files on the file server. These files can be large (up to twice the size of the source data) and may contain sensitive information. Remove these files after the execution completes.

  • Objects on Continuous Compliance Engines
    Hyperscale creates objects such as connectors, rulesets, file formats, and jobs on associated Continuous Compliance Engines. Remove these objects after the execution completes.

  • Transient service data
    The unload, masking, and load services store transient internal data while the execution runs. Remove this data after the execution completes.