Skip Navigation Links | |
Exit Print View | |
Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
1. About Sun QFS and Sun Storage Archive Manager
4. Release Package Contents, Directories, and Files
5. Installing Sun QFS and SAM-QFS
6. Installing and Configuring SAM-QFS Manager
7. Configuring the File System Environment
8. Setting Up Mount Parameters and Initializing the File System Environment
9. Backing Up SAM-QFS Data and Files
10. Upgrading Sun QFS and SAM-QFS
11. Uninstalling the SAM-QFS Manager Software
12. Installing Sun QFS and Sun Storage Archive Manager -- Quick Start
This section describes the directories and files that are associated with the Sun QFS and SAM-QFS products. For more information, see the related man pages after the software is installed.
The following directories are created when the software packages are installed:
Device driver special files (only when SAM-QFS packages are installed)
Commands specific to the software
Configuration files
Site-customizable scripts
User command binaries
Files for the remote procedure call API client
Documentation repository for any informational files, such as the README file, that is included in the release
Various example configuration files
API include files
Relocatable libraries
Man pages
Standard MIB files and product MIB, SUN-SAM-MIB.mib
System administrator commands and daemon binaries
Oracle Solaris Cluster binaries and configuration files
SAM-QFS Manager administrator commands
SAM-QFS Manager online documentation repository
Device catalogs, catalog trace file, log files, and archiver data directory and queue files
The following miscellaneous files are created when the software is installed:
Vendor and product identification strings for recognized SCSI devices (only when SAM-QFS packages are installed)
Oracle Solaris system event handler configuration file
File system asynchronous I/O pseudo-driver (64-bit version for x64 platforms)
Oracle Solaris 64-bit file system interface module (for x64 platforms)
SAM-QFS driver for SCSI media changers and optical drives for tape drives (64-bit version for x64 platforms)
Configuration file for samaio
Configuration file for the samioc module
Configuration file for the samst driver
File system asynchronous I/O pseudo-driver (64-bit version for SPARC platforms)
Oracle Solaris 64-bit file system interface module (for SPARC platforms)
SAM-QFS driver for SCSI media changers and optical drives for tape drives (64-bit version for SPARC platforms)
Oracle Solaris 64-bit file system module for the x64 platform
Oracle Solaris 64-bit file system module for SPARC platforms
SAM-QFS Manager configuration file
Faults history file
Software for removing SAM-QFS Manager and its supporting applications
Oracle Solaris Cluster configuration file created only in the presence of Oracle Solaris Cluster software
Oracle Solaris Cluster configuration file created only in the presence of Oracle Solaris Cluster software
The file system has dynamically loadable components that are stored in the Oracle Solaris /kernel directory. Use the modinfo command to determine which modules are loaded. Typically, the kernel loads the file system module at boot time. Alternatively, you can load the file system module when the file system is first mounted after the software is installed.
After the software is installed, it creates files to use for fault notification. When the software detects faults serious enough to merit user attention, the software uses these trap and log files to convey fault information through the SAM-QFS Manager software. The files are as follows:
Sends trap information
Records faults
Records tapealert faults (only when SAM-QFS packages are installed)
Sends tapealert traps (only when SAM-QFS packages are installed)
The software creates these files with 750 permissions.
Caution - Do not change these file permissions. If execute permissions are lost, for example, the system writes messages such as the following to /var/adm/messages: SUNW,SUNWsamfs,sysevent.conf, line1: no execute access to /opt/SUNWsamfs/sbin/tapealert_trap - No such file or directory. |
The configuration procedures in this document direct you to create several site-specific files.
Note - Your site's configuration files must contain ASCII characters only.
You must create the master configuration file, mcf, at your site to use the SAM-QFS software. For more information about the /etc/opt/SUNWsamfs/mcf file, see Chapter 2, About the Master Configuration File, in Sun QFS File System 5.3 Configuration and Administration Guide and mcf(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual.
If you are only using file system features, create only the first two files. If you are using the archiver and file system features, create all of the following files.
File system mount parameter command file (see samfs.cmd(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual)
Miscellaneous default values (see defaults.conf(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual)
Archiver command file (see Chapter 10, Configuring the Archiver, in Sun Storage Archive Manager 5.3 Configuration and Administration Guideand archiver.cmd(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual)
Previewer command file (see Chapter 15, Configuring the Stager, in Sun Storage Archive Manager 5.3 Configuration and Administration Guide and preview.cmd(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual)
Recycler command file (see Chapter 16, Configuring the Recycler, in Sun Storage Archive Manager 5.3 Configuration and Administration Guide and recycler.cmd(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual)
Releaser command file (see Chapter 14, About Releasing, in Sun Storage Archive Manager 5.3 Configuration and Administration Guide and releaser.cmd(4) in Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual.
During installation, the software adds information to certain Oracle Solaris system files. The Oracle Solaris OS uses these ASCII text files to identify loadable kernel modules by number rather than by name.
/etc/name_to_major
The SAM-QFS software uses this file to map drivers to major numbers. The samst and samrd major numbers can vary depending on the major numbers that are already in use by the Oracle Solaris OS. The system adds the following lines to this file:
samst 63 samrd 64 samioc 236 samaio 237
/etc/security/auth_attr
This file is the authorization description database. The system adds the following lines to this file:
# File System Manager Authorizations com.sun.netstorage.fsmgr.config:::File System Manager All Access:: com.sun.netstorage.fsmgr.operator.media:::File System Manager Media Related Operation Access:: com.sun.netstorage.fsmgr.operator.sam.control:::File System Manager Start/Stop/Idle Archiving Access:: com.sun.netstorage.fsmgr.operator.file:::File System Manager File LevelOperation Access:: com.sun.netstorage.fsmgr.operator.filesystem:::File System Manager FileSystem Level Operation Access::
/etc/user_attr
This file is the extended user attributes database used by SAM-QFS Manager.
root::::profiles=Web Console Management,All;auths= Solaris.*,solaris.grant,*com.sun.netstorage.fsmgr.**; lock_after_retries=no