Rollback for Data Privacy Clone in sub-production environment

[Heather White]

Hello Community,

Is it possible to roll back a data privacy clone in a sub production instance? 

It looks like the job can be rolled back but the data doesn't actually change.

Thanks,

Heather

[Tanushree Maiti]

Hi @Heather White 

"

1. Select an anonymization job that is in a Completed state.
   • After the job has run, the data will be anonymized for the selected configuration.
   • In the job summary, the Time remaining to rollback field informs of the expiration time. Within this timeframe, you have the ability to roll back the job."

   2

   • Rollback is limited to a few days, per the configured expiry duration of the RollbackContext of the new RollbackType REDACT. After expiration of the RollbackContext associated with a data privacy job, the rollback function is no longer available for that job.
     • A rollback context from de-anonymization is saved for three days by default.
     • The default expiry time can be set to a value greater than one by the data privacy administrator in the RollbackContext of the new RollbackType REDACT. Set the value in the Glide system property glide.rollback.expiration_days_redact. See Roll back and delete recovery.

       To learn more about adding or creating a system property, see Add a system property.

       for additional information.
   • Rollback is available for data privacy jobs that are in a Completed, Canceled, or Error state.
   • For every successful sys_user de-anonymization job which is configured with a data privacy policy with rollback support turned on, a rollback context is created. There can be at most one rollback context per data privacy job.

Refer:

Roll back a data privacy job 

Data privacy job rollback