Maximum number of changeId for CBT

Hello,

I wrote a program that by using CBT will give me the amount of changes on a particular VM. My concern is that if this program will introduce problems to any backup solution that uses CBT to enable incremental backups, like Veeam or vRanger on the same VM.

Let's say I need a good resolution from my  CBT script, and through the day I take 24 data points; now if my backup solution generates a backup job every 2 or 3 days, how can I be sure that it can still use that "old" changeId from 2 or 3 days ago?

In other words, how many points in time (changeId's) can I have and be able to call QueryChangedDiskAreas to get the changed blocks.

Any help is highly appreciated,

Juan Aristizabal.