6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 13: Database Administration – Microsoft SQL ServerDatabase Backups with Microsoft ToolsThe offline backup is done when R/3 and the database are down. Here, we also use theoffline backup to also backup other files which are needed to restore R/3. Since highcapacity tape drives are now more common, it is simpler and safer to backup the entireserver. This full server backup eliminates the possibility of not backing up an important file.For smaller customers, the entire server could be backed up to a single DLT cartridge.At a minimum, backing up R/3 on SQL Server involves backing up the following SAPspecificand database-related directories: \usr\sap \usr\sap\trans of adm \data (the R/3 database files) \log (the R/3 log file) \tempdbIn addition to these directories, you must back up any directories and files for third-partyproducts, interfaces, etc. that store their data outside the R/3 database. Getting all therequired files and directories can be difficult, which is why we recommend that you backupthe entire server.The data in the database does not change while the backup is being made, which means thatyou have a static “picture” of the database and do not have to deal with the issue of datachanging while the backup is being run. With some third party applications, you cannotback up the files unless they are closed, and this is not possible unless R/3 and theapplication are shut down. Therefore, an offline backup needs to be done. A “full server”offline backup also gives you the most complete backup in the event of a catastrophicdisaster. On one tape, you have everything on the server.Due to system limitations on the documentation system, the location of the files in thisexample are presented differently from the recommendations in the SAP installationmanual.13–24Release 4.6A/B