6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 1: R/3 System Administration BasicsSpecial Definitions The latest full backup tape will be bad. The one time you did not check the backup log will be the time when the backup fails. You will need a tape from the backup that failed. The computer room will be destroyed—along with all your backup tapes. What you did not write down, and forgot, is what you need to know. User transparent, is not. The Peter Principle will strike. A shortcut is the longest distance between two points. When you need to send an alpha page, a link in the e-mail system will fail. When a disaster strikes, and you need to be found, you will be out of the pager or cellphone coverage area. When a disaster strikes, and you need to be contacted, the battery in your pager or cellphone will be dead.There are terms used in this guidebook that have very specific meanings. To preventconfusion, they are defined below:This is where R/3 and the database resides.The system clock of the database server is the master clock for the R/3 system.This is where R/3 application runs.On a two-tiered system, this would be combined on the database server. Applicationservers can be dedicated to online users, batch processing or a mix.An installation of R/3 on a server.The two types of instances are central, and dialog. More than one instance could exist on aphysical server.The complete R/3 installation for a System ID (SID), for example PRD.A system logically consists of the R/3 central instance and dialog instances for the SID. Thisphysically consists of the database server and application servers for that SID.1–14Release 4.6A/B