File Types and Locations

The STA Services are comprised of executable scripts, java jar files containing server and client applications, configuration files, dump file, logging files, and a cumulative data file. This section describes their purposes and locations.

STA Services Daemon Startup/Shutdown Script

The STA Services daemon startup/shutdown script, staservd, and system run level symbolic links are located at:

/etc/init.d/staservd - Main startup/shutdown script
/etc/rc0.d/K04staservd - Symbolic link for system shutdown
/etc/rc1.d/K04staservd - Symbolic link for system shutdown
/etc/rc2.d/S96staservd - Symbolic link for system startup
/etc/rc3.d/S96staservd - Symbolic link for system startup
/etc/rc4.d/S96staservd - Symbolic link for system startup
/etc/rc5.d/S96staservd - Symbolic link for system startup
/etc/rc6.d/K04staservd - Symbolic link for system shutdown

The staservd init script and its associated symbolic links are created at STA install time by the STA installer. If there is a need to manually install and configure the STA Services daemon, see “Manually Install the STA Services Daemon”.

STA Backup Service Administration Utility

The STA Backup Service Administration Utility, staservadm, is a Perl script that calls a Java client application named ServerAdm that is contained in the staServerAdm.jar file. For Backup Service configuration information, see the “Configuring STA Services” chapter within the StorageTek Tape Analytics Configuration Guide. For Backup Service administration information, see “STA Backup Service”.

STA Resources Monitor Administration Utility

The STA Resources Monitor Administration Utility, staresmonadm, is a Perl script that is a command line interface for calling a Java client application named StaResMonAdm that is contained in the staResMonAdm.jar file. The StaResMonAdm Java program is an RMI client that “talks to” the STA Services daemon to set and reset run-time preferences.

Executable Program Locations

TABLE 3‑1 lists the executable programs and their locations.

Where:

$STAHOME = /Oracle/StorageTek_Tape_Analytics

Backup File Locations

These are the kinds of files involved in the backup operation:

STA Services Daemon and Backup Service Admin Logs

These log the activities of the STA Services Daemon Server, STAServer, and its Backup services configuration utility ServerAdm. Admin logs are collections of up to 10 log files, each up to 1.0 MB in size. The log file names are of the format "*.log.N," where "N" is the number of the log; for example, staservd.log.0, staservadm.log.0, staservd.log.1, and so forth.

The logs are circularly rotated such that log file #1 will be reused when staservd.log.9 has been filled up. The active log file is always #0 (that is, staservd.log.0). When log #0 fills up, it is renamed to log #1 and a new log #0 is started. By default the STAServer and ServerAdm logs are located at:

/var/log/tbi/db/backups

The location of and internal log format type (either simple ASCII text or XML markup) is controlled by the logging properties file staservd.log.props and staservadm.log.props located at:

$STAHOME/common/conf/staservd.log.props
$STAHOME/common/conf/staservadm.log.props

Where:

$STAHOME = /Oracle/StorageTek_Tape_Analytics

MYSQL Database Dump Files

The MySQL database dump file is a snapshot-in-time of the database schema and data contents. STA Backup service performs these actions:

The dump file name format is YYYYCCC.stafulldump.sql, where YYYY is the year and CCC is the calendar day of the year. For example, a dump file generated on July 22, 2011 would have the name "2011203.stafulldump.sql."

The STA Backup Service by default will place its local dump files and incremental binlog files into the directory:

/dbdata/mysql/backups

MySQL Binary Logs

The term incremental dumps refers to the MySQL binary logs (binlogs) that record all transactions that result in a change to a database. The STA Backup Service treats binlogs as incremental backups following the main database dump.

STA incremental dumps are comprised of all the binary logs that are produced since the last full dump. By replaying the binlogs, you can restore a database to its state up the last transaction recorded in the log.

Thus, a restore consists of loading the latest dump file, then replaying, in order, all the MySQL binlogs that were generated following the latest database dump.

Backing up the binlogs, therefore, consists of making a list of all the binlogs created since the most recent full dump and then transmitting each of those logs (except the current one because it is still open) to the backup server.

The backup binary log naming format is YYYYCCC.stadb-bin.NNNNN, where YYYY is the year and CCC is the calendar day of the year, and NNNNN is the MySQL log sequence number. For example, a binlog file generated on July 22, 2011 would have the name "2011203.stadb-bin.000168.gz."

The MySQL binary log location is defined in the MySQL settings file /etc/my.cnf. That is currently set to:

/var/log/tbi/db/

Local copies of the backup binlog files are located at:

/dbdata/mysql/backups

Note – All but the three most recent binlogs that are successfully transferred to the backup server are purged from the server using the MySQL command "PURGE BINLOGS TO 'log_name'".

That will leave the current binlog, the two previous binlogs, and the current day's full backup file remaining on the server.

STA Services Daemon and WebLogic Configuration Files

In addition to files necessary to recover the STA application database, the STA Backup Service also backs up STA's WebLogic configuration files as well as its own STA Services daemon configuration files. The backup is actually a recursive backup of all the files and directories in their respective configuration directories.

Configuration file backups are performed once every 24 hours when the full STA database dump is performed. The backup file names format is YYYYCCC.<dirname>.zip.gz, for example, 2011203.fmconfig.zip.gz.

The source and target locations of these backups are shown in TABLE 3‑2:

Where:

$STAHOME = /Oracle/StorageTek_Tape_Analytics

$WLHOME = /Oracle/Middleware/user_projects/domains/TBI

$BACKUPS = /dbdata/mysql/backups

$RHOST = Backup server IP address or name

$RDIR = Directory on backup server