probkup online dbname incremental always have same size as full backups - Forum - OpenEdge General - Progress Community

probkup online dbname incremental always have same size as full backups

 Forum

probkup online dbname incremental always have same size as full backups

This question is answered

Hello

As my subject says, probkup online dbname incremental always have same size as my full backups.
I do this over years now and never got a bug like this.

Dayli i make full backup:
probkup online dbname backupfile -com -red 3

After that i check backup:
prorest dbname backupfile -vp

After that i make incremental backups every hour:
probkup online dbname incremental $hour_backupfile -io 2

I already tried without -io. Every incremental backup hase same size then full.
Maybe i have to mark db with rfutil for "baked up?

But documentation says that probkup does this on every backup.
Please help, i don't understand what happens.

I also watched backup status with promon:

08/07/18 Status: Backup
13:15:28

Most recent full backup: 08/06/18 19:30
Most recent incremental backup: 08/07/18 12:58
Database changed since backup: Yes
Sequence of last incremental: 2

Verified Answer
All Replies
  • the two are not compatible. incremental backups do not work with online backups.

  • Sounds like you are hitting this issue: knowledgebase.progress.com/.../P138656

  • Not sure that's 100% right (depending on your definition of "not compatible"). According to the wonderful folks in techsupport (via the knowledgebase), you can have an incremental backup online but it isn't as effective as an offline one:

    knowledgebase.progress.com/.../000054696 (mentioned in the detail).

  • Thank's for your link ( https://knowledgebase.progress.com/articles/Article/000054696 )
    Im wondering why i didn't found it my self. The solution is aweful...:

    "Dump and reload a productive database with 50g+" Just wow Indifferent and from 2016!
    Hopefully they fix this or have another workaround. Dump and reaload takes a lot of time.

    For me it is compatible! It worked like a charm over 2 years, already restored many times from online incremental backups with zero problems (In productive env's). Only difference in my lab was that offline incremental backup was smaller (size)  and finished faster then online incremental backup.

    Anyway, thank you all. Seems that we must go back to the roots with after image Hmm