Planning data storage on the IBM Storage Protect server

Edit online

In SAP terminology, backup refers to the backup of data; archive refers to the backing up of log files. Data Protection for SAP uses the IBM Storage Protect™ archive function for backups and archives.

Tape storage is the preferred media for storing the database contents as it provides the best data throughput for backup and restore. In addition, the backup file sequence is maintained for restore, which improves restore processing time. A disk-tape storage hierarchy is used for backing up log files. Each log file must be backed up immediately after it is placed in the archive directory. This action provides the best protection against data loss, and eliminates the requirement to mount a tape for each 20 MB file.

Tape storage is the preferred media for storing database contents as it provides the best data throughput for backup and restore operations. For a large scale-out system, the number of required tape drives might become too large. In this case, use a virtual tape library (VTL). A disk-tape storage hierarchy is used for backing up redo log files. This action provides the best protection against data loss, and eliminates the need to mount a tape for each redo log file.

Data Protection for SAP transfers data to and from the backup server through single or multiple (parallel) sessions to the IBM Storage Protect server. Each session must have a storage device that is associated with it. The SAP backup ID is persistently linked with each backup file. This backup ID can be used later to determine all files that are required for a complete restore.

Collocation is an IBM Storage Protect function that ensures client data is maintained together on one tape. Deactivate collocation in these situations:
  • Deactivate collocation for Data Protection for SAP backups when you enable parallel sessions for use with multiple tape drives in parallel.
  • Deactivate collocation when you use the multiple log copy function.

SAP administration tools can generate information about backups that are on the IBM Storage Protect server. This information is accessible by viewing the local (detailed) backup log or by using the Data Protection for SAP File Manager (backfm). In addition to viewing backups, File Manager also allows the administrator to bypass SAP tools to query, delete, or restore backups and files.

To improve availability (alternate servers) or performance (multiple servers), configure Data Protection for SAP to use multiple IBM Storage Protect servers. Consider the location of all backup data before you remove an IBM Storage Protect server from the Data Protection for SAP profile.

Because Data Protection for SAP accesses only those servers that are defined in the profile, be cautious when you remove an IBM Storage Protect server if it contains valid backup data.

Database backups are retained for a specified period and then become obsolete. Manage backup storage space efficiently, by deleting obsolete backups in one of the following ways:
  • Set an appropriate archive retention period with IBM Storage Protect options.
  • Use the Data Protection for SAP backup version control function. When the number of backup versions that are specified by this function is exceeded, entire backup generations are deleted. The backups that can be deleted are full backups and all related Oracle redo log redo log files or DB2® partial and log file backups.

The SAP backup log might still list deleted (expired) backups since this log cannot be updated by Data Protection for SAP.