Script (.pdf file, 8 MB) - SAP MaxDB
Script (.pdf file, 8 MB) - SAP MaxDB Script (.pdf file, 8 MB) - SAP MaxDB
The "Start" button now becomes active and you can start the recovery. The process stops after the complete data backup has been recovered, and you can continue the process by recovering the incremental backup. Alternatively, you can stop the recovery at this point by choosing Cancel and restart it later as long as the database instance has not been switched from the ADMIN to ONLINE operational state in the meantime. This makes it possible to build a shadow instance manually. The next unit provides more information about these downtime security solutions with MaxDB.
The system behaves in the same way after the incremental backup has been recovered: The Wizard stops and gives you the option of interrupting the recovery process. At the end of the recovery process, the "Results" tab page displays a summary of the process including the return values of the various steps. Return value -8020 displayed here is not an error, but an indication that this log backup has been completed successfully and the next log backup has been requested.
- Page 2 and 3: This session is aimed at a wide aud
- Page 4 and 5: To prevent data loss in a database
- Page 6 and 7: In this second chapter, the differe
- Page 8 and 9: The data pages to be backed up can
- Page 10 and 11: A complete data backup stores all u
- Page 12 and 13: MaxDB supports multiple external ba
- Page 14 and 15: In the next step, you select a medi
- Page 16 and 17: In addition to complete data backup
- Page 18 and 19: As with complete data backups, you
- Page 20 and 21: The backup history shows the increm
- Page 22 and 23: MaxDB gives you the option of using
- Page 24 and 25: Interactive log backups back up all
- Page 26 and 27: As with data backups, you first hav
- Page 28 and 29: Activate automatic log backup to pr
- Page 30 and 31: Database Studio also gives you the
- Page 32 and 33: Before you overwrite the backups of
- Page 34 and 35: Three options for analyzing backups
- Page 36 and 37: To ensure data security, it is nece
- Page 39 and 40: In this 3 rd chapter, we take a loo
- Page 41 and 42: The following files contain informa
- Page 43 and 44: The following slides explain the re
- Page 45 and 46: You select the complete backup as t
- Page 47: If you use files for the data backu
- Page 51 and 52: All transaction-relevant actions ar
- Page 53 and 54: Step 2: The existing pages from the
- Page 55 and 56: Step 3: Restoring changes after dat
- Page 57 and 58: Step 3: Option 3: This variant als
- Page 59 and 60: This slide shows the typical action
- Page 61 and 62: SAP note 628131: SAP DB/MaxDB opera
- Page 63 and 64: Task that started the recovery but
- Page 65 and 66: While a Recovery is active, you can
- Page 68 and 69: In case you‘re ever in need of mo
- Page 70: Thanks a lot for your interest in t
The system behaves in the same way after the incremental backup has been recovered: The<br />
Wizard stops and gives you the option of interrupting the recovery process.<br />
At the end of the recovery process, the "Results" tab page displays a summary of the process<br />
including the return values of the various steps.<br />
Return value -8020 displayed here is not an error, but an indication that this log backup has<br />
been completed successfully and the next log backup has been requested.
Change language