on 04-29-2008 10:37 AM
Hi,
is there a possibility to restore or import the backup history when creating a new instance? And is there a way to back it up?
This would be very handy in case of a disaster recovery (machine completely dead; restore from tape/backup media). Then it would be possible to make a timestamp recovery without the need to look for the different needed log backups.
bye
Chris
When you take up backup of Maxdb on tape through external tools it writes a backup history file on tape.
When you want to restore the backup on a new server you need to restore the external backup history file first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's right. dbm.knl and dbm.ebf is saved on tape after every backup operation. But if you create a new instance there's no possibility to recover the backup history + external backup history first.
Is the only to recover a database on a clean server by creating the instance, going to state online, then offline, afterwards overwrite the dbm.knl and dbm.ebf files manually and then restore the database?
Hi Christian,
for the case of desaster recovery the necessary steps are simple:
- create a new instance on a new server
- recover from backup medium (of course not from the backup history)
When you recover log-backups from a medium, you just provide the start number from which on the DBMGUI should start to recover. It will then increase the number until no more log-backups can be found.
- After that you can start the database and with that you're done with the desaster recovery.
Keep in mind: desaster recovery is an action that should produce the latest state of the database available through the backups. It's not designed to make point-in-time-recoveries extremely easy (although you can also specify the recover until option all the time).
KR Lars
Hi Lars,
thanks for your answer. I agree with your opinion about disaster recovery. But very often users delete some records or whole tables accidentally. So we have to make a timestamp recovery on a different instance/machine to export the tables and copy them to the real instance.
Therefore it would be very nice to have an import of the backup history on a fresh database.
bye
Chris
>
> Hi Lars,
>
> But very often users delete some records or whole tables accidentally. So we have to make a timestamp recovery on a different instance/machine to export the tables and copy them to the real instance.
>
Wow - you don't need an easy backup - you need a better designed access to your data.
Point-In-Time recoveries are actions of last hope (check my blog on this. [Point-in-time-recovery considered harmful|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/8636] [original link is broken] [original link is broken] [original link is broken]; )
> Therefore it would be very nice to have an import of the backup history on a fresh database.
Regards,
Lars
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.