6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 3: Backup and RecoveryBackup DatabaseAssuming the size of your database and backup window permits it, we recommend afull database backup be taken every day. For databases that are too large for daily fulldatabase backup, a full backup should be taken weekly. Transaction LogsBacking up the transaction logs is critical. If the filespace is used up, the database willstop, which stops R/3.Between 6:00 a.m. and 9:00 p.m., we recommend that you back up these logs at leastevery three hours. A company with high transaction volume carries higher risk andwould increase the frequency accordingly, perhaps to every hour. Similarly, if you havea Shipping department that opens at 3:00 a.m. and a Finance department that closes at10:00 p.m., you would need to extend the start and end times. Operating System Level FilesThe frequency of the operating system level backup depends on the application. If thesefiles must be kept in sync with R/3, they must be backed up with the same frequencyand at the same time as the database and log backups. An option for a non-sync-criticalsituation is to back up these operating system level files once a day.It is important to set up a proper procedure to back up the valuable system information.Procedures should be defined as early as possible to prevent possible data loss. Resolve thefollowing list of backup issues before you go live: Decide how often to perform complete database backups Decide whether partial or differential backups are necessary Decide when to perform transaction log backups Have the ability to save a day’s worth of logs on the server. Provide ample disk space for the transaction log directory Consider using DBA Planning Calendar (DB13) to schedule transaction log backups Set the appropriate R/3, operating system, and database authorizations Create a volume labeling scheme to ensure smooth operations Decide on a backup retention period Determine tape pool size (tapes needed per day × retention + 20 percent)Allow for growth and special needs. Initialize tapes Determine physical tape storage strategy Decide whether to use unattended operationsIf using unattended operations, decide where (in CCMS or elsewhere). Document backup procedures in operations manual Train operators in backup procedures3–12Release 4.6A/B