6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

ÃChapter 3: Backup and RecoveryBackupIf you do not have an offsite backup server, back up the transaction log backups to tapeafter each log backup and immediately send the tape offsite.Do not back up the logs to the tape drive in “append” mode and append multiplebackups on the same tape. If a data center disaster occurs, the tape with all these logswill be lost.Operating system level files, which must also be backed up, are for: Operating environment (for example, system and network configuration) R/3 files Spool files, if stored at the operating system level(system profile: rspo/store_location = G) Change management transport files located in /usr/sap/trans Other R/3 related applications Interface or add-on products, such as those used for EDI or taxes, that store theirdata or configuration outside the R/3 database.The amount of data is small in relation to the R/3 database. Depending on how your systemis used, the above list should only require several hundred megabytes to a few gigabytes ofstorage. In addition, some of the data could be “static” and may not change for months.The frequency of the operating system level backup depends on the specific application. Ifthese application files must be kept in sync with the R/3 System, they must be backed up atthe same frequency as the log backup files. An example of this situation is a tax programthat stores its sales tax data in files external to the R/3 database. These files must be in syncwith the sales orders in the system.A simple and fast method to back up operating system files is to copy all data file directoriesto disk on a second server; from the second server, you can back up those files to tape. Thisprocess minimizes file downtime.Use the sample schedule below to determine your backup frequency:Backup types is like a three-dimension matrix, where any combination can be used: What is backed up: full database vs incremental of the logs How the backup taken: online vs offline When the backup is made: scheduled vs nonscheduled (ad-hoc)3–6Release 4.6A/B