Sun StorageTek™ Storage Archive Manager (SAM) Archive Configuration and Administration Guide Version 4, Update 6 Sun Microsystems, Inc. www.sun.com Part No. 819-7931-10 April 2007, Revision A Submit comments about this document at: http://www.sun.
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Contents Preface 1. xix Overview Capabilities 1 1 Storage Devices 3 Sun SAM-Remote Software 4 High-Availability Configuration Using Sun Cluster (HA-SAM) File System Manager ▼ 5 To Invoke the File System Manager Setting the Session Timeout 5 6 Creating Additional Administrator and User Accounts ▼ To Create Additional Accounts Assigning Privilege Levels 6 6 7 Creating an Account for Multiple Users 8 Managing Additional Servers From the File System Manager 2.
▼ To Turn On an Automated Library 13 ▼ To Turn Off an Automated Library 14 Loading a Cartridge Into an Automated Library ▼ To Manually Load a Cartridge Unloading a Cartridge From a Drive ▼ 15 15 To Manually Unload a Cartridge Labeling a Cartridge 14 16 16 ▼ To Label or Relabel a Tape ▼ To Label or Relabel an Optical Disk 16 17 ▼ To Audit a Volume ▼ To Audit a Direct Attached Automated Library 17 Using a Cleaning Cartridge 18 19 ▼ To Use a Cleaning Cartridge With a Barcode ▼ To
Using Drives With Encryption Capability Manually Loaded Drive Operations 3.
The drives Directive: Controlling the Number of Drives Used for Archiving 54 The examine Directive: Controlling Archive Scans 55 The interval Directive: Specifying an Archive Interval 55 The logfile Directive: Specifying An Archiver Log File 56 ▼ To Back Up an Archiver Log File 57 The notify Directive: Renaming the Event Notification Script The ovflmin Directive: Controlling Volume Overflow 57 57 The scanlist_squash Directive: Controlling Scanlist Consolidation 59 The setarchdone Directive: Cont
Unarchiving Automatically 72 Specifying More Than One Copy for Metadata Archive Set Copy Parameters 72 73 Controlling the Size of Archive Files: -archmax Setting the Archiver Buffer Size: -bufsize 74 74 Specifying the Number of Drives for an Archive Request: -drivemax, -drivemin, and -drives 75 Maximizing Space on a Volume: -fillvsns Specifying Archive Buffer Locks: -lock 77 77 Making Archive Copies of Offline Files: -offline_copy Specifying Recycling 78 78 Associative Archiving: -join path Co
The Preview Queue Archiver Examples 100 101 Example 1: No archiver.cmd File 4. 101 Example 2: Data Files Archived Separately From Metadata 103 Example 3: User and Data Files Archived to Various Media 106 Example 4: User and Data Files Archived to Optical Media 110 Releasing 115 Releaser Process Overview Releaser Concepts 115 116 About Partial Releasing and Partial Staging System Administrator Option Summary User Option Summary 118 120 121 About the releaser.
5. Staging 133 About the stager.cmd File 133 The drives Directive: Specifying the Number of Drives Setting the Stage Buffer Size Specifying a Log File 134 135 136 Specifying the Number of Stage Requests Example stager.
Example recycler.cmd File ▼ To Run the Recycler 156 158 Creating a crontab File for the Recycler ▼ To Remove -recycle_ignore and ignore Parameters Creating a recycler.sh File Recycling Disk Archive Volumes To Run the Recycler 160 161 162 Creating a crontab File for the Recycler ▼ 162 To Remove -recycle_ignore and ignore Parameters Recycling for Archive Copy Retention 7. Using the Sun SAM-Remote Software Sun SAM-Remote Software Overview Features 159 160 Editing the archiver.
▼ To Edit the mcf Files ▼ To Define a Sun SAM-Remote Client ▼ To Define a Sun SAM-Remote Server in the Server’s mcf File ▼ To Create the Sun SAM-Remote Server Configuration File ▼ To Enable Archiving 173 176 176 177 180 Recycling With the Sun SAM-Remote Software 184 Recycling in a Sun SAM-Remote Environment—Method 1 185 Configuration Files for Server sky 186 Configuration Files for Client zeke 187 ▼ To Configure Recycling—Method 1 188 ▼ To Recycle no-data VSNs ▼ To Recycle partially
▼ To Enable the Device Log by Editing the defaults.
Sony Direct Attached 8400 PetaSite Automated Libraries ▼ To Import Tapes Exporting Tapes ▼ 236 236 ▼ To Export a Tape Without Using the Mailbox Slots As Storage Slots 236 ▼ To Export a Tape Using Mailbox Slots As Storage Slots To Move a Cartridge to a Different Slot Sony Network Attached Automated Libraries ▼ To Import a Cartridge 239 ▼ To Export a Cartridge 240 ▼ To Import Tapes ▼ To Export Tapes Using a Mailbox Glossary 237 238 239 StorageTek ACSLS-Attached Automated Libraries Ind
xiv Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
Tables TABLE 1-1 Automated Library Daemons 3 TABLE 1-2 File System Manager Permission Levels TABLE 2-1 Arguments for samcmd(1M) load TABLE 2-2 Arguments for tplabel(1M) 16 TABLE 2-3 Arguments for odlabel(1M) 17 TABLE 2-4 Arguments for auditslot(1M) TABLE 2-5 Arguments for chmed(1M) 21 TABLE 2-6 Arguments for chmed(1M) 23 TABLE 2-7 Arguments for auditslot(1M) TABLE 2-8 Arguments for chmed(1M) TABLE 2-9 Arguments for samexport(1M) TABLE 3-1 Archiver Log File Fields TABLE 3-2 arc
TABLE 3-10 -minsize and -maxsize size Suffixes 64 TABLE 3-11 The -release Directive Attributes TABLE 3-12 The -stage Directive’s Attributes TABLE 3-13 Arguments for the Archive Set Copy Parameters TABLE 3-14 Arguments for the -drivemax, -drivemin, and -drives Directives 75 TABLE 3-15 Archive Set Example Split TABLE 3-16 Values for the -offline_copy Directive’s method Argument TABLE 3-17 Archive Set Form Examples TABLE 3-18 Owner Set Form Examples TABLE 3-19 File System Form Examples TABL
TABLE A-1 Arguments for the import(1M) Command 230 TABLE A-2 Arguments for the samexport(1M) Command TABLE A-3 Arguments for the import(1M) Command TABLE A-4 Arguments for the samexport(1M) Command TABLE A-5 Arguments for the move(1M) Command 237 231 232 TABLE A-6 Arguments for the move(1M) Command TABLE A-7 Arguments for the import(1M) Command TABLE A-8 Arguments for the samexport(1M) Command TABLE A-9 Arguments for the import(1M) Command TABLE A-10 Arguments for the samexport(1M) Com
xviii Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
Preface This manual, the Sun StorageTek™ Storage Archive Manager Archive Configuration and Administration Guide, describes the storage and archive management software supported in the Sun StorageTek Storage Archive Manager (SAM) Version 4, Update 6 (4U6) release. The Sun StorageTek SAM software automatically copies files from online disk to archive media. The archive media can consist of either online disk or removable media cartridges.
How This Book Is Organized This manual contains the following chapters: ■ Chapter 1 provides overview information. ■ Chapter 2 explains basic operations. The information in this chapter applies to most automated libraries and manually loaded devices. ■ Chapter 3 explains the archiving process. ■ Chapter 4 explains the releasing process. ■ Chapter 5 explains the staging process. ■ Chapter 6 explains the recycling process. ■ Chapter 7 describes how to use the Sun SAM-Remote software.
Shell Prompts TABLE P-1 shows the shell prompts that this manual uses. TABLE P-1 Shell Prompts Shell Prompt C shell machine-name% C shell superuser machine-name# Bourne shell and Korn shell $ Bourne shell and Korn shell superuser # Typographic Conventions TABLE P-2 lists the typographic conventions used in this manual. TABLE P-2 Typeface or Symbol Typographic Conventions Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output. Edit your .
TABLE P-2 Typeface or Symbol Typographic Conventions (Continued) Meaning Examples [] In syntax, brackets indicate that an argument is optional. scmadm [–d sec] [–r n[:n][,n]...] [–z] { arg | arg } In syntax, braces and pipes indicate that one of the arguments must be specified. sndradm -b { phost | shost } \ At the end of a command line, the backslash (\) indicates that the command continues on the next line.
Accessing Sun Documentation Online The Sun StorageTek QFS and Sun StorageTek SAM software distribution includes PDF files that you can view from Sun’s Network Storage documentation web site or from docs.sun.com. To Access Documentation From docs.sun.com This web site contains documentation for Solaris and many other Sun software products. 1. Go to the following URL: http://docs.sun.com The docs.sun.com page appears. 2.
or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources. Contacting Sun Technical Support If you have technical questions about this product that are not answered in this document, go to the following web site: http://www.sun.
CHAPTER 1 Overview The Sun StorageTek SAM environment provides a configurable file system with storage, archive management, and retrieval capabilities. The Sun StorageTek SAM software archives files by copying the files from online disk cache to archive media. The archive media can consist of disk slices in another file system or it can consist of removable tape or magneto-optical cartridges in automated or manually loaded storage devices.
files in a Sun StorageTek SAM file system and writes the archive copy to archive media. You can configure the archiver to create up to four archive copies on a variety of archive media. If a file is segmented, each segment is treated as a file and is archived separately. The archiving process is initiated after disk-based files match a site-definable set of selection criteria. For more information about the archiver, see “Archiving” on page 33.
■ Relabel the volume for immediate reuse. ■ Export the volume to offsite storage as a historical record of file changes. You can use standard UNIX utilities to restore previous versions of files from expired archive copies. The recycling process is transparent to end users. For more information about recycling, see “Recycling” on page 149. Storage Devices The Sun StorageTek SAM environment supports a wide variety of tape storage and magneto-optical devices.
For a list of supported storage devices, contact your Sun Microsystems sales representative or your authorized service provider (ASP). The relationships between the devices managed within the Sun StorageTek SAM environment are defined in the master configuration file, /etc/opt/SUNWsamfs/mcf. The mcf file specifies the removable media devices, libraries, and file systems included in the Sun StorageTek SAM environment. Each piece of equipment is assigned a unique equipment identifier in the mcf file.
High-availability SAM (HA-SAM) depends on the Sun StorageTek QFS Sun Cluster agent, so this configuration must be installed with a shared Sun StorageTek QFS file system that is mounted and managed by the Sun StorageTek QFS Sun Cluster agent. For more information see “Configuring a SAM-QFS File System in a Sun Cluster Environment (HA-SAM)” on page 211.
4. At the Password prompt, enter the password. 5. Click Log In. 6. Click File System Manager. You are now logged in to File System Manager. Setting the Session Timeout The Java Web Console framework has a default session timeout of 15 minutes. The File System Manager installation program changes the session timeout to 60 minutes. You can change the session timeout to a different value, but it is recommended that you not set it to a value greater than 60 minutes in order to preserve security.
2. Use the useradd and passwd commands to add each user. For example, to add a user with account name bobsmith, type the following: # /usr/sbin/useradd bobsmith # /usr/bin/passwd bobsmith Each user account that you add in this way has read-only viewing privileges for File System Manager functions. To add additional privileges see the following section, “Assigning Privilege Levels” on page 7. Assigning Privilege Levels You can assign users full or partial access to File System Manager functions.
To assign bobsmith privileges only for staging and restoring file systems (privilege level com.sun.netstorage.fsmgr.operator.file) and exporting, importing, and assigning VSNs (privilege level com.sun.netstorage.operator.media), add the following line to the /etc/user_attr file: bobsmith::::auths=com.sun.netstorage.fsmgr.operator.file, com.sun.netstorage.fsmgr.operator.
Managing Additional Servers From the File System Manager By default, File System Manager is set up to manage the server on which it is installed. It can also be used to manage other servers running Sun StorageTek QFS or Sun StorageTek SAM software, but those additional servers must first be configured to enable File System Manager access. Once these servers are configured, you can administer their file systems, archiving processes, and media through the browser interface. To add a server: 1.
10 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
CHAPTER 2 Using Automated Libraries and Manually Loaded Drives An automated library is a robotically controlled device designed to load and unload removable cartridges without operator intervention. Automated libraries are also known as media changers, jukeboxes, robots, libraries, or media libraries. This chapter describes aspects of using automated libraries and manually loaded drives in a Sun StorageTek SAM environment.
Automated Library Operations A number of basic operations are essentially the same for all automated libraries.
If removable media operations are already running when the preceding command is entered, the following message is generated: SAM-FS sam-amld daemon already running For more information about the samd(1M) command, see the samd(1M) man page. ▼ To Stop Removable Media Operations It is possible to stop removable media operations and leave the Sun StorageTek SAM system mounted. You might do this, for example, if you want to manually manipulate cartridges in a library.
● Use the samcmd(1M) on command. samcmd on eq For eq, specify the equipment ordinal of the automated library as defined in the mcf file. You can also perform this task by using samu(1M) or File System Manager. ▼ To Turn Off an Automated Library Placing a library in the off state stops I/O operations and removes the automated library from Sun StorageTek SAM control. No automatic movement of cartridges occurs, and the drives in the automated library remain in the on state.
▼ To Manually Load a Cartridge ● Use the samcmd(1M) load command. You can use this command even if the drive is in unavail status. This command has the following two possible formats: samcmd load eq:slot[:partition] samcmd load media-type.vsn TABLE 2-1 Arguments for samcmd(1M) load Argument Meaning eq The equipment ordinal of the drive as defined in the mcf file. slot The number of a storage slot as recognized in the library catalog. media-type The media type.
▼ To Manually Unload a Cartridge ● Use the samcmd(1M) unload command. This command can be used even if the drive is in unavail status. Use this command: samcmd unload eq For eq, specify the equipment ordinal of the drive as defined in the mcf file. You can also perform this task by using samu(1M) or File System Manager. Labeling a Cartridge The procedure for labeling a cartridge depends on whether you are labeling a tape or optical disk. The following two sections describe these procedures.
After the command to label or relabel a tape is issued, the tape is loaded and positioned, and the tape label is written. For more information about the tplabel(1M) command, see the tplabel(1M) man page. You can also perform this task by using File System Manager. ▼ To Label or Relabel an Optical Disk ● To label a new optical disk, use the odlabel(1M) command. odlabel –new –vsn vsn eq:slot:partition ● To relabel an existing optical disk, use the odlabel(1M) command.
● Use the auditslot(1M) command to audit a volume. auditslot [–e] eq:slot[:partition] TABLE 2-4 Arguments for auditslot(1M) Argument Meaning -e If the –e option is specified and the media is tape, the remaining space is updated. Otherwise, it is not changed. eq The equipment ordinal of the drive as defined in the mcf file. slot The number of the storage slot as recognized in the library catalog. This argument is not applicable to manually loaded drives.
For eq, specify the equipment ordinal of the automated library as defined in the mcf file. You can also perform this task by using the samu(1M) utility’s :audit command or by using File System Manager. Using a Cleaning Cartridge The Sun StorageTek SAM environment supports the use of cleaning tapes if cleaning tapes are supported by the hardware. If a tape drive requests cleaning, the system automatically loads a cleaning tape.
The Sun StorageTek SAM system moves the cartridge from the mailbox to a storage slot and updates the library catalog. In addition, after this command is issued, the cleaning media flag is set, and the access count is set to the appropriate number of cleaning cycles, based on the media type. Each time the cartridge is used to clean a drive, the access count is decremented. ▼ To Use a Cleaning Cartridge Without a Barcode If the cartridge is not barcoded, you must import it first.
For more information about the chmed(1M) command, see the chmed(1M) man page. ▼ To Reset the Number of Cleaning Cycles Cleaning tapes are useful only for a limited number of cleaning cycles. You can view the number of remaining cycles with the samu(1M) utility’s :v display or by using File System Manager. The Sun StorageTek SAM system tracks the number of cleaning cycles used for each cleaning tape and ejects the tape when the number of remaining cycles equals zero.
For example, the following command sets the cleaning cycle count to 20 for the cleaning cartridge in slot 77 of the automated library with the equipment ordinal of 50. # chmed -count 20 50:77 ▼ To Clean a Tape Drive When automatic cleaning is not available and the system uses barcodes, perform the following procedure to request manually that a drive be cleaned: ● Use the cleandrive(1M) command. cleandrive eq For eq, specify the equipment ordinal of the automated library as defined in the mcf file.
To invoke the legacy Sun StorageTek SAM auto-cleaning feature, which relies on sense data only for drive cleaning status, insert the following line in the defaults.conf file: tapeclean = all autoclean on logsense off Note – When using the auto-cleaning feature with a library with more than two drives, it is recommended that you have at least two cleaning cartridges per Sun StorageTek SAM catalog.
TABLE 2-7 Arguments for auditslot(1M) Argument Meaning -e If the –e option is specified and the media is tape, the remaining space is updated. Otherwise, it is not changed. eq The equipment ordinal of the automated library or manually loaded drive as defined in the mcf file. slot The number of the storage slot in the automated library as recognized in the library catalog. This argument is not applicable to manually loaded drives. partition A side of a magneto-optical disk.
4. Use the samcmd(1M) on command to turn on the automated library and the drive. Issue this command once for the drive and once for the library. samcmd on eq For eq, specify the equipment ordinal of the library or drive as defined in the mcf file. If the automated library performs an audit when it is turned on, you are done. 5. Follow these steps if the automated library does not perform an audit when it is turned on: a. Put the cartridge back into its storage slot. b.
■ Relocate cartridges to off-site storage to use later for disaster recovery purposes. You can use the -I option on the chmed(1M) command to specify additional information such as the storage location of the cartridge. When you import and export cartridges, you also update the library catalog. The library catalog is the central repository of all information that the Sun StorageTek SAM environment needs for finding cartridges in an automated library.
Tracking Exported Media – The Historian The Sun StorageTek SAM historian keeps track of cartridges exported from an automated library or a manually mounted device. The historian acts like a virtual library, but it has no defined hardware devices. Like an automated library, it is configured in the mcf file, has a catalog that records entries for all cartridges associated with it, can import and export cartridges, and appears in File System Manager as another automated library.
Importing and exporting practices differ from manufacturer to manufacturer. See “Basic Operations for Libraries With Vendor-Specific Operational Procedures” on page 229 to determine if specialized procedures are recommended for your equipment.
TABLE 2-9 Arguments for samexport(1M) Argument Meaning eq The equipment ordinal of the automated library as defined in the mcf file. slot The number of the storage slot in the automated library as recognized in the library catalog. media-type The media type of the cartridge. For a list of valid media types, see the mcf(4) man page. vsn The volume serial name (VSN) assigned to the volume. You can also perform this step by using samu(1M) or File System Manager. 2.
2. Wait until the system completes its current task, sets the status to off, and transfers the current active catalog to the historian. 3. Unlock and open the door to the automated library. 4. Remove the cartridges from their respective slots. 5. Close and lock the door to the automated library. The automated library reinitializes and scans the cartridges in the automated library. The system updates the library catalog with the VSNs of the cartridges currently in library slots.
Using Drives With Encryption Capability If you are archiving files to drives with encryption capability, there are some special considerations: ■ You should not mix non-encrypted and encryption-capable drives in a library. ■ Once a drive has encryption enabled, it cannot be disabled. ■ You cannot mix encrypted and non-encrypted files on a tape. ■ An encrypted drive cannot append to a tape that contains non-encrypted data. ■ An encryption-enabled drive can, however, read non-encrypted data.
▼ To Unload a Cartridge ● Use samcmd(1M) idle command to idle the drive. samcmd idle eq For eq, specify the equipment ordinal of the drive as defined in the mcf file. This command ensures that no archive or stage processes are active. The drive switches from idle to off when all I/O activity is complete, and the tape ejects. If the cartridge is a tape, the tape rewinds and is ready to be removed. An optical disk ejects automatically.
CHAPTER 3 Archiving Archiving is the process of copying a file from a Sun StorageTek SAM file system to a volume that resides on a removable media cartridge or on a disk partition of another file system. Using Sun StorageTek SAM archiving capabilities, you can specify that files be archived immediately, specify that files never be archived, and perform other tasks.
The archiver starts automatically when a Sun StorageTek SAM file system is mounted. You can customize the archiver’s operations for your site by inserting archiving directives into the following file: /etc/opt/SUNWsamfs/archiver.cmd The archiver.cmd file does not need to be present for archiving to occur. In the absence of this file, the archiver uses the following defaults: ■ All files are archived to available volumes. ■ The archive age for all files is 4 minutes.
As files are created and modified, the archiver copies them to archive media. The archiving process also copies the data necessary for Sun StorageTek SAM file system operations, including directories, symbolic links, the index of segmented files, and archive media information. Archive files are compatible with the standard UNIX tar(1) format. This ensures data compatibility with the Solaris OS and other UNIX systems.
Note – Issuing an mv(1) command alters the file name but not the file data, and this can have ramifications in a disaster recovery situation if you are restoring from tar(1) files. For more information on disaster recovery, see the Sun StorageTek Storage Archive Manager Troubleshooting Guide. A file is selected for archiving based on its archive age, which is the period of time that has past since the file was last modified. The archive age can be defined for each archive copy.
The sam-arfind process determines the archive set to which the file belongs by using the file properties descriptions.
Continuous Archiving Continuous archiving is the default archiving method (the archiver.cmd file parameter is examine=noscan). With continuous archiving, you can specify scheduling start conditions for an archive set by using the -startage, -startcount, and -startsize parameters. These conditions enable you to optimize archive timeliness versus archive work done.
When the file system scan is complete, the sam-arfind process sends each archive request to the archiver daemon, sam-archiverd, to be scheduled for file copying to archive media. The sam-arfind process then sleeps for the duration specified by the interval=time directive. At the end of the interval, the sam-arfind process resumes scanning. Step 2: Composing Archive Requests When archive requests are received by the sam-archiverd daemon, they are composed. This section describes the composing process.
The sam-archiverd daemon determines whether the files are online or offline. If both online and offline files are in the archive request, the online files are selected for archiving first. If the archive request was not required to be joined or sorted by a sort method, the offline files are ordered by the volume on which the archive copies reside. This ensures that all files in each archive set on the same volume are staged at the same time in the order in which they were stored on the media.
Drives If the archive set has the -drives parameter specified, the sam-archiverd daemon divides the selected files in the archive request among multiple drives. If the number of drives available at this time is fewer than that specified by the -drives parameter, the smaller number is used. If the total size of files in the archive request is less than the -drivemin value, only one drive is used. The -drivemin value is either the value specified by the -drivemin parameter or the archmax value.
threshold above which additional volumes or media are assigned for archiving. An ovflmin value specified for the archive set takes precedence over an ovflmin value specified for the media. If the size of the files is less than the value of ovflmin, the files cannot be archived. An appropriate message for this condition is sent to the log. If the size of the files is more than the value of ovflmin, additional volumes are assigned as required.
When the sam-arcopy process exits, the sam-archiverd daemon examines the archive request. If any files have not been archived, the archive request is recomposed. You can also specify timeouts for archiving operations in the archiver.cmd file. The directive is as follows: timeout = [operation | media] time operation may be one of the following: ■ read: Reading the file from the disk. The default timeout is 1 minute. ■ request: Requesting the archive media. The default timeout is 15 minutes.
Sample Default Output CODE EXAMPLE 3-1 shows sample output from the archiver(1M) -l command. CODE EXAMPLE 3-1 Output From the archiver(1M) -l Command # archiver Archive media: default:mo media:mo archmax:5000000 media:lt archmax:50000000 Archive devices: device:mo20 drives_available:1 archive_drives:1 device:lt30 drives_available:1 archive_drives:1 Archive file selections: Filesystem samfs1: samfs1 Metadata copy:1 arch_age:240 big path:.
CODE EXAMPLE 3-2 shows sample lines from an archiver log file with definitions for each field. CODE EXAMPLE 3-2 Archiver Log File Lines A 2001/03/23 18:42:06 mo 0004A arset0.1 9a089.1329 samfs1 118.51 162514 t0/fdn f 0 56 A 2001/03/23 18:42:10 mo 0004A arset0.1 9aac2.1 samfs1 189.53 1515016 t0/fae f 0 56 A 2001/03/23 18:42:10 mo 0004A arset0.1 9aac2.b92 samfs1 125.53 867101 t0/fai f 0 56 A 2001/03/23 19:13:09 lt SLOT22 arset0.2 798.1 samfs1 71531.
Archiver Log File Fields (Continued) TABLE 3-1 Field Example Value Content 8 samfs1 File system name. 9 118.51 Inode number and generation number. The generation number is used in addition to the inode number for uniqueness since inode numbers are reused. 10 162514 Length of the file if the file is written on only one volume. Length of the section if the file is written on multiple volumes. 11 t0/fdn Path and name of the file relative to the file system’s mount point.
Note – The data verification feature places an additional burden on stager resources since data verification requests are placed on the stager queue along with the normal stage requests. Data verification also leads to additional tape mounts and may therefore affect archiver and stager performance. Since a file cannot be released until all archive copies are made, using data verification may also require additional disk cache. About the archiver.cmd File The archiver.
3. Save and close the file. 4. Use the archiver(1M) -lv command to verify the correctness of the file. Whenever you make changes to the archiver.cmd file, you should check for syntax errors using the archiver(1M) command. Specifying the archiver(1M) command as follows evaluates an archiver.cmd file against the current Sun StorageTek SAM system: # archiver –lv This command produces a list of all options and writes a list of the archiver.
The directives consist of lines of text read from the archiver.cmd file. Each directive line contains one or more fields separated by spaces or tabs. Any text that appears after the pound sign character (#) is treated as a comment and is not examined. You can continue long directives to a second line by ending the first line with a backslash (\). Certain directives in the archiver.cmd file require you to specify a unit of time or a unit in bytes. To specify such a unit, use one of the letters in TABLE 3-2.
Example archiver.cmd File CODE EXAMPLE 3-3 shows a sample archiver.cmd file. The comments indicate the various types of directives. CODE EXAMPLE 3-3 Example archiver.cmd File # Global directives archivemeta = off archmax = li 8G examine = noscan scanlist_squash = on # limit the drives drives = stk50 X # File selection fs = samfs1 logfile = /var/adm/samfs1.log archive . 1 -norelease 5m 2 -norelease 5m fs = samfs2 logfile = /var/adm/samfs2.log archive .
Example archiver.cmd File (Continued) CODE EXAMPLE 3-3 # The below information is for tape archiving. # The recycler is not set up to actually recycle. # data checks and file recovery. It is set up for params allsets -sort path -offline_copy stageahead -reserve set allsets -recycle_ignore allsets -recycle_hwm 50 -recycle_mingain 90 -recycle_vsncount 1 allsets.1 -startage 6h -startsize 8G -startcount 90000 -drives X -drivemin XXG allsets.
Global Archiving Directives Global directives control the overall archiver operation and enable you to optimize archiver operations for your site’s configuration. You can add global directives directly to the archiver.cmd file, or you can specify them using the File System Manager software. For more information on using File System Manager to set global directives, see the File System Manager online help. Global directives in the archiver.
The archmax Directive: Controlling the Size of Archive Files The archmax directive specifies the maximum size of an archive file. User files are combined to form the archive file. No more user files are added to the archive file after the target-size value is met. Large user files are written in a single archive file. To change the defaults, use the following directive: archmax=media target-size TABLE 3-3 Arguments for the archmax Directive Argument Meaning media The media type.
TABLE 3-4 Arguments for the bufsize Directive Argument Meaning media The media type. For the list of valid media types, see the mcf(4) man page. buffer-size A number from 2 through 1024. The default is 4. This value is multiplied by the dev_blksize value for the media type, and the resulting buffer size is used. The dev_blksize value is specified in the defaults.conf file. For more information on this file, see the defaults.conf(4) man page.
Also see the -drivemax, -drivemin, and -drives archive set copy parameters described in “Specifying the Number of Drives for an Archive Request: -drivemax, -drivemin, and -drives” on page 75. The examine Directive: Controlling Archive Scans New files and files that have changed are candidates for archiving.
The interval directive initiates full scans only when continuous archiving is not set and no startage, startsize, or startcount parameters have been specified. If continuous archiving is set (examine=noscan), the interval directive acts as the default startage value. This directive has the following format: interval=time For time, specify the amount of time you want between scan operations on a file system. By default, time is interpreted in seconds and has a value of 600, which is 10 minutes.
▼ To Back Up an Archiver Log File Assume that you want to back up the archiver log file every day by copying the previous day’s log file to an alternate location. Be sure to perform the copy operation when the archiver log file is closed, not while it is open for a write operation. 1. Use the mv(1) command to move the archiver log file within a UNIX file system. This gives any sam-arfind(1M) or sam-arcopy(1M) operations time to finish writing to the archiver log file. 2.
Note – Use volume overflow with caution only after thoroughly assessing its effect on your site. Disaster recovery and recycling are much more difficult with files that span volumes. For more information, see the Sun StorageTek Storage Archive Manager Troubleshooting Guide and the request(1) man page. The archiver controls volume overflow through the ovflmin directive. The ovflmin directive specifies the file size threshold that triggers the overflow process. By default, volume overflow is disabled.
CODE EXAMPLE 3-4 Archiver Log File Example A 97/01/13 16:03:29 lt DLT000 477609472 00 big/file50 0 0 A 97/01/13 16:03:29 lt DLT001 516407296 01 big/file50 0 1 A 97/01/13 16:03:29 lt DLT005 505983404 02 big/file50 0 2 big.1 7eed4.1 samfs1 13.7 big.1 7fb80.0 samfs1 13.7 big.1 7eb05.0 samfs1 13.7 CODE EXAMPLE 3-4 shows that file50 spans three volumes with VSNs of DLT000, DLT001, and DLT005.
performance penalty if archiving on a file system that has a large number of changes to many subdirectories. When the scanlist is consolidated, these directories are combined upwards to a common parent, which results in a deep recursive scan over many subdirectories. The setarchdone Directive: Controlling the Setting of the archdone Flag The setarchdone parameter is a global directive that controls the setting of the archdone flag when the file is examined by sam-arfind.
File System Directives After the general directives in the archiver.cmd file, you can use the fs= directive to include directives specific to a particular file system. After an fs= directive is encountered, the archiver assumes that all subsequent directives specify that actions be taken only for the specified file systems. You can specify fs= directives by editing the archiver.cmd file, as described in the following sections, or by using the File System Manager software.
Archive Set Assignment Directive By default, files are archived as part of the archive set named for the file system. However, you can specify archive sets to include files that share similar characteristics. If a file does not match one of the specified archive sets, it is archived as part of the default archive set named for the file system. You can create archive sets by directly editing the archiver.cmd file, as described in the following sections, or by using the File System Manager software.
TABLE 3-8 Arguments for the Archive Set Assignment Directives (Continued) Argument Meaning file-attribute1 file-attribute2 Zero, one, or more file-attribute values can be specified. These file attributes are set for files as the sam-arfind process scans a file system during archiving. CODE EXAMPLE 3-6 shows typical archive set membership directives. CODE EXAMPLE 3-6 hmk_files datafiles system Archive Set Membership Directives net/home/hmk xray_group/data .
TABLE 3-9 -access age Suffixes (Continued) Suffix Meaning d Days w Weeks ]y Years For example, you can use this directive to specify that files that have not been accessed in a long time be rearchived to less expensive media. When determining age, the software validates the access and modification times for files to ensure that these times are greater than or equal to the file creation time, and less than or equal to the time at which the file is examined.
TABLE 3-10 -minsize and -maxsize size Suffixes (Continued) Letter Meaning T Terabytes P Petabytes E Exabytes Example. The lines in CODE EXAMPLE 3-8 specify that all files of at least 500 kilobytes, but less than 100 megabytes, belong to the archive set big_files. Files bigger than 100 megabytes belong to the archive set huge_files. CODE EXAMPLE 3-8 big_files . huge_files .
All files beneath the selected directory (with their specified paths relative to the mount point of the file system) go through pattern matching. This allows you to create patterns in the -name regex field to match both file names and path names. Examples The following directive restricts files in the archive set images to those files ending with .gif: images . -name \.gif$ The following directive selects files that start with the characters GEO: satellite .
CODE EXAMPLE 3-12 shows the files that are archived if you specify the directives shown in CODE EXAMPLE 3-10. CODE EXAMPLE 3-12 Files Archived (Using Directives Shown in CODE EXAMPLE 3-10) /sam1/fred.anything /sam1/share/fred.anything /sam1/testdir/fred.anything /sam1/testdir/share/fred.anything /sam1/testdir/share/marketing/fred.anything /sam1/testdir/share/marketing/second_user/fred.anything In contrast to CODE EXAMPLE 3-10, assume that your archiver.
Release and Stage file-attributes: -release and -stage You can set the release and stage attributes associated with files within an archive set by using the -release and -stage options, respectively. Both of these settings override stage or release attributes that a user might have set previously. The -release option has the following format: -release attribute The attributes for the -release directive follow the same conventions as the release(1) command and are shown in TABLE 3-11.
Archive Set Membership Conflicts Sometimes the choice of path and other file characteristics for inclusion of a file in an archive set results in ambiguous archive set membership. These situations are resolved in the following manner: 1. The membership definition occurring first in the archive set is chosen. 2. Membership definitions local to a file system are chosen before any globally defined definitions. 3. A membership definition that exactly duplicates a previous definition is noted as an error.
Archive Copy Directives If you do not specify archive copies, the archiver writes a single archive copy for files in the archive set. By default, this copy is made when the archive age of the file is four minutes. If you require more than one archive copy, all copies, including the first, must be specified through archive copy directives. The archive copy directives begin with a copy-number value of 1, 2, 3, or 4.
Delaying Disk Space Release: -norelease You might not want to release disk space until multiple archive copies are completed. The -norelease option prevents the automatic release of disk cache until all copies marked with -norelease are made. This directive has the following format: -norelease The -norelease directive makes the archive set eligible to be released after all copies have been archived, but the files will not be released until the releaser is invoked and selects them as release candidates.
In CODE EXAMPLE 3-19, the files in directory data are archived when their archive age reaches one hour. CODE EXAMPLE 3-19 An archiver.cmd File That Specifies the Archive Age ex_set data 1 1h Unarchiving Automatically If you specify more than one archive copy of a file, it is possible to unarchive all but one of the copies automatically. You might want to do this when the files are archived to various media using various archive ages. CODE EXAMPLE 3-20 shows the directive that specifies the unarchive age.
File system metadata includes path names in the file system. For this reason, if you have frequent changes to directories, the new path names cause the creation of new archive copies. This results in frequent loads of the volumes specified for metadata. Archive Set Copy Parameters The archive set parameters section of the archiver.cmd file begins with the params directive and ends with the endparams directive. CODE EXAMPLE 3-22 shows the format for directives for an archive set.
The pseudo archive set allsets provides a way to set default archive set directives for all archive sets. All allsets directives must precede directives for actual archive set copies. Parameters set for individual archive set copies override parameters set by the allsets directive. For more information on the allsets archive set, see the archiver.cmd(4) man page. The following subsections describe all archive set processing parameters, with the exception of disk archiving parameters.
The equivalent of this directive on a global basis is bufsize=media buffer-size. For more information on that directive, see “The bufsize Directive: Setting the Archiver Buffer Size” on page 53. Specifying the Number of Drives for an Archive Request: -drivemax, -drivemin, and -drives By default, the archiver uses only one media drive to archive the files of one archive set. When an archive set has many files or large files, it can be advantageous to use more than one drive.
When you use the –drives parameter, multiple drives are used only if data that is more than the value of min-size is to be archived.
Maximizing Space on a Volume: -fillvsns By default, the archiver selects from all volumes assigned to an archive set when it writes archive copies, using a volume with enough space for all the files. This action can result in volumes not being filled to capacity. If -fillvsns is specified, the archiver separates the archive request into smaller groups. Specifying Archive Buffer Locks: -lock By default, a file being archived is stored in memory in a buffer before being written to archive media.
Making Archive Copies of Offline Files: -offline_copy A file is a candidate for being released after one archive copy is made. If the file releases and goes offline before all the archive copies are made, the archiver uses this parameter to determine the method to be used when making the other archive copies. In choosing the method to be used, consider the number of drives available to the Sun StorageTek SAM system and the amount of disk cache available.
Associative Archiving: -join path The archiver employs associative archiving if you specify the -join path parameter. Associative archiving is useful if you want an entire directory to be archived to one volume and you know that the archive file can physically reside on only one volume. Otherwise, if you want to keep directories together, use either the –sort path or -rsort path parameters to keep the files contiguous. The -rsort parameter specifies a reverse sort.
It is also possible to sort files within an archive set copy by age, size, or path. The age and size arguments are mutually exclusive. CODE EXAMPLE 3-24 shows how to sort an archive set using the -sort parameter with the argument age or size. CODE EXAMPLE 3-24 Directives for Sorting an Archive Set cardiac.1 –sort path cardiac.2 -sort age catscans.3 -sort size The first line forces the archiver to sort an archive request by path name.
Assume that a patient is in the hospital for four weeks. During this time, all of this patient’s files are on fast media (copy 1=mo). After four weeks, the patient is released from the hospital. If no data has been accessed for this patient for up to 60 days after the patient is released, the copy 1 entry in the inode is unarchived, and only copy 2 and copy 3 entries are available. The volume can now be recycled in order to make room for more current patients without having to increase the disk library.
Note – The -reserve parameter is intended to reserve a volume for exclusive use by one archive set. Many directories with a few small files cause many small archive files to be written to each reserved volume. These small discrete archive files, each with its own tar(1) header, slow the performance of the system.
TABLE 3-18 Owner Set Form Examples (Continued) Directive and Keyword Reserved Name Examples -reserve user users.1/user5/ users.1/user4/ -reserve group ■ data.1/engineering/ File system form – The fs keyword specifies the file system component in the reserved name. TABLE 3-19 shows examples. TABLE 3-19 File System Form Examples Directive and Keyword Reserved Name Examples -reserve fs proj.1/p103/samfs1 proj.1/p104/samfs1 In the archiver.
As CODE EXAMPLE 3-28 shows, the lines in the library catalog that describe reserved volumes begin with #R characters. CODE EXAMPLE 3-28 Library Catalog Showing Reserved Volumes 6 00071 00071 lt 0xe8fe 12 9971464 1352412 0x6a000000 131072 0x # -il-o-b----- 05/24/00 13:50:02 12/31/69 18:00:00 07/13/01 14:03:00 #R lt 00071 arset0.3// 2001/03/19 18:27:31 10 ST0001 NO_BAR_CODE lt 0x2741 9 9968052 8537448 0x68000000 1310 # -il-o------- 05/07/00 15:30:29 12/31/69 18:00:00 04/13/01 13:46:54 #R lt ST0001 hgm1.
Setting Archive Priorities: -priority The Sun StorageTek SAM file systems offer a configurable priority system for archiving files. Each file is assigned a priority computed from properties of the file and priority multipliers that can be set for each archive set in the archiver.cmd file. Properties include online/offline, age, number of copies made, and size. By default, the files in an archive request are not sorted, and all property multipliers are zero.
For value, specify a floating-point number in the following range: -3.400000000E+38 ≤ value ≤ 3.402823466E+38 For more information on priorities, see the archiver(1M) and archiver.cmd(4) man pages. Scheduling Archiving: -startage, -startcount, and -startsize As the archiver scans a file system, it identifies files to be archived. Files that are recognized as candidates for archiving are placed in a list known as an archive request.
The -startage, -startcount, and -startsize directives can be specified in an archiver.cmd file for each archive copy. If more than one of these directives is specified, the first condition encountered starts the archive operation. If none of these directives is specified, the archive request is scheduled based on the examine= method directive, as follows: ■ If examine=noscan, the default values are as follows: startage 10 minutes, startcount 10,000, and startsize 10 gigabytes.
TABLE 3-22 Arguments for the VSN Association Directive (Continued) Argument Meaning media-type The media type. For a list of valid media types, see the mcf(4) man page. vsn-expr A regular expression. See the regexp(5) man page. -pool vsn-pool-name A named collection of VSNs. An association requires at least three fields: archive-set-name and copy-num, media-type, and at least one volume. The archive-set-name and copy-num values are connected by a period (.).
CODE EXAMPLE 3-32 VSN Specifications With Shorthand Notation vsns set.1 lt VSN0[1-9] VSN10 endvsns When the archiver needs volumes for the archive set, it examines each volume of the selected media type in all automated libraries and manually mounted drives to determine if the volume would satisfy any VSN expression. It selects the first volume that matches an expression that contains enough space for the archive copy operation.
A VSN pool is a named collection of volumes. VSN pools are useful for defining volumes that can be available to an archive set. As such, VSN pools provide a useful buffer for assigning volumes and reserving volumes to archive sets. You can use VSN pools to define separate groups of volumes by departments within an organization, by users within a group, by data type, and according to other convenient groupings. If a volume is reserved, it is no longer available to the pool in which it originated.
CODE EXAMPLE 3-33 VSN Pools vsnpools users_pool mo data_pool mo scratch_pool mo proj_pool mo endvsnpools vsns users.1 mo data.1 mo proj.1 mo endvsns ^MO[0-9][0-9] ^DA.* ^SC[5-9][0-9] ^PR.* -pool users_pool -pool data_pool -pool proj_pool -pool scratch_pool -pool scratch_pool -pool scratch_pool For more information on VSN associations, see “VSN Association Directives” on page 87. About Disk Archiving Archiving is the process of copying a file from online disk to archive media.
The following list summarizes some of the similarities and differences between archiving to online disk and archiving to removable media: ■ Unlike archive copies written to a magneto-optical disk or to a tape, archive copies written to disk are not recorded in a catalog. In addition, archive files in disk volumes do not appear in the historian.
Configuration Guidelines Although there are no restrictions on where disk archive volumes can reside, it is recommended that disk volumes reside on a disk other than the one on which the original files reside. It is also recommended that you make more than one archive copy and write to more than one type of archive media. For example, you might archive copy 1 to disk volumes, copy 2 to tape, and copy 3 to magneto-optical disk.
CODE EXAMPLE 3-34 An Example of the vsns and vsnpools Directives vsnpools data_pool dk disk0[0-5] endvsnpools vsns arset0.1 dk disk10 disk1[2-5] arset1.1 dk -pool data_pool endvsns Beginning with version 4U6 of the software, disk archiving can also be carried out on the Sun StorageTek 5800 system. The Sun StorageTek 5800 is an online storage appliance with an integrated hardware and software architecture in which the diskbased storage nodes are arranged in a symmetric cluster.
For more information on directives for disk archiving, see the archiver.cmd(4) man page. Note – If you are using the disk volumes on the Sun StorageTek 5800 for archiving, be aware that the Sun StorageTek 5800 is not a traditional file system and the security considerations are different from other types of disk storage. Read the Sun StorageTek 5800 documentation for more information. ▼ To Enable Disk Archiving You can enable disk archiving at any time.
b. Use the samd(1M) config command to propagate the configuration file changes and restart the destination system. # samd config 6. If you are archiving to a Sun StorageTek 5800 system, you must upgrade the Sun StorageTek 5800 metadata schema configuration. Follow the procedures documented in the Sun StorageTek 5800 System Administration Guide. Use the XML overlay in CODE EXAMPLE 3-36 to define the metadata that is used by Sun StorageTek SAM.
CODE EXAMPLE 3-37 shows the diskvols.conf file that resides on client system pluto. CODE EXAMPLE 3-37 The diskvols.conf File on pluto # This is file /etc/opt/SUNWsamfs/diskvols.conf on pluto # VSN Name [Host Name:]Path # disk01 /sam_arch1 disk02 /sam_arch2/proj_1 disk03 mars:/sam_arch3/proj_3 disk04 /sam_arch4/proj_4 CODE EXAMPLE 3-38 shows the diskvols.conf file on server system mars. CODE EXAMPLE 3-38 The diskvols.conf File on mars # This is file /etc/opt/SUNWsamfs/diskvols.
Example 2 In this example, file /sam1/testdir0/filea is in the archive set for arset0.1, and the archiver copies the content of this file to the destination path /sam_arch1. CODE EXAMPLE 3-40 shows the diskvols.conf file. CODE EXAMPLE 3-40 A diskvols.conf File # This is file /etc/opt/SUNWsamfs/diskvols.conf # # VSN Name [Host Name:]Path # disk01 /sam_arch1 disk02 /sam_arch12/proj_1 CODE EXAMPLE 3-41 shows the archiver.
Example 3 In this example, file /sam2/my_proj/fileb is on client host snickers in archive set arset0.1, and the archiver copies the content of this file to the destination path /sam_arch1 on server host mars. CODE EXAMPLE 3-43 shows the diskvols.conf file on snickers. CODE EXAMPLE 3-43 The diskvols.conf File on snickers # This is file /etc/opt/SUNWsamfs/diskvols.conf on snickers # # VSN Name [Host Name:]Path # disk01 mars:/sam_arch1 CODE EXAMPLE 3-44 shows the diskvols.conf file on mars.
■ Save your archive logs. The archive logs provide information that is essential to recovering data, even when the Sun StorageTek SAM software is unavailable. Keep these logs in a safe place in the event of a catastrophic disaster during which the Sun StorageTek SAM software is unavailable. ■ Use regular expressions for volumes. Allow the system to put files on many different volumes. Volume ranges (specified with regular expressions) allow the system to run continuously.
You can assign different priorities to preview requests. You can override the FIFO default by entering directives in the preview command file, which is written to /etc/opt/SUNWsamfs/preview.cmd. For more information about this file and setting priorities for archiving and staging, see “Prioritizing Preview Requests” on page 140. Archiver Examples This section provides some examples of archiving processes in real-world environments. Example 1: No archiver.
Note – The archiver(1M) -lv command only shows VSNs with space available. CODE EXAMPLE 3-47 archiver(1M) -lv Output Showing Available VSNs Archive libraries: Device:hp30 drives_available:2 archive_drives:2 Catalog: mo.optic00 capacity: 1.2G space: 939.7M mo.optic01 capacity: 1.2G space: 934.2M mo.optic02 capacity: 1.2G space: 781.7M mo.optic03 capacity: 1.2G space: 1.1G mo.optic10 capacity: 1.2G space: 85.5M mo.optic11 capacity: 1.2G space: 0 mo.optic12 capacity: 1.2G space: 618.9k mo.optic13 capacity: 1.
CODE EXAMPLE 3-49 shows the files in the archive sets archived to the volumes in the indicated order. CODE EXAMPLE 3-49 archiver(1M) -lv Output Showing Archive Sets and Volumes Archive sets: allsets samfs.1 media: mo (by default) Volumes: optic00 optic01 optic02 optic03 optic10 optic12 optic13 optic20 optic21 optic22 optic23 Total space available: 8.1G Example 2: Data Files Archived Separately From Metadata This example shows how to separate data files into two archive sets separate from the metadata.
CODE EXAMPLE 3-50 shows the content of the archiver.cmd file. CODE EXAMPLE 3-50 archiver(1M) -lv Output Showing the archiver.cmd File # archiver –lv -c example2.cmd Reading archiver command file "example2.cmd" 1: # Example 2 archiver command file 2: # Simple selections based on size 3: 4: logfile = /var/opt/SUNWsamfs/archiver/log 5: interval = 5m 6: 7: # File selections. 8: big . -minsize 500k 9: all . 10: 1 30s 11: 12: vsns 13: samfs.1 mo .*0[0-2] # Metadata to optic00 - optic02 14: all.1 mo .*0[3-9] .
CODE EXAMPLE 3-51 archiver(1M) -lv Output Showing Media and Drives (Continued) mo.optic22 capacity: mo.optic23 capacity: Device:lt40 drives_available:0 Catalog: lt.TAPE01 capacity: lt.TAPE02 capacity: lt.TAPE03 capacity: lt.TAPE04 capacity: lt.TAPE05 capacity: lt.TAPE06 capacity: 1.2G space: 244.9k 1.2G space: 1.1G archive_drives:0 9.5G 9.5G 9.5G 9.5G 9.5G 9.5G space: space: space: space: space: space: 8.5G 6.2G 3.6G 8.5G 8.5G 7.
CODE EXAMPLE 3-53 archiver(1M) -lv Output Showing Archive Sets and Removable Media (Continued) optic13 optic20 optic21 optic22 optic23 Total space available: big.1 media: lt Volumes: TAPE01 TAPE02 TAPE03 TAPE04 TAPE05 TAPE06 Total space available: samfs.1 media: mo Volumes: optic00 optic01 optic02 Total space available: 6.3G 42.8G 2.6G Example 3: User and Data Files Archived to Various Media In this example, user files and project data files are archived to various media.
CODE EXAMPLE 3-54 shows the output of the archiver(1M) -lv -c command in this example. CODE EXAMPLE 3-54 archiver(1M) -lv -c Command Output # archiver -lv -c example3.cmd Reading archiver command file “example3.
CODE EXAMPLE 3-54 archiver(1M) -lv -c Command Output (Continued) 33: joe.1 mo optic01$ 34: pict.1 mo optic02$ 35: pict.2 mo optic03$ 36: proj_1.1 mo optic1[0-1]$ 37: proj_1.2 mo optic1[2-3]$ 38: prod.1 mo optic2.$ 39: joe.2 lt 0[1-2]$ 40: prod_big.1 lt 0[3-4]$ 41: prod_big.2 lt 0[5-6]$ 42: endvsns Notify file: /etc/opt/SUNWsamfs/scripts/archiver.sh Archive media: media:lt archmax: 512.0M Volume overflow not selected media:mo archmax: 4.
CODE EXAMPLE 3-54 archiver(1M) -lv -c Command Output (Continued) prod path:data copy:1 arch_age:60 proj_1 path:projs/proj_1 copy:1 arch_age:60 copy:2 arch_age:60 joe path:. uid:10006 copy:1 arch_age:60 copy:2 arch_age:60 pict path:. gid:8005 copy:1 arch_age:60 copy:2 arch_age:60 no_archive Noarchive path:tmp samfs path:. copy:1 arch_age:240 Archive sets: allsets joe.1 media: mo Volumes: optic01 Total space available: 934.2M joe.2 media: lt Volumes: TAPE01 TAPE02 Total space available: 14.7G pict.
CODE EXAMPLE 3-54 archiver(1M) -lv -c Command Output (Continued) prod_big.1 media: lt drives:2 Volumes: TAPE03 TAPE04 Total space available: 12.1G prod_big.2 media: lt drives:2 Volumes: TAPE05 TAPE06 Total space available: 16.0G proj_1.1 media: mo Volumes: optic10 Total space available: 85.5M proj_1.2 media: mo Volumes: optic12 optic13 Total space available: 981.9M samfs.1 media: mo Volumes: optic00 optic01 Total space available: 1.
CODE EXAMPLE 3-55 shows the archiver.cmd file and archiver output. CODE EXAMPLE 3-55 archiver.cmd File and Archiver Output Reading archiver command file "example4.cmd" 1: # Example 4 archiver command file 2: # Using 4 VSN pools 3: 4: interval = 30s 5: logfile = /var/opt/SUNWsamfs/archiver/log 6: 7: fs = samfs 8: users users 9: 1 10m 10: 11: data data 12: 1 10m 13: 14: proj projects 15: 1 10m 16: 17: params 18: users.1 -reserve user 19: data.1 -reserve group 20: proj.
CODE EXAMPLE 3-55 archiver.cmd File and Archiver Output (Continued) Notify file: /etc/opt/SUNWsamfs/scripts/archiver.sh Archive media: media:mo archmax: 4.8M Volume overflow not selected Archive libraries: Device:hp30 drives_available:0 archive_drives:0 Catalog: mo.optic00 capacity: 1.2G space: 939.7M -il-o------mo.optic01 capacity: 1.2G space: 934.2M -il-o------mo.optic02 capacity: 1.2G space: 781.7M -il-o------mo.optic03 capacity: 1.2G space: 1.1G -il-o------mo.optic04 capacity: 1.2G space: 983.
CODE EXAMPLE 3-55 archiver.cmd File and Archiver Output (Continued) users_pool media: mo Volumes: optic01 optic02 optic03 Total space available: 2.7G Archive sets: allsets data.1 reserve:/group/ media: mo Volumes: optic10 optic20 optic21 optic22 optic23 Total space available: 3.4G proj.1 reserve:/dir/fs media: mo Volumes: optic12 optic13 optic20 optic21 optic22 optic23 Total space available: 4.2G samfs.1 media: mo Volumes: optic00 Total space available: 939.7M users.
114 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
CHAPTER 4 Releasing Releasing is the process by which the releaser makes disk cache space available by identifying archived files and releasing their disk cache copy. This makes room for other files to be created or staged from archive media. The releaser can release only archived files. A released file has no data on the disk cache. The Sun StorageTek SAM software automatically invokes the releaser process when a site-specified disk threshold is reached.
2. Scans the file system and collects information about each file. 3. Begins releasing files in priority order. A file system can contain thousands of files. Keeping track of the release priority for every file can be wasteful because releasing only several large files might return the file system to its low-water mark. However, the releaser must examine the priority of each file or risk missing the best candidates for release. The releaser does this by identifying the first 10,000 candidates.
■ ■ Candidate – A candidate is a file that is eligible to be released. A file is not a candidate under the following circumstances: ■ The file is already offline. ■ The file has not been archived. ■ The archiver.cmd command file specifies the -norelease attribute for the file, and the required copies have not yet been made. ■ The file is marked as damaged. ■ The file is not a regular file. It is a directory, block, character-special file, or pipe.
About Partial Releasing and Partial Staging Releasing and staging are complementary processes. Files can be completely released from online disk cache after they are archived, or a site can specify that the beginning of a file (the stub) remain in disk cache while the remainder of the file is released. Partially releasing a file provides immediate access to data in the file stub without requiring that the file be staged first.
■ If the -o partial_stage=n option is set to the size of the partial release stub, the default behavior prevents the file from being staged until the application reaches the end of the partial release stub. Waiting until the end of the stub is reached causes a delay in accessing the rest of the file. ■ If the -o partial_stage=n option is set to a value smaller than the partial release stub, the file is staged after the application crosses the threshold set by the -o partial_stage=n option.
System Administrator Option Summary As system administrator, you can change the maximum value and default value for partial release when the file system is mounted. The mount(1M) options in TABLE 4-1 affect partial release. For more information about the mount(1) command, see the mount_samfs(1M) man page.
User Option Summary As system administrator, you can set maximum and default values for the size of a file stub that can remain in disk cache after the file is released. You can also determine whether the partial release feature is enabled for a particular file system. By using the release(1) command and the sam_release(3) library routines, however, a user can set other release attributes and can specify the files to be marked for partial release.
The following subsections describe the releaser.
By default, the age of a file is the more recent of the file’s three ages. In some cases, a simple age derived from the most recently accessed time, modified time, and residence-changed time is preferred. In other cases, you might want the access age of a file to take precedence over the modification age. You can use directives to specify that a weighted age priority be used when calculating the release priority for a file. CODE EXAMPLE 4-1 shows the formats of the age priority directive.
CODE EXAMPLE 4-2 shows lines in a releaser.cmd file specifying that only the file’s residence age be considered, and that the modification age and the access age be ignored, when the release priority of a file is calculated. CODE EXAMPLE 4-2 releaser.cmd File Fragment weight_age_residence = 1.0 weight_age_modify = 0.0 weight_age_access = 0.0 After a file’s age-related priority is calculated, it is multiplied by the file’s sizerelated priority.
The fs Directive: Specifying Directives for Individual File Systems You can use the fs = family-set-name directive in the releaser.cmd file to indicate that the directives that follow the fs = directive apply only to the named file system. This directive has the following format: fs = family-set-name For family-set-name, specify the name of a family set in the mcf file. Directives preceding the first fs = directive are global and apply to all file systems.
These directives are helpful during debugging because the releaser writes the names of release candidates to the log file, but it does not physically release them from the file system. The min_residence_age Directive: Specifying a Minimum Residence Time The min_residence_age directive enables you to specify the minimum amount of time that a file must reside in a file system before it becomes a candidate for release.
CODE EXAMPLE 4-4 Releaser Log File Example (Continued) display_all_candidates? no ---before scan--blocks_now_free: 3481504 lwm_blocks: 3729362 ---scanning--10501 (R: Wed Apr 21 18:47:50 CDT 2006) 10001 min, 500 blks /sam1/testdir0/filevp 10500 (R: Wed Apr 21 18:48:10 CDT 2006) 10000 min, 500 blks /sam1/testdir0/filewq ...
The rearch_no_release Directive: Inhibiting Releasing for Rearchived Files By default, files marked for rearchiving are released. If the rearch_no_release directive is specified in the releaser.cmd file, the releaser does not release the files marked for rearchiving. This directive has the following format: rearch_no_release The list_size Directive: Adjusting the Size of the Releaser Candidate List You can use the list_size directive to specify the number of releaser candidates.
TABLE 4-3 shows archive set assignment values that pertain to releasing. TABLE 4-3 Archive Set Assignment Values for Releasing Directive Effect -release a Specifies that the files in the archive set should be released after the first archive copy is made. Do not use this option if you are making more than one archive copy of each file. In such a situation, copy 1 would be staged in order to make copy 2. -release d Reset to default.
CODE EXAMPLE 4-6 Directives to Release Oldest Modified Files First weight_size = 0.0 weight_age_access = 0.0 weight_age_modify = 1.0 weight_age_residence = 0.0 However, most situations are not this straightforward. Assume that you want to release the largest files first. There are hundreds of small files that are the same size, and there are several large files. Eventually, the releaser releases all the large files. If weight_age = 0.
For example, to release files in the /sam1 file system until it reaches 47 percent full, log in as root and type the following: # /opt/SUNWsamfs/sbin/sam-releaser /sam1 47 1.0 Command-line options override options specified in the releaser.cmd file. As the releaser runs, it writes information to your screen and to the releaser log file, if one is specified in the releaser.cmd file. For more information, see the sam-releaser(1M) man page.
132 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
CHAPTER 5 Staging Staging is the process of copying file data from nearline or offline storage back to online storage. This chapter describes the Sun StorageTek SAM file staging capabilities. It contains the following sections: ■ “About the stager.cmd File” on page 133 ■ “Prioritizing Preview Requests” on page 140 ■ “Calculating Total Preview Request Priority” on page 144 ■ “Setting Up a Preview Request Priority Scheme” on page 144 About the stager.cmd File You can use the stager.
The rest of this section describes the stager directives. For additional information on stager directives, see the stager.cmd(4) man page. The “Example stager.cmd File” on page 139 shows the completed stager.cmd file after all possible directives have been set. Note – If you are using the File System Manager software, you can control staging from the File System Summary or File System Details page.
TABLE 5-1 Arguments for the drives Directive Argument Meaning library The family set name of a library as it appears in the Sun StorageTek SAM mcf file. count The maximum number of drives to be used. By default, this is the number of drives configured in the mcf file for this library. For example, the following directive line specifies that only one drive from the dog family set’s library be used for staging files: drives = dog 1 For more information on the mcf file, see the mcf(4) man page.
TABLE 5-2 Arguments for the bufsize Directive (Continued) Argument Meaning lock The lock argument indicates that the stager should use locked buffers when staging archive copies. If lock is specified, the stager sets file locks on the stage buffer in memory for the duration of the copy operation. This avoids the overhead associated with locking and unlocking the buffer for each I/O request and can thereby result in a reduction in system CPU time.
TABLE 5-3 Values for the event Argument (Continued) Value Action finish Logs when staging ends for a file. Enabled by default. cancel Logs when the operator cancels a stage. Enabled by default. error Logs staging errors. Enabled by default. When a log file is specified, the stager writes one or more lines to the log file for each file staged. This line includes information such as the name of the file, the date and time of the stage, and the volume serial number (VSN).
Stager Log File Example (Continued) CODE EXAMPLE 5-1 S 2003/12/16 14:07:47 dk disk01 26.c4d 2831.1113 1428718 /sam1/testdir0/fileez 1 root other root 0 S 2003/12/16 14:07:47 dk disk02 1b.835 3736.59 1787855 /sam1/testdir1/filedp 1 root other root 0 - As CODE EXAMPLE 5-1 shows, the stager log file consists of lines of information divided into nine fields. TABLE 5-4 describes the content of the stager log file fields.
Specifying the Number of Stage Requests The maxactive directive enables you to specify the number of stage requests that can be active at any one time. This directive has the following format: maxactive=number By default, number is 4000. The minimum number allowed is 1. The maximum allowed is 500,000. For example, the following directive line specifies that no more than 500 stage requests can be in the queue simultaneously: maxactive=500 Example stager.cmd File CODE EXAMPLE 5-2 shows an example stager.
Chapter 3 describes the archive set assignment directive and its arguments completely. TABLE 5-5 shows the staging directives that can appear in an archive set assignment directive. TABLE 5-5 Staging Directives That can Appear in the archiver.cmd File Directive Effect -stage a Specifies that the files in the archive set should be associatively staged. -stage d Reset to default. -stage n Specifies that the files in the archive set should never be staged.
The following types of directives can appear in the preview.cmd file: ■ Global directives, which apply to all file systems. These must appear before the first fs = line. ■ Directives that are specific to individual file systems. These directives must appear in the file after all global directives. File system directives begin with fs = file-system-name. This directive names the file system to which all subsequent directives pertain. More than one block of file directives can appear in a file.
If this factor is more than 1.0, it increases the importance of the time factor in calculation of the total priority. If it is less than 1.0, it decreases the importance of the time factor. Setting the factor to 0.0 eliminates the time factor from the overall priority calculation. A VSN whose priority flag is not set increases in priority based on the time it remains in the queue. Its priority can become higher than a VSN that comes into the queue later with the priority flag already set.
TABLE 5-6 Water Mark Priority Directives (Continued) Priority Directive Argument lhwm_priority = value For value, specify the amount by which you want the water mark priority factor to change for archiving requests when the file system crosses from below to above the LWM but remains below the HWM level. This generally indicates that the file system is filling up. The default is 0.0.
Calculating Total Preview Request Priority The numeric priority of preview requests is determined by the combination of static and dynamic factors. Higher numbers correspond to higher priority. A static priority factor is set when the request is generated. Its effect does not change the overall priority after the request is generated and is waiting to be satisfied. A dynamic priority factor can increase or decrease the overall priority of a request while the request is waiting to be satisfied.
CODE EXAMPLE 5-4 shows an example preview.cmd file that addresses these three conditions. CODE EXAMPLE 5-4 Example preview.cmd File # condition 1 lwm_priority = -200.0 lhwm_priority = -200.0 hlwm_priority = -200.0 # condition 2 hwm_priority = 500.0 # condition 3 age_priority = 1.0 For environments in which user access to data is of paramount importance, the VSN drives are limited, or file archival is performed as a background function, you can use the preview.
Example 2: Enforcing Archive Requests When the environment is balanced between the importance of staging a file back to the user and the importance of getting new files archived to media, the biggest concern is exceeding the HWM. In this situation, if not enough files have met their archive requirements to lower the percentage of the file system that is full, meeting the pending archive requests is the best way to keep the file system from filling up. In this situation, the preview.
Example 4: Complex Prioritization Assume that there are two Sun StorageTek SAM file systems with the following requirements: ■ No request should sit too long in the queue (age_priority). ■ When one of the file systems is below the LWM, staging requests should take precedence. ■ When one of the file systems is above the LWM but below the HWM, it is not necessary to prioritize archive or stage requests one over the other. CODE EXAMPLE 5-5 shows the affected directives.
148 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
CHAPTER 6 Recycling Recycling is the process of reclaiming space on archive volumes. The recycler works with the archiver to reclaim the space occupied by unused archive copies. As users modify files, the archive copies associated with the old versions can be purged from the system. The recycler identifies the volumes with the largest proportions of expired archive copies and directs the movement of unexpired copies to different volumes.
The capacity of a volume is the total amount of space for data on a volume. For example, a 10-gigabyte tape volume with 3 gigabytes written to it has a capacity of 10 gigabytes and 7 gigabytes of free space. New or newly labeled archive media starts out with all its capacity as free space. As data is archived to the media, the amount of free space decreases and the amount of current data increases.
Before configuring the recycler, note the following: ■ Directives in the archiver.cmd file control recycling by archive set. Directives in the recycler.cmd file control recycling by library. In addition, the recycler.cmd file controls general recycler behavior. For information on recycler directives, see “Using Recycling Directives” on page 152. ■ Do not recycle volumes that contain removable media files. You create removable media files by using the request(1) command.
Recycling Tape Libraries You initiate recycling for tape libraries by entering the sam-recycler(1M) command either manually or through a cron(1) job. TABLE 6-1 shows recycling methods. TABLE 6-1 Recycling Methods and Media Types Recycling Method Media and Notes By automated library Removable media cartridges. When you archive by library, you put recycling directives in the recycler.cmd file. By archive set Removable media cartridges and disk.
The following is an example of a logfile= directive line: logfile=/var/adm/recycler.log Preventing Recycling: The no_recycle Directive The no_recycle directive enables you to prevent recycling of volumes. To specify the VSNs, you use regular expressions and one or more specific media types. This directive has the following format: no_recycle media-type VSN-regexP [ VSN-regexP ... ] TABLE 6-2 Arguments for the no_recycle Directive Argument Meaning media-type A media type from the mcf(4) man page.
For library, specify the library’s name as specified in the family set field of the mcf file. For parameter, specify one or more space-separated parameter keywords from TABLE 6-3. TABLE 6-3 Library Directive parameter Values parameter Value Meaning -dataquantity size Maximum amount of data that the recycler can schedule for rearchiving in its efforts to clear volumes of useful data. Default is 1 gigabyte. -hwm percent Library high-water mark. Default is 95.
Configuring the recycler for a tape library involves the tasks described in the following sections, in this order: 1. “Creating a recycler.cmd File” on page 155 2. “Editing the archiver.cmd File” on page 161 (This step is optional for recycling tape libraries) 3. “To Run the Recycler” on page 158 4. “Creating a crontab File for the Recycler” on page 159 5. “To Remove -recycle_ignore and ignore Parameters” on page 159 6. “Creating a recycler.sh File” on page 160 Creating a recycler.
3. Add one or more directives described in this chapter to control recycler activity. 4. Save and close the file. Alternatively, you can create a recycler.cmd file by using File System Manager software. For more information, see the File System Manager online help. Example recycler.cmd File CODE EXAMPLE 6-1 shows an example of a recycler.cmd file. CODE EXAMPLE 6-1 Example recycler.cmd File logfile = /usr/tmp/recycler.
Note – You can force a VSN to be recycled by using the following command to set the recycling flag: # chmed +c lt.VSN When the +c flag is set, the archiver does not write any more archive images to the volume. The +c flag can be viewed through the samu(1M) utility. For more information, see the chmed(1M) and samu(1M) man pages. For information on using the samu(1M) operator utility, see the Sun StorageTek QFS File System Configuration and Administration Guide.
TABLE 6-2 shows sample message bodies. CODE EXAMPLE 6-2 Sample Recycling Messages I will recycle VSN vsn. Cannot find any candidate VSN in this media changer. Previously selected VSN vsn is not yet finished recycling. Previously selected VSN vsn is now finished recycling. It will now be post-recycled. ▼ To Run the Recycler Follow these instructions to manually run the recycler. 1. Issue the sam-recycler(1M) command. The recycler reads the recycler.cmd file. 2.
CODE EXAMPLE 6-3 Recycler Log File Example for Removable Media Cartridges (Continued) Volume utilization 22%, high 95% VSN_min 50% Recycling is ignored on this robot. 1 Family: hy Path: /var/opt/SUNWsamfs/catalog/historian Vendor: Sun SAM-FS Product: Historian SLOT ty capacity space vsn (no VSNs in this media changer) Total Capacity: 0 bytes, Total Space Available: 0 bytes Volume utilization 0%, high 95% VSN_min 50% Recycling is ignored on this robot.
1. Use vi(1) or another editor to remove the -recycle_ignore parameters from the archiver.cmd file. 2. Use vi(1) or another editor to remove the ignore parameters from the recycler.cmd files. You are now recycling. Creating a recycler.sh File Create a recycler.sh file if you are recycling archive copies on removable media cartridges. If you are archiving only to disk, do not perform this step. The recycler executes the recycler.
Editing the archiver.cmd File If you are archiving to disk, you must edit the archiver.cmd file in order to recycle. If you are recycling by library, this step is optional. To edit the archiver.cmd file, follow the steps described in “To Create or Modify an archiver.cmd File and Propagate Your Changes” on page 47. Alternatively, you can edit the archiver.cmd file by using the File System Manager. For more information, see the File System Manager online help.
TABLE 6-4 Archive Set Recycling Directives (Continued) Directive Function -rearch_stage_copy copy-number Allows staging for rearchiving to take place from selected (faster) copies. For more information about archiver directives, see Chapter 3 or see the archiver.cmd(4) man page. ▼ To Run the Recycler Follow these instructions to manually run the recycler. 1. Issue the sam-recycler(1M) command. The recycler reads the recycler.cmd file. 2.
▼ To Remove -recycle_ignore and ignore Parameters If you have used the -recycle_ignore or ignore parameter to disable recycling during configuration, use this procedure to remove them. As an alternative to the following procedure, you can use the File System Manager. For more information, see the File System Manager online help. 1. Use vi(1) or another editor to remove the -recycle_ignore parameters from the archiver.cmd file. 2.
You can also include a logfile= directive line in the nrecycler.cmd file to specify an nrecycler log file. The system writes recycling messages and recycling reports to this file. When sam-nrecycler(1M) detects that a removable media volume contains only free or expired space and is safe to relabel, it invokes the sam-nrecycler.sh script. The script can relabel the cartridge using either the original VSN or a new VSN.
CHAPTER 7 Using the Sun SAM-Remote Software The Sun SAM-Remote client and the Sun SAM-Remote server form a client/server implementation that allows libraries and other removable media devices to be shared between Sun StorageTek SAM host systems. Sun SAM-Remote enables you to configure multiple storage clients that archive and stage files from a centralized tape library or magneto-optical library.
Features FIGURE 7-1 shows an environment configured with two Sun SAM-Remote host system servers. Each has two clients.
configuration include the ability to create local copies for each server with an additional archive copy of data on the other server. File systems can be shared between servers using standard NFS. In the event of a loss of access to the local library, Sun SAM-Remote software would automatically retrieve file data from the archive copy. Users of both servers would have uninterrupted access to their data, even if their primary storage library were unavailable.
Client and Server Interactions Sun SAM-Remote clients interact with the Sun SAM-Remote server using a TCP/IP connection. The network between Sun SAM-Remote clients can be any network type supported by the Solaris OS, such as Ethernet, Fast Ethernet, or Fibre Channel. FIGURE 7-2 shows Sun SAM-Remote client and Sun SAM-Remote server interactions.
per daemon. To configure more than ten clients, add an additional remote server entry in the mcf file for each ten clients that you want to configure. For more information about the server daemon, see the sam-remote(7) man page. Sun SAM-Remote Client Overview The Sun SAM-Remote client is a Sun StorageTek SAM host system that establishes a Sun SAM-Remote client daemon containing a number of pseudo-devices.
Upon initialization, the system builds a client catalog and passes it to the Sun SAMRemote client based on information from the Sun SAM-Remote server catalog file. After the connection between the host and client is established, media available to the client is flagged as available. If the connection between the client and server is lost, the media on the client side is flagged as unavailable. You can view the media availability through the samu(1M) v display.
Enterprise Backbone (TCP/IP) Automated Library Sun SAM-Remote server chicago Sun SAM-Remote client portland TCP/IP Sun SAM-Remote client sacramento TCP/IP Sun SAM-QFS File System FIGURE 7-3 Example Sun SAM-Remote Configuration The Sun StorageTek SAM file systems on portland and sacramento use chicago as their Sun SAM-Remote server.
7. “To Enable Archiving” on page 180 ▼ To Log In to the Potential Server and Client Hosts Follow these steps for the potential server and all potential client hosts. 1. Log in to the Sun SAM-Remote server as the superuser. You must have superuser access to the server system on which the Sun Sun SAM-Remote software is to be installed. 2. Log in to the Sun SAM-Remote clients as the superuser.
The same release and revision level of Sun StorageTek SAM software must be installed on all client and server hosts to be configured as part of a Sun SAM-Remote environment. In the example output shown in CODE EXAMPLE 7-1, you can see that the server (chicago) is running software version 4U0.5, and any systems included in an environment with this server would also have to be running 4U0.5. 2. Issue the showrev(1M) command with its -p option, and examine the output.
Alternatively, you can also idle the drives by using the samu(1M) operator utility. For information on using the samu(1M) operator utility, see the Sun StorageTek QFS File System Configuration and Administration Guide. Note – The drives in your Sun StorageTek SAM environment should be idled before you issue the samd stop command. This enables the archiver, stager, and other processes to complete current tasks. This also enables the cartridges to be unloaded and put into their storage slots. b.
mcf File on portland CODE EXAMPLE 7-3 # mcf file on portland # # Sun StorageTek QFS file system # # Equipment Eq Eq Family Dev Additional # Identifier Ord Ty Set St Parameters # ========== === == ====== == ========== samfs1 1 ms samfs1 on /dev/dsk/c1t1d0s0 10 md samfs1 on /dev/rdsk/c1t1d0s0 /dev/dsk/c1t2d0s0 12 md samfs1 on /dev/rdsk/c1t2d0s0 # # Define Sun SAM-Remote Client portland to Sun SAM-Remote server chicago # /etc/opt/SUNWsamfs/rmt200 200 sc chicagoss on /var/opt/SUNWsamfs/catalog/tcat /dev/samrd
The last two entries in this mcf file define the Sun SAM-Remote pseudo-devices, as indicated by the rd equipment type. A pseudo-device defines a network connection to an actual device on the Sun SAM-Remote server. Pseudo-device entries are created when the system is rebooted. You can define an unlimited number of pseudo-devices. ▼ To Define a Sun SAM-Remote Client The Sun SAM-Remote client’s configuration file contains a single-line entry consisting of the name of the Sun SAM-Remote server.
CODE EXAMPLE 7-5 shows the mcf file on chicago. CODE EXAMPLE 7-5 mcf File on chicago # mcf file on Sun SAM-Remote server chicago: # Eq Identifier Eq Ord Eq Typ Fam Set Dev St Addl Params # samfs1 1 ms samfs1 on /dev/dsk/c2t6d0s0 11 md samfs1 on /dev/rdsk/c2t6d0s0 /dev/dsk/c2t6d0s1 12 md samfs1 on /dev/rdsk/c2t6d0s1 # # define a tape library that client portland can use: /dev/samst/c0t3u0 100 rb rb100 on /var/opt/SUNWsamfs/catalog/rb100.
As CODE EXAMPLE 7-6 shows, a server configuration file consists of multiline entries for each client. A pound character (#) indicates a comment line. Anything to the right of a comment line is ignored.
The parameter line is expressed in a keyword = value pair. You can use the parameter field to specify the network block size. The net_block_size parameter specifies the network block size to be used by this client’s socket, in kilobytes. The format for this parameter is as follows: net_blk_size=size For size, specify an integer from 4 ≤ size ≤ 64. The default is 4, which specifies 4096 bytes. The parameter line must be indented with white space or tab characters c.
Argument Definition media-type The two-character specific media type, such as lt. The generic media type specifications that are valid in the mcf file are not valid for the media-type specification. For information about valid media types, see the mcf(4) man page. Specify more than one media definition line if you have a network attached library with more than one media type.
To ensure that the new configuration files on the server and clients are read, you must start or restart your Sun StorageTek SAM software. Enter the following command on the clients and the server: server# samd start For more complete instructions about starting and restarting Sun StorageTek SAM, see the Sun StorageTek Storage Archive Manager Installation and Upgrade Guide. 3. Invoke samu(1M) on the server and the clients. The goal of this step is to verify the connection between hosts.
CODE EXAMPLE 7-10 shows the samu(1M) status s display on the Sun SAM-Remote server chicago. Note the device type ss, which represents the Sun SAM-Remote server. This display indicates that this system is a Sun SAM-Remote server. CODE EXAMPLE 7-10 Server samu(1M) s Display on chicago Device status samu 4.0.5 Tue Apr 24 14:49:43 License: License never expires.
In CODE EXAMPLE 7-11, the connected client is named portland. The client index field indicates that this client is the zero of a possible 0 through 9 clients defined for this server daemon. The maximum file size, minimum file size, and network block size are listed in bytes. Flags indicate the state of the connection, as shown in TABLE 7-1: TABLE 7-1 The samu(1M) R Display Flags Flag Meaning 0x00000000 No connection. 0xc0000000 A connection has been established. 4.
5. From each client, issue the archiver(1M) command and its -A option. In this step, you verify that archiving is taking place from the client to the server. This command enables a listing to be written from the archiver, including the VSNs from the server. For information about this command, see the archiver(1M) man page. If files are not archiving, see the Sun StorageTek Storage Archive Manager Troubleshooting Guide.
You can prevent accidental recycling of VSNs used by Sun SAM-Remote clients by creating a no_recycle list in the Sun SAM-Remote server’s /etc/opt/SUNWsamfs/recycler.cmd file. However, be careful of using the chmed(1M) command’s +c option on volumes in a no_recycle list. When you use this command to set the recycling flag (+c) on a volume, that action overrides the no_recycle list in the /etc/opt/SUNWsamfs/recycler.cmd file.
Configuration Files for Server sky The server must have Sun SAM-Remote configuration information in its mcf file and in its server configuration file. The following code examples show these files. CODE EXAMPLE 7-13 shows the mcf file on server sky. CODE EXAMPLE 7-13 The mcf File on Server sky # This is the mcf file for the server (sky). # The server parameters file (rmt1000) points # back to the correct automated library’s equipment number # (70) for the ADIC Scalar 1000.
CODE EXAMPLE 7-14 shows the server configuration file on server sky. CODE EXAMPLE 7-14 The Server Configuration File on Server sky # Server configuration file /etc/opt/SUNWsamfs/rmt1000 on sky. # The eq of the automated library MUST match the eq of the # automated library that you want to use in the mcf file. zeke media 70 at 00002[0-9] endmedia Configuration Files for Client zeke The client must have Sun SAM-Remote configuration information in its mcf file and in its client configuration file.
▼ To Configure Recycling—Method 1 The procedure for configuring the recycling process includes a test for archiving and recycling. Because of the testing period, this procedure can take a day or two to complete, depending on how frequently files are archived and recycled. Before starting the procedure, read about the recycler in Chapter 6. Using the recycler in a Sun SAM-Remote environment requires a complete understanding of the steps in the recycling process.
CODE EXAMPLE 7-17 The archiver.cmd File on Client zeke # This is file /etc/opt/SUNWsamfs/archiver.cmd # on Sun SAM-Remote client zeke. # # wait logfile = /var/opt/SUNWsamfs/archiver/archiver.log trace = /var/opt/SUNWsamfs/trace/archiver all interval = 1m no_archive tmp no_archive . archmax = lt 2G archmax = at 5G drives = skyrs 4 # use up to four drives for remote archiving. fs = samfs1 1 4h archiveset testdir0 1 1m 2 1m defaultset . 1 1m 2 1m params # Start with mingain high to reduce workload.
CODE EXAMPLE 7-17 The archiver.cmd File on Client zeke (Continued) # Remote directives. # Start with mingain high to reduce workload. # If you need more recycling, reduce mingain. # If too much recycling, increase High-Water Mark. archiveset.2 -recycle_hwm 60 -recycle_mingain 90 -recycle_vsncount 1 archiveset.2 -recycle_ignore defaultset.2 -recycle_hwm 60 -recycle_mingain 90 -recycle_vsncount 1 defaultset.2 -recycle_ignore endparams vsns samfs1.1 lt 000173 archiveset.1 lt ^CEL archiveset.
CODE EXAMPLE 7-18 The recycler.cmd File on Client zeke # # This is the /etc/opt/SUNWsamfs/recycler.cmd file # on client zeke. # logfile = /var/opt/SUNWsamfs/log/recycler 4. Verify that the archiver.cmd file on the server is written to specify recycling by archive set. When using Sun SAM-Remote, you must specify that recycling be performed on an archive set basis, not by library. The directives specifying that recycling be done by archive set must appear in the archiver.cmd file.
CODE EXAMPLE 7-19 The archiver.cmd File on Server sky (Continued) allsam1.1 -drives 4 -drivemin 50m allsam1.1 -recycle_hwm 60 -recycle_mingain 90 -recycle_vsncount allsam1.1 -recycle_ignore allsam1.2 -drives 4 -drivemin 50m allsam1.2 -recycle_hwm 60 -recycle_mingain 90 -recycle_vsncount allsam1.2 -recycle_ignore testset.1 -drives 4 -drivemin 50m testset.1 -recycle_hwm 60 -recycle_mingain 90 -recycle_vsncount testset.1 -recycle_ignore testset.2 -drives 4 -drivemin 50m testset.
6. Use the sam-recycler(1M) command to test the recycler on the Sun SAM-Remote client. Run the recycler on the Sun SAM-Remote client system. This is a test to see if the recycler properly acknowledges the devices and VSNs specified in the configuration files.
CODE EXAMPLE 7-21 shows a sample log file. CODE EXAMPLE 7-21 Recycler Log File on Client zeke # recycler.log from client zeke. ========== Recycler begins at Mon Jun 4 09:49:41 2001 =========== Initial 7 catalogs: 0 Family: stk_l20 Path: /var/opt/SUNWsamfs/catalog/L20_cat Vendor: STK Product: L20 SLOT ty capacity space vsn 0 lt 33.0G 33.0G 000173 1 lt 32.8G 44.1M CEL170 2 lt 33.0G 33.0G CEL139 4 lt 32.8G 16.8G CFC504 5 lt 33.0G 33.0G CFC503 6 lt 32.9G 0 CSM689 7 lt 32.9G 19.6G CSM690 8 lt 33.0G 33.
CODE EXAMPLE 7-21 Recycler Log File on Client zeke (Continued) 2 Family: hy Path: /var/opt/SUNWsamfs/catalog/historian Vendor: Sun SAM-FS Product: Historian SLOT ty capacity space vsn (no VSNs in this media changer) Total Capacity: 0 bytes, Total Space Available: 0 bytes Volume utilization 0%, high 95% VSN_min 50% Recycling is ignored on this robot. 3 Family: defaultset.1 Path: /etc/opt/SUNWsamfs/archiver.cmd Vendor: Sun SAM-FS Product: Archive set SLOT ty capacity space vsn 0 lt 33.0G 33.
CODE EXAMPLE 7-21 6 Recycler Log File on Client zeke (Continued) Family: archiveset.2 Path: /etc/opt/SUNWsamfs/archiver.cmd Vendor: Sun SAM-FS Product: Archive set SLOT ty capacity space vsn 0 at 48.5G 23.3G 000020 1 at 23.8G 23.8G 000021 2 at 48.5G 48.5G 000022 3 at 48.5G 48.5G 000023 4 at 48.5G 48.5G 000024 Total Capacity: 218.0G bytes, Total Space Available: 192.8G bytes Volume utilization 11%, high 60% VSN_min 90% Recycling is ignored on this archive set.
CODE EXAMPLE 7-21 Recycler Log File on Client zeke (Continued) ---Archives-------Status----Count Bytes empty VSN 0 0 partially full 13 80.3k Recycler finished. ========== Recycler ends at Mon Jun -----Percent----stk_l20 Use Obsolete Free Library:Type:VSN 0 0 100 stk_l20:lt:CLN018 0 0 100 stk_l20:lt:CEL139 4 09:49:53 2001 =========== 8. Issue the sam-recycler(1M) command from the Sun SAM-Remote server to verify that the recycler is not recycling any VSNs reserved for the Sun SAM-Remote client.
CODE EXAMPLE 7-22 13 14 15 16 17 18 19 20 21 22 23 24 25 The Recycler Log File (Continued) at at at at at at at at at at at at at 48.5G 48.5G 48.5G 48.5G 1.3G 48.5G 23.8G 23.8G 23.8G 23.8G 48.5G 1.3G 48.5G 361.4k 48.5G 48.5G 0 1.3G 48.5G 23.8G 23.8G 23.8G 23.8G 421.6M 1.3G 0 000026 000027 000028 000029 000005 000016 CLN001 CLN002 CLN004 CLN003 000015 000000 000013 26 at 1.3G 1.3G 000003 27 at 48.5G 43.6G 000007 28 at 48.5G 41.8G 000008 29 at 48.5G 46.9G 000006 30 at 48.5G 48.3G 000009 31 at 48.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) 3 Family: testset.2 Path: /etc/opt/SUNWsamfs/archiver.cmd Vendor: Sun SAM-FS Product: Archive set SLOT ty capacity space vsn 0 at 48.5G 0 000019 1 at 48.5G 421.6M 000015 Total Capacity: 97.1G bytes, Total Space Available: 421.6M bytes Volume utilization 99%, high 60% VSN_min 90%: *** Needs recycling *** Recycling is ignored on this archive set. 4 Family: allsam1.1 Path: /etc/opt/SUNWsamfs/archiver.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) Checking 000014. Need to free 0E, quantity VSN is in correct media changer... good. VSN is not already recycling... good. VSN has no request files... good. VSN has no ‘archive -n’ files...good. VSN was not specified as “no_recycle” in VSN exceeds VSN count limit - skipped. Checking 000019. Need to free 0E, quantity VSN not in correct media changer. Checking 000015. Need to free 0E, quantity VSN not in correct media changer.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) Checking 000026. Need to free 0E, quantity VSN not in correct media changer. Checking 000025. Need to free 0E, quantity VSN not in correct media changer. Checking 000020. Need to free 0E, quantity VSN not in correct media changer. Checking 000017. Need to free 0E, quantity VSN not in correct media changer. Checking 000018. Need to free 0E, quantity VSN not in correct media changer. Checking CLN003.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) Checking 000019. Need to free 38.8G, quantity limit: (no limit), VSN count: 1. VSN is in correct media changer... good. VSN is not already recycling... good. VSN has no request files... good. VSN has no ‘archive -n’ files...good. VSN was not specified as “no_recycle” in recycler.cmd file... good. VSN does not exceed VSN count limit... good. VSN does not exceed data quantity limit... good. VSN meets minimum gain requirement.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) Checking 000013. Need to free 0E, quantity VSN not in correct media changer. Checking 000012. Need to free 0E, quantity VSN not in correct media changer. Checking 000026. Need to free 0E, quantity VSN not in correct media changer. Checking 000025. Need to free 0E, quantity VSN not in correct media changer. Checking 000020. Need to free 0E, quantity VSN not in correct media changer. Checking 000017.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) -----Status----no-data VSN no-data VSN ---Archives--Count Bytes 0 0 0 0 -----Percent----Use Obsolete Free 0 100 0 0 100 0 testset.1 Library:Type:VSN adic1:at:000010 adic1:at:000014 -----Status----no-data VSN partially full ---Archives--Count Bytes 0 0 677 2.3G -----Percent----Use Obsolete Free 0 100 0 5 93 2 testset.
CODE EXAMPLE 7-22 The Recycler Log File (Continued) no_recycle VSN no_recycle VSN no_recycle VSN no_recycle VSN no_recycle VSN no_recycle VSN empty VSN empty VSN empty VSN empty VSN partially full 0 0 0 0 0 0 0 0 0 0 12 0 0 0 0 0 0 0 0 0 0 88.3k Recycler finished.
CODE EXAMPLE 7-23 The recycler.log File on Client zeke # From the client zeke recycler.log file: ---Archives-------Percent---------Status----Count Bytes Use Obsolete Free no-data VSN 0 0 0 100 0 no-data VSN 0 0 0 99 1 partially full 111 2.8G 6 88 6 empty VSN 0 0 0 0 100 empty VSN 0 0 0 0 100 defaultset.2 Library:Type:VSN skyrs:at:000029 skyrs:at:000026 skyrs:at:000025 skyrs:at:000028 skyrs:at:000027 2. Examine the recycler.
For example, for tape VSN 000029, use the following command: sky# tplabel -vsn 000029 -old 000029 at.000029 When this VSN 000029 is relabeled, you regain 100 percent of the space on that VSN. If the media had been a magneto-optical disk, you would have used the odlabel(1M) command. For more information on the odlabel(1M) command, see the odlabel(1M) man page. ▼ To Recycle partially full VSNs The VSNs for which a partially full status is reported can also be recycled. 1. Examine the recycler.
The server’s recycler.log file indicates that VSN 000025 is 6 percent free, which is the same percentage that was reported in the client’s recycler.log file. The server is not aware of the client’s archive images, so it reports that all of the remaining 94 percent is consumed by obsolete archive images. CODE EXAMPLE 7-26 The recycler.
6. When archiving is complete, issue the sam-recycler(1M) command to rerun the recycler on the client. zeke# sam-recycler -dvx This ensures that all active files have been rearchived. 7. If the Count, Bytes, and Use field values are all 0 (zero), use the tplabel(1M) or odlabel(1M) command to relabel the VSN from the server. For example, for tape VSN 000025, use the following command: sky# tplabel -vsn 000025 -old 000025 at.000025 This command relabels the VSN and destroys all data on it.
2. Analyze the recycler log file for recycling candidates. Toward the end of the recycler.log file is a Status column. VSNs with the following types of status entries in the client log file are candidates for recycling: ■ no-data VSN. To recycle a no-data VSN, see “To Recycle no-data VSNs” on page 205. ■ partially full. To recycle a partially full VSN, see “To Recycle partially full VSNs” on page 207.
CHAPTER 8 Advanced Topics This chapter discusses advanced topics that are beyond the scope of basic system administration and usage. This chapter contains the following sections.
For tape archiving and staging to continue after failover, tape drives must be visible to all nodes in a cluster on which HA-SAM is running, but they should not be configured as Sun StorageTek SAM shared drives. HA-SAM also supports disk archiving with disk archives visible to all nodes in a cluster. HA-SAM depends on the Sun StorageTek QFS Sun Cluster agent and assumes that the Sun StorageTek QFS file systems are mounted and managed by the Sun StorageTek QFS agent.
■ Within the HA-SAM environment, the nosam mount option must be specified for any non-HA-SAM Sun StorageTek QFS file systems. ■ The HA-SAM resource, QFS file systems, and HAStoragePlus file systems must all be configured within the same resource group. A separate Sun Cluster resource group must be created for non-HA-SAM file systems. ■ When using the SUNW.hasam resource type, you cannot specify the bg mount option in the /etc/vfstab file. ■ Fibre tape drives are required.
Configuration Instructions Before configuring HA-SAM, you must configure the following extension properties using the Sun Cluster scrgadm command: ■ QFSName - supply a comma separated list of Shared QFS family set names ■ CatalogFileSystem - Assign a cluster HAStoragePlus file system specified in /etc/vfstab Note – See the Sun Cluster administration guide for more details on using the scrgadm command.
b. Verify that the output shows symbolic links similar to the following example. lrwxrwxrwx 1 root other 19 Sep 30 11:05 /var/opt/SUNWsamfs/catalog -> /sam_shared/catalog lrwxrwxrwx 1 root other 18 Sep 30 11:05 /var/opt/SUNWsamfs/stager -> /sam_shared/stager If the symbolic links exist, proceed to “To Configure Sun StorageTek SAM in a Sun Cluster Environment” on page 215. If the links do not exist, proceed to Step c. c. Copy any existing Sun StorageTek SAM catalog information to a temporary location. d.
2. Create and configure the SUNW.qfs resource. # scrgadm -a -g SAM-HA -t SUNW.qfs -j qfs-res \ -x QFSFileSystem=/global/qfs1,/global/qfs2 3. Create and configure a Sun StorageTek SAM shared resource. # scrgadm -a -j sam-hastp -g SAM-HA -t SUNW.HAStoragePlus \ -x FilesystemMountPoints=/sam_shared -x AffinityOn=TRUE 4. Create the HA-SAM resource type. # scrgadm -a -t SUNW.hasam -f /opt/SUNWsamfs/sc/etc/SUNW.hasam 5. Create and configure the SUNW.hasam resource. # scrgadm -a -g SAM-HA -t SUNW.
Using the samd hastop Command The samd command has an option that is specifically for use with HA-SAM. The samd hastop command stops the archiver and stager daemons before stopping sam-amld and its children. The samd hastop command must not be used by an administrator in either a stand-alone or shared Sun StorageTek SAM environment. In addition, the normal samd stop command must not be used on nodes under HA-SAM control.
CODE EXAMPLE 8-1 shows the mcf file. CODE EXAMPLE 8-1 Example mcf File /dev/samst/c1t5u0 /dev/samst/c1t4u0 /dev/samst/c1t6u0 40 41 42 hp mo mo hp40 hp40 hp40 - etc/opt/SUNWsamfs/hp40_cat CODE EXAMPLE 8-2 shows the /var/opt/SUNWsamfs/devlog file. CODE EXAMPLE 8-2 The devlog File # pwd /var/opt/SUNWsamfs/devlog # ls 40 41 42 43 # Device 43 is the historian.
Enabling the Device Log You can enable the device log in one of two ways, as described in the following subsections: ■ “To Enable the Device Log By Using the samset(1M) Command” on page 219 ■ “To Enable the Device Log by Editing the defaults.conf File” on page 219 ▼ To Enable the Device Log By Using the samset(1M) Command ● Use the samset(1M) command. For example: # samset devlog eq event For eq, specify the equipment ordinal of the device for which you want to log messages.
5. Use the samd(1M) config command to propagate the defaults.conf file changes. # samd config Using Removable Media Files You can use the request(1) command to manually create, write, and read files that do not use the disk cache for buffering the data. Files created in this manner are called removable media files. Note – The request(1) command bypasses the typical functions of the archiver.
▼ To Create a Removable Media or Volume Overflow File 1. Use the tplabel(1M) or odlabel(1M) command to label a tape or magnetooptical cartridge, respectively. For information on these commands, see their respective man pages. 2. Use the request(1) command. At a minimum, use the following options: request -m media-type -v vsn [vsn/vsn ...] [-l vsn-file] input-file TABLE 8-1 Arguments for the request(1) Command Argument Meaning media-type The media type of the removable media cartridge.
Using Segmented Files The Sun StorageTek SAM environment supports segmented files. Segmenting files improves tape storage retrieval speed, access, and manageability for very large files. A segmented file can be larger than the physical disk cache. It is possible for only part of a segmented file to reside on the disk cache at any one time. The segment(1) command enables you to specify the segment size. You cannot set a segment size that is smaller than the current file size.
directive, this file is archived to two drives in parallel. Segments 1, 3, 5, 7, and 9 are archived using the first drive, and segments 2, 4, 6, 8, and 10 are archived using the second drive. Only segments that have been modified are archived. Up to four archive copies can be made for each segment. Sun StorageTek SAM also supports volume overflow for segments. Note – The index of a segmented file contains no user data. It is considered metadata and is assigned to the file system archive set.
▼ To Enable SEF Reporting 1. Become superuser. 2. Use the mkdir(1) command to create the SEF directory. For example: # mkdir /var/opt/SUNWsamfs/sef 3. Use the touch(1) command to create the log file. You can enable SEF reporting any time after installation by creating the sefdata log file. Initially, the SEF log file must be empty. The following command shows the SEF log file being created in the default location. # touch /var/opt/SUNWsamfs/sef/sefdata 4.
■ The -d option. The -d option generates additional device information. It writes an additional header line that contains the equipment ordinal and path name to the device for each record. This makes it easier to search for and to locate SEF records that pertain to a specific device. ■ The -v option or the -t option. The -v option generates information in verbose mode. It appends information regarding the equipment ordinal, page code, and VSN to each line of a record.
CODE EXAMPLE 8-3 sef.output Contents (Continued) PAGE CODE 3 param code control 00h 74h 01h 74h 02h 74h 03h 74h 04h 74h 05h 74h 06h 74h PAGE CODE 6 param code control 00h 74h param value 0x0 0x0 0x0 0x0 0x0 0x140 0x0 param value 0x0 Record no. 2 Mon Mar 26 11:30:06 2001 STK 9840 Eq no.
CODE EXAMPLE 8-3 sef.output Contents (Continued) Record no. 3 Mon Mar 26 11:30:23 2001 STK 9840 Eq no. 32 Dev name /dev/rmt/1cbn PAGE CODE 2 param code control param value 00h 74h 0x0 01h 74h 0x0 02h 74h 0x0 03h 74h 0x0 04h 74h 0x0 05h 74h 0x18400f0 06h 74h 0x0 PAGE CODE 3 param code control 00h 74h 01h 74h 02h 74h 03h 74h 04h 74h 05h 74h 06h 74h PAGE CODE 6 param code control 00h 74h 1.25 VSN 002981 param value 0x0 0x0 0x0 0x0 0x0 0x1e0 0x0 param value 0x0 . . .
SEF sysevent Functionality In addition to using the SEF log file, you can use the Solaris sysevent feature to obtain tape drive SCSI log sense error counter pages 2 and 3 for media analysis. By default, the SEF sysevent feature is enabled and set to poll once before unload. The SEF sysevent behavior is controlled by defaults.conf and samset. In the defaults.conf file, the sef parameter can be used to enable SEF sysevent feature by equipment ordinal, or to specify the log sense polling frequency.
APPENDIX A Basic Operations for Libraries With Vendor-Specific Operational Procedures You can include libraries from many different manufacturers in a Sun StorageTek SAM environment. For most libraries, you should use the operational procedures described in “Using Automated Libraries and Manually Loaded Drives” on page 11. Some libraries, however, have vendor-specific operational procedures, and these are described in this chapter.
ADIC/Grau Automated Libraries If you have an ADIC/Grau automated library, use the procedures in this section for importing and exporting cartridges. These procedures differ from those described in “Using Automated Libraries and Manually Loaded Drives” on page 11. Because you use vendor-supplied utilities to physically add and remove cartridges in the ADIC/Grau automated library, the Sun StorageTek SAM interface (import(1M), samexport(1M), and File System Manager) affects only the library catalog.
▼ To Export a Cartridge To export a cartridge, perform the following steps. 1. Use the Sun StorageTek SAM samexport(1M) command to remove the entry from the library catalog. Use this command in one of the following formats: samexport eq:slot samexport media-type.vsn TABLE A-2 Arguments for the samexport(1M) Command Argument Meaning eq The equipment ordinal of the device being addressed as defined in the mcf file.
▼ To Import a Cartridge To import a cartridge, perform the following steps. 1. Use Fujitsu commands to physically move the cartridge into the library. 2. Use the Sun StorageTek SAM import(1M) command to update the library catalog. Use this command in the following format: import –v volser eq ▼ TABLE A-3 Arguments for the import(1M) Command Argument Meaning volser The volser to be added.
The samexport(1M) command updates the library catalog as each VSN is exported, and it moves the library catalog entry for each VSN from the Sun StorageTek SAM library catalog to the Sun StorageTek SAM historian. 2. Use Fujitsu commands to physically move the cartridge out of the library. IBM 3584 UltraScalable Tape Libraries The IBM 3584 UltraScalable Tape Libraries are supported in the Sun StorageTek SAM environments.
When a cartridge is exported from a partitioned library, only the logical library from which it was exported can access that drawer slot. If the cartridge is removed and reinserted manually, it is accessible to any and all logical partitions. ▼ To Remove a Cartridge To remove a cartridge from a partitioned library, perform the following steps. 1. Open the door. 2. Remove the cartridges. 3. Close the door. 4. Wait for the door to lock and then unlock. 5. Open the door. 6. Replace the cartridges. 7.
2. Close the door. The library locks the door and moves the media into the storage area. You can import only 100 volumes at one time. If the library is configured with access=private, this is the last step you need to perform. The library informs the daemon as the media is moved, and the media is added to the catalog. 3. If the library is configured with access=shared, issue the import(1M) command to add the media to the catalog. ▼ To Export a Cartridge 1. Use the export(1M) command to export cartridges.
▼ To Import Tapes To import tapes, follow these steps. 1. Open the door of the automated library by pushing the open/close button on the front panel of the automated library. 2. Load the cartridges into the mailbox slots. 3. Push the open/close button on the front panel of the automated library and manually close the door to the mailbox. The automated library checks the mailbox slots for the cartridge barcodes after the door is closed.
TABLE A-5 Arguments for the move(1M) Command Argument Meaning source-slot The number of the slot in which the cartridge currently resides. destination-slot The number of the slot into which the cartridge should be moved. eq The equipment ordinal of the device being addressed as defined in the mcf file. 2. Push the open/close button on the front panel of the automated library. The door opens. 3. Remove the cartridge from the mailbox slot. 4.
4. Issue the samexport(1M) command to enable the Sun StorageTek SAM system to recognize the exported cartridge. Use this command in the following format: samexport eq For eq, specify the equipment ordinal of the device being addressed as defined in the mcf file. You can also perform this step by using File System Manager. For more information, see File System Manager online help. ▼ To Move a Cartridge to a Different Slot To move a cartridge to a different slot, follow these steps. 1.
Sony Network Attached Automated Libraries If you have a Sony network attached automated library, use the procedures in this section for importing and exporting cartridges. These procedures differ from those described in “Using Automated Libraries and Manually Loaded Drives” on page 11.
▼ To Export a Cartridge To export a cartridge, perform the following steps. 1. Use the samexport(1M) command to remove the entry from the library catalog. Use this command in one of the following formats: samexport eq:slot samexport media-type.vsn TABLE A-8 Arguments for the samexport(1M) Command Argument Meaning eq The equipment ordinal of the device being addressed as defined in the mcf file. slot The number of a storage slot in an automated library as recognized in the library catalog.
StorageTek 9714 and the StorageTek 9710. The StorageTek 9730 uses a mailslot. In StorageTek documentation, the mailbox and mailbox slot are often referred to as the cartridge access port (CAP). When importing and exporting cartridges from an ACSLS-attached automated library, be aware of the following: ■ When you are importing cartridges, Sun StorageTek SAM commands affect only the library catalog. The import(1M) command does not insert cartridges into the automated library physically.
▼ To Export Tapes Using a Mailbox You can export tape cartridges by slot or by VSN. ● Use the samexport(1M) command in one of the following formats: samexport [-f] eq:slot samexport [-f] media-type.vsn TABLE A-10 Arguments for the samexport(1M) Command Argument Meaning -f Specification for the Sun StorageTek SAM system to put the volume in the cartridge access port (CAP) and to update the catalog accordingly. eq The equipment ordinal of the device being addressed as defined in the mcf file.
Glossary A addressable storage The storage space encompassing online, nearline, offsite, and offline storage that is user-referenced through a Sun StorageTek QFS or Sun StorageTek SAM file system. archive media The media to which an archive file is written. Archive media can be removable tape or magneto-optical cartridges in a library. In addition, archive media can be a mount point on another system.
block allocation map block size A bitmap representing each available block of storage on a disk and indicating whether the block is in use or free. See DAU. C cartridge catalog A physical entity that contains media for recording data, such as a tape or optical disk. Sometimes referred to as a piece of media, a volume, or the medium. A record of the VSNs in an automated library. There is one catalog for each automated library and, at a site, there is one historian for all automated libraries.
direct I/O directory disk allocation unit An attribute used for large block-aligned sequential I/O. The setfa(1) command’s –D option is the direct I/O option. It sets the direct I/O attribute for a file or directory. If applied to a directory, the direct I/O attribute is inherited. A file data structure that points to other files and directories within the file system. See DAU.
FDDI Fibre Channel file system file-system-specific directives FTP Fiber-distributed data interface (FDDI) is a standard for data transmission in a local area network that can extend in range up to 200 km (124 miles). The FDDI protocol is based on the token ring protocol. The ANSI standard that specifies high-speed serial communication between devices. Fibre Channel is used as one of the bus architectures in SCSI-3. A hierarchical collection of files and directories.
I indirect block A disk block that contains a list of storage blocks. File systems have up to three levels of indirect blocks. A first-level indirect block contains a list of blocks used for data storage. A second-level indirect block contains a list of first-level indirect blocks. A third-level indirect block contains a list of second-level indirect blocks. inode Index node. A data structure used by the file system to describe a file.
M mcf media media recycling metadata metadata device mirror writing mount point multireader file system Master configuration file. The file that is read at initialization time that defines the relationships between the devices (the topology) in a file system environment. Tape or optical disk cartridges. The process of recycling or reusing archive media with few active files. Data about data. Metadata is the index information used to locate the exact data position of a file on a disk.
network attached automated library A library, such as those from StorageTek, ADIC/Grau, IBM, or Sony, that is controlled using a software package supplied by the vendor. The Sun StorageTek SAM file system interfaces with the vendor software using a Sun StorageTek SAM media changer daemon designed specifically for the automated library. NFS Network file system. A file system distributed by Sun that provides transparent access to remote file systems on heterogeneous networks. NIS The Sun OS 4.
R RAID recycler Redundant array of independent disks. A disk technology that uses several independent disks to reliably store files. It can protect against data loss from a single disk failure, can provide a fault-tolerant disk environment, and can provide higher throughput than individual disks. A Sun StorageTek SAM utility that reclaims space on cartridges that is occupied by expired archive copies.
SAM-QFS samfsrestore SCSI shared hosts file Small Computer System Interface soft limit staging storage family set A configuration that combines the Sun StorageTek SAM software with the Sun StorageTek QFS file system. SAM-QFS offers a high-speed, standard UNIX file system interface to users and administrators in conjunction with the storage and archive management utilities. It uses many of the commands available in the Sun StorageTek SAM command set as well as standard UNIX file system commands.
Sun SAM-Remote client Sun SAM-Remote server superblock A Sun StorageTek SAM system with a client daemon that contains a number of pseudodevices, and can also have its own library devices. The client depends on a Sun SAM-Remote server for archive media for one or more archive copies. Both a full-capacity Sun StorageTek SAM storage management server and a Sun SAM-Remote server daemon that defines libraries to be shared among Sun SAM-Remote clients.
VSN Volume serial name. In the context of archiving to removable media cartridges, the VSN is a logical identifier for magnetic tape and optical disk that is written in the volume label. In the context of archiving to disk cache, this is the unique name for the disk archive set. W WORM Write once read many. A storage classification for media that can be written only once but read many times.
254 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
Index A -access archiver directive, 63 ACSAPI interface, 3 ACSLS-attached library, 240 ADIC/Grau automated library operations, 230 age_priority preview.
overview, 1 -ovflmin parameter, 41 preventing archiving, 63 preview queue, 100, 140 queue time notification, 43 renaming the event notification script, 57 -reserve parameter, 39 reserved VSNs, 83 reserving volumes, 81 role in staging, 139 scanned archiving, 38 scheduling archive requests, 40 scheduling archiving, 86 segmented files, 222 setting automatic unarchiving, 72 setting priorities, 85 setting the archive age, 71 setting the archiver buffer size, 53, 74 -sort and -rsort parameters, 39 specifying a fi
audit automated library, 18 volume, 17 auditslot(1M) command, 17, 23 auto-cleaning, 22 automated library ADIC/Grau, 230 auditing, 18 catalog, 26 cleaning, 19 daemons, 3 defined, 11 direct attached, 3 Fujitsu LMF, 231 historian, 27 IBM 3494, 234 IBM 3584, 233 importing and exporting, 27 network attached, 3 operation, 26 SCSI attached, see automated library, direct attached Sony 8400 PetaSite, 235 Sony network attached, 239 specifying recycling parameters, 153 Sun StorageTek ACSLS-attached, 240 turning off, 1
release priority, 2 diskvols.
load_notify.sh script, 30 loading media, 14 manually loaded drive, 31 -lock archiver directive, 77 log files archiver, 44, 56 backing up, 57, 100 device logging, 217 enabling device logging, 219 managing the SEF log file, 227 recycler, 193, 197, 205, 210 recycler error messages, 158, 162 releaser, 126 SEF log file, 223 stager, 136 log sense pages, 223 log_rotate.
directives, 141 hlwm_ priority directive, 143 hwm_ priority directive, 143 lhwm_ priority directive, 143 lwm_ priority directive, 142 setting priority, 145 vsn_priority directive, 141 -priority archiver directive, 85 Q queue time notification for archiving, 43 -queue_time_limit parameter, 43 R rearch_no_release releaser directive, 128 rearchiving, defined, 150 -recycle_dataquantity archiver directive, 161 -recycle_hwm archiver directive, 190 -recycle_ignore archiver directive, 160, 161, 163, 190 -recycle_
min_residence_age directive, 126 no_release directive, 125 rearch_no_release directive, 128 weight_age directive, 123 weight_age_access directive, 123 weight_age_modify directive, 123 weight_age_residence directive, 123 weight_size directive, 124 removable media files, 220 starting, 12 stopping, 13 request files, see removable media files request(1) command, 151, 220 arguments, 221 -reserve archiver directive, 81 robot, see automated library S sam_release(3) library routines, 121 sam-amld daemon, 140 sam-a
options, 224 segment(1) command, 222 segmented files, 222 archiving, 222 showqueue(1M) command, 37 showrev(1M) command, 173 software documentation, xxii Sony 8400 PetaSite automated library operation, 235 Sony network attached automated library operations, 239 ssum -e, data verification, 46 -stage archiver directive, 68 stager archive role in staging, 139 defined, 133 directives, 133 enforcing stager requests, 145 error processing, 2 log file fields, 138 logging activities, 136 overview, 2, 133 partial stag
wm_priority preview.
264 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
