Script (.pdf file, 8 MB) - SAP MaxDB
Script (.pdf file, 8 MB) - SAP MaxDB Script (.pdf file, 8 MB) - SAP MaxDB
The "Data Carriers" tab page shows detailed information about the backup files. This tab page also displays the log backups required to fill the transactional gap until the first log entry of the online log volume. The "Start" button is grayed out until all inconsistencies have been eliminated from the backup history. In this example, the "resolve" function is required because single templates point to different file names. The following slide shows how to resolve the problem using the automatic function in Database Studio.
If you use files for the data backup, the definition of the data medium may have changed several times in the meantime from one file name to the next. Database Studio recognizes this based on the information in the backup history and offers to create temporary media definitions automatically in this case. You can decide at this point whether these definitions are to be retained afterwards or deleted automatically. Based on the backup history in this example, the decision has to be made for both the complete backup and incremental backup.
- 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: You select the complete backup as t
- Page 49 and 50: The system behaves in the same way
- 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 "Data Carriers" tab page shows detailed information about the backup <strong>file</strong>s.<br />
This tab page also displays the log backups required to fill the transactional gap until the first<br />
log entry of the online log volume.<br />
The "Start" button is grayed out until all inconsistencies have been eliminated from the<br />
backup history.<br />
In this example, the "resolve" function is required because single templates point to<br />
different <strong>file</strong> names.<br />
The following slide shows how to resolve the problem using the automatic function in<br />
Database Studio.
Change language