Script (.pdf file, 8 MB) - SAP MaxDB

More documents

Recommendations

Info

Activate automatic log backup to protect the database against LOG FULL situations. When the number of entries written to the log equals the value of the "AutoLogBackupSize" parameter, this data is written to the defined backup template and the log area is released for overwriting. The log area is not deleted by being overwritten with dummy data. Each log area is stored in a separate backup <strong>file</strong> to which a version number is assigned. It is only possible to perform automatic log backups to backup <strong>file</strong>s. In turn, these must be backed up to tapes or backup servers with the relevant tools. The automatic log backup can also be used alongside script-controlled log backups as a safety net in case the script fails. Automatic log backup must be deactivated whenever a script-controlled log backup is performed (for example, with the dbmcli –U c autolog_off command). The longer the duration of data backup actions performed with the utility task, the more important automatic log backups become, since the utility task cannot be used for other purposes during this time, which means that you cannot start any interactive log backups. For example, if data backups take a long time in online mode because backup media are slow, it is possible that online activities carried out during this backup could cause the log area to become full. If automatic log backup is activated, the log area can still be backed up when the utility task is occupied, thereby preventing a LOG_FULL situation.
To activate the automatic log backup function, create a corresponding backup template with Backup Type "LOG". Next, activate the automatic log backup function by setting Automatic Log Backup to "ON". As always, an initial data backup must exist before you can activate the automatic log backup function. Otherwise, the Wizard does not offer this option. Automatic log backup remains active until it is deactivated manually or an error occurs during the backup process. You check the status of the automatic log backup function, for example, on the Log Area tab page of the registered database instance.
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 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 and 48: If you use files for the data backu
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

Script (.pdf file, 8 MB) - SAP MaxDB

Create successful ePaper yourself

Delete template?

Save as template?