Protect synchronization

Synchronization in Protect refers to the process of aligning the data protection standards and data access rules created in Collibra with your data sources. This ensures that data protection measures are enforced across all connected data sources.

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

In this topic

Sync types

Protect offers the following types of sync:

  • Lazy sync (default): All standards and rules in Protect are synchronized with your data source only if any standards, rules, or target data elements in Collibra have changed since the last synchronization.
  • Full sync: All standards and rules in Protect are synchronized with your data source regardless of whether any standards, rules, or target data elements in Collibra have changed since the last synchronization.
Note 

Regardless of the type of sync:

  • Failed standards and rules are automatically included in the next synchronization cycle.
  • Synchronization is skipped if an Edge site is unavailable, and it is retried in the next cycle.

Sync configuration

Lazy sync is enabled by default, while full sync is disabled by default. You can enable or disable lazy sync and full sync using the Lazy sync enabled and Full sync enabled settings in Collibra Console. You can also choose to enable both types of sync.

Tip If you have the Protect > Edit or Protect > Administration global permission, you can start a full sync at any time using the Sync Policies button on the Data Protection Standards and Data Access Rules tabs in Protect.

Both types of sync run in the background on a configured frequency. For a lazy sync, the default frequency is every 1 hour. For a full sync, the default frequency is every 1 day. You can change the frequency using the Lazy sync delay and Full sync delay settings in Collibra Console.

Sync processes

The sync includes the following processes:

  • Aggregation of all standards and rules with a computation of the following:

    • Which columns need to be masked for which groups.
    • Which tables need to have a row filter.
    • Which tables and columns need to be granted access.

  • On the databases of the data sources such as Snowflake:

    • Creation and application of masking.
    • Creation and application of row filters.
    • Granting of access to groups on tables and columns (depending on the underlying database).

Sync statuses

The following table describes the statuses that may be shown in the Synchronization Status column on the Data Protection Standard or Data Access Rule tab.

Sync status Description
Draft Draft of the standard or rule is created.
Pending Standard or rule is created (published), and the sync has begun.
Active Sync is complete, and the standard or rule is enforced in the data source.
Failed

Sync has failed, and the standard or rule isn't guaranteed to be enforced in the data source. The sync, however, is retried in the next cycle.

Tip 
  • For information about the error, click next to the status.
  • Sync fails typically due to the reasons described in Protect errors.
Delete Pending Standard or rule will be deleted during the next sync. This sync status is shown after you delete a standard or rule.
Not Deleted Sync has failed for the deleted standard or rule, meaning that the standard or rule isn't deleted in the data source. The sync, however, is retried in the next cycle.

Tip For more information about the error, click next to the status.

Status in the data source

To view the status of a standard or rule in the data source, go to the database of the data source.