Cloning and the 90 data copy option

KB15
Giga Guru

When the "Amount of data copied from large tables" is set to 90 days, the documentation shows:

"Clones the number of days of historical data from large source tables, including task, pa_scores, and metric_instance. By default, the target instance receives the latest 90 days of historical data from the source instance."

Why would I see incidents that are beyond 90 days? Is it based on creation or update of the record?

1 ACCEPTED SOLUTION

Stephen Sturde
Tera Guru

Hi KB,

The 'incident' table is not one of the ServiceNow tables referenced in '...large source tables...' ServiceNow is referring to logs, metrics, attachments, workflow contexts, and other tables that collect significant numbers of administrative data. 

Incidents and other task-based records are considered core data and the entire table is cloned. If you want to limit the amount of Incident data in a clone, you'll need to create a custom clone data preserver. 

https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/managing-data/task/...

-Stephen

View solution in original post

5 REPLIES 5

Stephen Sturde
Tera Guru

Hi KB,

The 'incident' table is not one of the ServiceNow tables referenced in '...large source tables...' ServiceNow is referring to logs, metrics, attachments, workflow contexts, and other tables that collect significant numbers of administrative data. 

Incidents and other task-based records are considered core data and the entire table is cloned. If you want to limit the amount of Incident data in a clone, you'll need to create a custom clone data preserver. 

https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/managing-data/task/...

-Stephen

Thank you.

For some reason I read that as "large source tables...such as" instead of just those specified tables.

Did you ever have luck with this or find a solution for not cloning all of the task data?  We have a similar requirement, and that option doesn't even seem to impact the tables it lists.

I don't think there's a solution. If task is considered a vital table, it may not be avoidable.