Database server considerations
In general, the production (SAP® database) server is the most critical component for data transfer, especially when parallelism is applied. As a result, special attention is given to the following items.
- CPU power
- Data transfer, data compression, local, or LAN-free backup operations can cause significant demands on the database server CPU. These demands are in addition to the application load caused by online backups. In many environments, the CPU is the most critical constraint. The CPU load for LAN-free backups (Managed System for SAN) can be reduced by managing the buffers.
- I/O paths
- Fast disk attachments with internal busses (like a peripheral component interface) and file system features (like caching or reading ahead) can improve data transfer rates. These attachments and features can be especially useful for backup and restore operations that contain a significant number of files and large data volumes.
- Volume Manager settings
- Volume Manager provides volume mirroring options that can significantly reduce the data transfer rate during restore operations. As a result, not using volume mirroring options during restore operations can improve the data transfer rate.
- Disk layout
- The manner in which the database files are laid out can affect data transfer rates. Since parallel is allowed, distribute data across several disks to take advantage of this feature.
- Disk layout
- The manner in which the database files are laid out can affect
data transfer rates.
Data Protection for SAP allows parallel access to database files during backup and restore operations.
Since parallel is allowed, distribute data across several disks to take advantage of this feature.
- Database size
- The size of a database can be reduced by offloading inactive data to an external archive.
- Size of the database files
- When similar files are the same size, multiplexing can be used to improve data transfer rates.
- Backup types.
- Online backups save database files, control files, and redo logs non-disruptively. However, more data is saved to redo log files during an online backup. The amount of data that is saved to redo logs during an online backup might be decreased when you use the file-online mode that is provided by SAP. A backup in this mode takes longer. Incremental backups reduce the backup time and the amount of data to be sent to the backup server while restore time might be increased. For incremental backups, Oracle RMAN must be employed. For details on backup options, refer to your Oracle and SAP documentation.