on 09-26-2012 9:39 PM
We are in the process of migrating from MAXDB 7.3 to version 7.6.03.09. Currently on V7.3, we have databases in one location that are kept in sync at a 2nd location by backing up and restoring incremental backups. I'll refer to that 2nd location as our warm standby location. Periodically, we perform a full backup (backup_start mediumname migration pages) on the warm standby databases. We then restore that to what we call our TEST system so developers can have a somewhat fresh location to do testing. We go from warm standby to TEST because they are both on the same network while the source databases are scattered all over the country. It all works fine on 7.3. However, on 7.6, the "migration" evidently is no longer supported as a parameter on the backup_start command. We have found that after we perform a full backup of the standby database, we can no longer do any incremental restore to same standby database as it results in an "Incompatible incremental backup" error. I understand exactly what that error means, but I am seeking a way to continue doing things as we always have. It is not feasibly to take full backups of the source systems and restore to the TEST systems.
So, in a nutshell, I'm wondering with the absence of the "migration" parameter, is there some other option I'm missing that would allow us to back up our warm standby databases?
Thanks.
Hello,
1. Please review the documents at
http://maxdb.sap.com/doc/7_6/default.htm
-> Tutorials
-> Database Administration Tutorial
"Setting Up and Updating Standby Instances" and "Setting Up and Updating Standby Instances"
and at
http://maxdb.sap.com/doc/7_6/default.htm
Concepts of the Database System
Replication and High Availability
2. Please review SAP note:
952783 FAQ: MaxDB high availability
3. Incremental Data Backup has all data that has been saved since the last complete data backup
of the database instance. Please review SAP note 1377148.
"Incompatible incremental backup" error:
Before to restore the incremental databackup you need to restore the complete databackup created
before this int databackup. After you restoreed the int databackup you could continue to restore the logbackups or restart the database.
Regards, Natalia khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Natalia, Hello Terry,
backup a stand by database - even in admin mode - creates a new database ident for the target system. This avoids any further restore pages which belongs to a database with a different DBIdent.
This is a check which avoids that you mixe backups from different databases.
It is not supported anymore to restore pages of one instance to another one if the DBIdent does not match between DB-Instance and backup.
=> after you create abackup of the target system you cannot restore pages anymore from the source system!!! You have to start with a new complete backup with initialize of the source system.
See also CSS-Ticket 898352 2012
Regards, Christiane
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.