"incompatible incremental backups"?

[former_member192710]

Folks;

trying to get our MaxDB backup configuration organized in a way a little more "sane", I was about to replace the full backup done several times per day with incremental backup mediums / runs, which generally works but ends up like this: While recovering a full backup on a standby machine, trying to recover an incremental backup on the same machine reproducibly ends up like this:

ERR

-24988,ERR_SQL: SQL error

-111,Incompatible incremental backup

6,Data recovery failed

17,Servertask Info: because Error in backup task occured

10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT104 Result=1040

6,Error in backup task occured, Error code 1040 "incompatible_savefile"

MaxDB versions used on both machines are the same. I completely restored the database there using the latest full backup before trying to restore the incremental one. Tried to restore the incremental one using

>medium_put Dump "/backup/data/PV/maxdb/BFDATA_CURRENT3" FILE PAGES 0 8 NO

>recover_start Dump

So to ask: Are there any general considerations against using incremental backups in such a way (restore on different hosts)? Am I doing something else wrong here? MaxDB in use: X32/LINUX 7.6.03 Build 007-121-157-515.

Thanks in advance and best regards,

Kristian

Edited by: Kristian Rink on Apr 1, 2009 4:15 PM

[lbreddemann · Accepted solution]

>

> ERR

> -24988,ERR_SQL: SQL error

> -111,Incompatible incremental backup

> 6,Data recovery failed

> 17,Servertask Info: because Error in backup task occured

> 10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT104 Result=1040

> 6,Error in backup task occured, Error code 1040 "incompatible_savefile"

>

>

> MaxDB versions used on both machines are the same. I completely restored the database there using the latest full backup before trying to restore the incremental one. Tried to restore the incremental one using

hmm... how did you start the recovery of the full data backup before ?

What was the return-info?

Has the database been started/stopped between the recovery of full data backup and the incremental backups?

>

> >medium_put Dump "/backup/data/PV/maxdb/BFDATA_CURRENT3" FILE PAGES 0 8 NO

> >recover_start Dump

>

>

> So to ask: Are there any general considerations against using incremental backups in such a way (restore on different hosts)? Am I doing something else wrong here? MaxDB in use: X32/LINUX 7.6.03 Build 007-121-157-515.

Nope - this really should work.

If you're a SAP customer, it may be easier to open a support message.

That way we can easier handle the protocol files.

regards,

Lars

[former_member192710 · Accepted solution]

Hi Lars;

and first, thanks a bunch for your comments on that. Actually, your answer made me think and resolve my problem in this situation - indeed my scripts were messed up and the DB was brought online after restoring the FullDump but before restoring the Incremental one. Using this script on a newly created database now does correctly do as it is supposed to:

> medium_put FullDump "/backup/data/PV/maxdb/BFDATA_FULL" FILE DATA 0 8 NO

> medium_put Incremental "/backup/data/PV/maxdb/BFDATA_CURRENT1" FILE PAGES 0 8 NO

> service_connect

> recover_config FullDump

> service_release

> param_put CACHE_SIZE 3000

> db_admin

> db_activate ... , ...

> db_admin

> db_connect

> db_activate RECOVER FullDump

> recover_start Incremental

> user_create DOMAIN , ...

> user_create ... , ...

> db_online

Thanks a bunch again,

Kristian