Laserfiche WebLink
day, it is important that unattended backups not require human intervention. Incremental backups <br />run at night will usually not fill a tape and will definitely take less processing time than a total <br />backup. Additionally, retrieving a lost file from an incremental backup takes less time than from a <br />total backup. <br />The backup procedure described below only applies to files at RTi. The State and CSU will perform <br />backups using their own methods. The development team has agreed that RTi will be the repository <br />for all current code and data, regardless of whether RTi personnel are working directly on the files. <br />Methods will be developed (using standard UNIX commands) to automatically copy recently- <br />changed files from CSU to RTi. This procedure will be carried out before automatic backups are <br />performed at RTi so that each day's work can be copied to RTi before backups are made. <br />Alternatively, disks at CSU may be mounted on RTi machines using NFS so that no transfer is <br />required. <br />The backup procedure will be carried out for specific directories on the system. The system will be <br />accessible from the machine with the tape device through the use of NFS. Consequently, all <br />directories that are to be backed up must be accessible via NFS from the machine that is performing <br />the backups. Directories to be backed-up will be specified to the backup program. In general, these <br />include directories that contain important system configuration information (e.g., the <br /> file), and important source code and data. The backup script then changes to <br />/etc/passwords <br />each of these directories and backs-up the system from the specified directory down using the UNIX <br />cpio tar <br /> (or ) command. Each directory is saved as a separate tape segment (more than one segment <br />mt <br />can exist on one tape) so that the fast-forward feature of the UNIX command can be used to <br />rapidly skip segments that are not of interest. A formatted log file is created indicating each file that <br />is saved. These log files are then used when searching for a tape to reload. <br />Daily incremental backups will be performed on Monday through Thursday late at night (e.g., 11:45 <br />P.M.), saving files that have changed in the previous day (Monday's backup saves the previous two <br />days' work to account for Sunday). A weekly incremental backup will be performed late Saturday <br />night. If necessary, weekend backups will be performed also. The backup tapes and log files will be <br />referenced using a file name that has the form: <br />tDDMonYY.host <br />where t = the backup type (e.g., D for daily, W for weekly, T for total); DD = the day (e.g., 01, 30); <br />Mon = the month abbreviation (e.g., Jan, Feb); the year (e.g., 01, 99); and = the name of <br />YY = host <br />the host on which the backup is being made (e.g., crdss5). Consequently, the daily backup for June <br />30, 1994, as performed on machine "crdss5", would be: <br />D30Jun94.crdss5 <br />backsys <br />The backup program developed by RTi (called ) has default settings that specify backup <br />interval and other parameters, but also allows these values to be set with command-line arguments. <br />For example, the command: <br />backsys -d <br />indicates that a daily backup is being performed; consequently, a one-day increment is assumed. <br />2 <br />A275 05.10.94 1.05-24 Malers <br />