SAP MaxDB: Database Administration Using Database Studio
Use
Database Studio is the new SAP MaxDB database administration tool. This section describes Database Studio from the high availability viewpoint and recommends how you can use it to increase the availability of your SAP MaxDB database.
Features
-
Monitoring data and log storage
You can use Database Studio to see how full the database is. Use this information to schedule manual log backups if necessary to avoid downtime. A value of 100% in either case stops the database from processing, so preventing SAP applications from continuing.
-
To perform certain administrative tasks for high availability, you need to check which operational state the database is in.
-
Background jobs
You can use Database Studio to show whether a backup, a structure check, or an update statistics is active in the background. For more information, see Monitoring Databases: Overview
-
Filling level of the log area
You can activate automatic log backup .
-
Configuration of the database
You can configure the database using Database Studio as described below:
-
You can display and modify the configuration of the database parameters.
-
Adding Data Volumes , Adding Log Volumes
You can expand data and the log area (physical storage area) of the database by adding data and log volumes.
You can configure the system to automatically add data volumes and thus increase the size of the data area when necessary.
-
Activities
You can use Database Studio to control and monitor the database system and to execute backups and recoveries. You can perform all monitoring functions available in the Database Studio using the Database Assistant in the CCMS of the SAP system. You can schedule backups in operational state ONLINE using the DBA Planning Calendar in CCMS.
Backup
Database Studio lets you perform complete data backups , incremental backups (that is, a backup of only the modifications made since the last data backup), and interactive log backups . You can also activate automatic log backup . The backup or recovery operations apply to only the addressed database.
Automatic log backups are performed using predefined parameters whereas ad-hoc data or log backups are performed interactively. Incorrect entries or a timeout due to delayed input can cause the backup to abort, possibly leading to downtime.
Each backup is done to a data carrier using a backup template . You can do parallel backups, allowing faster throughput.
Here are some recommendation for your backup strategy: