Understanding about activity log backups/clones

Frequently Asked Questions

Q1. How far back can we get the activity log information?

Answer: It depends on the tenant. If a tenant has not been cloned or subject to cleanup, then it is possible to retrieve activity log information that dates back to its creation.

Q2. Can you please explain why we will not be able to see the activity log due to the following: 

  1. What do you mean by "clone" - The tenant that was just cloned or the tenant whose data was cloned?
  2. What is do you mean by "clean up"?

Answer:  Cloning is copying a tenant configuration and data from one active environment into a different environment. Cleanup deletes all the data in a tenant, keeping the backup or not as per request.

After either of those operations, you will not be able to recover the whole activity log.

In a scenario where Tenant A and Tenant B exist and both tenants have their individual activity logs:

  • If we clone data and configuration from Tenant A to Tenant B, activity logs of Tenant B will be lost, but the activity log of Tenant A will remain intact.
  • If we delete all the data of Tenant B, activity logs of Tenant B will be lost.

Q3. Can’t we clone the Activity Logs from Tenant A to Tenant B?

Answer:   Yes we can clone an activity log from Tenant A to B, but that needs to be specifically requested.

Q4. Why will the activity log be lost -- aren't we just deleting the data?

Answer:   Deleting data from the tenant also deletes the activity log for that tenant, which can't be recovered. To avoid this, request a backup of the activity log before deleting tenant data.


NOTE: The daily backups that happen only take back up Cassandra's data, including activity logs and history logs. So users need to make a separate request for activity and history log backup.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.