S
slacroixak
Guest
Many thanks you for your point Slegian, The KBase link you shared seems to be broken. Here is an attempt to share it again (based on the KBase ID): knowledgebase.progress.com/.../How-many-online-probkups-000068748 So the limit is 65535 and not 32767, and we should definitely avoid overflowing that limit. Fine. Actually, the original point of my question was to avoid this kind of issue. Yes I intent to use probkup with the online option. Now I want to perform a full backup from time to time (every year or so), so this should reset the block counter. My main idea is to perform an incremental online backups every hour, as a start. Then roughly... every day at some point (say around midnight) do another one with -io 25 so it includes a full day, I will keep track of the daily files until I reach 10 days Then every 10 days, do another one with 260 (I have to check the number, but including a few extra hours is not a big problem) I will keep track of the 10 days files until I reach 100 Every 100 days I do another with -io around 2610 Every 1000 days a big one with around 26100 The idea is that 243 days after a full backup, I would be able to restore a database somewhere with a reasonable set of files like : full + inc200 + inc100 + inc40 + inc30 + inc20 + inc10 + inc4 + inc3 + inc2 + inc1 Yes we should issue a few warnings before reaching 65000, so it should roughly be able to go up to about 2500 days, so about 7 years, but as said above; I'd like to retrigger a full backup every year or so. The peculiar issue to find cleaver naming for the incremental backup files so it shows when each file is produced and the period of data that is included with the the -io overlap factor.
Continue reading...
Continue reading...