Restoring database from all backup logs

[#1]

Hello,

I have complete backup with bad page and restoring process always stops at this page. I have also all logs backup.

After creating new instance and restoring from first log (restore medium) the following error occurred:

-8003 Log and data must be compatible 20018,DBIdentifier of DataVolume (host1:PSK_20100429_231846) and LogArea (host2:PSK_20050616_092436) does not match Log- and data area are not compatible because 'The DB Identifiers of data and logbackup are not equal'. k38headmaster, Error code 3800 "incompatible_log" RestoreLog, Error code 3800 "incompatible_log"

How to restore data from all logs or from complete backup without all pages?

[Former Member]

Hi,

Please check the no. of data files and log files and their sizes in the source system and make sure that you add data and log files to the new system to match that.

The error (8003 Log and data must be compatible) is basically that it is identifying the database backup as not matching the current configuration.

However, if you have any pages missing/bad, I do not think you can use the backup to restore. Better take a fresh backup from the source system and then try the restore.

In any case, try both these points I mentioned.

Best Regards,

Shitij

[lbreddemann]

> Please check the no. of data files and log files and their sizes in the source system and make sure that you add data and log files to the new system to match that.

???

Wrong! The data/log-area configuration can be totally different than it has been on the source system.

We don't save files - we save content to the backups!

> The error (8003 Log and data must be compatible) is basically that it is identifying the database backup as not matching the current configuration.

Sorry, but simply reading the [documentation|http://maxdb.sap.com/doc/7_7/28/f26ecdd8fc4f08bda683d62b60d29f/content.htm] would make you and everybody else know better!

MaxDB basically uses two areas to store data:

1) the data area where all data is stored as it is put to to the tables

2) the log area where all changes to the data is saved.

Since the changes only make sense if applied to the right data and in the correct sequence, both the data and the log area get stamped with an identifier (the DBIdent).

This DBIdent must be the same in both areas.

As it is also saved in data backups, you can restore a data backup into a database that has a different DBident than what is in the log area.

To avoid this, the 'restore with initialisation' feature is available.

> However, if you have any pages missing/bad, I do not think you can use the backup to restore. Better take a fresh backup from the source system and then try the restore.

That's right. There's no way to get the database up and running based on the broken backup.

It's crap, rubbish and useless.

If the original database is still available - get a new backup and start over.

If the original database is lost, then: sorry, you lost your data.

regards,

Lars