User manual QUANTUM AMASS FOR UNIX 5.6.1 ADDENDUM REV A

[. . . ] · · amassbackup / amassrestore fileprint 0 amassbackup / amassrestore 0 [Update to Managing the AMASS File System (6-00028-01), pages 3-9 through 3-11, and 3-19 through 3-23. ] The AMASS internal implementation of the "-d <device>" option for amassbackup and amassrestore has been changed for Solaris (as described in CR23036). Instead of using the default cpio archive file type, the "-H tar" archive file type is now used with cpio. This allows individual files of size 2 Gb or larger (i. e. , Large Files, ) to be processed. The cpio "-H tar" option is backward compatible with cpio archive files, so previous amassbackups residing on an external device can be read by amassrestore (which now uses "-H tar" with cpio). Made in the USA. [. . . ] At the command prompt, type: kill -15 process_id where process_id is the process ID you identified in step 2. 4 When you are ready to start the libio daemon again, change to the /usr/amass/ daemons directory. At the command prompt, type: . /libio_tape juke_number drive_number where juke_number is the number of the juke containing the drive and drive_number is the number of the drive. (For an optical drive, type . /libio_optical juke_number drive_number instead. ) 6 Repeat step 2 to verify that libio daemon for the affected drive has successfully started. At the command prompt, type: drivestat -a drive_number [juke_number] where drive_number is the number of the drive and juke_number is the number of the juke containing the drive. (If you do not specify a juke number, the system assumes juke 1. ) Note: Before restarting the libio daemon, you must reset any exported environment variables specified in the amass_start script. If you do not do this, when the libio daemon starts, it will use the default value for all environment variables. To export a variable, at the command prompt, type: variable_name=value export variable_name where variable name is the name of the environment variable and value is the value of the variable. Database Checking Performance [Update to Managing the AMASS File System (6-00028-01), page 4-55. ] 0 In AMASS for UNIX version 5. 6, the dbcheck command invokes a new preprocessor when validating the AMASS file system database for data integrity. FADS identifies the database records that require validation, and dbcheck validates only those records rather than the entire database. As a result, when New and Enhanced Features in AMASS 5. 6 4 AMASS for UNIX Version 5. 6. 1 Addendum Document 6-01238-03 Rev A April 2008 dbcheck is run regularly, the FADS preprocessor significantly increases the speed of database validation without affecting accuracy or data integrity. Running dbcheck with FADS 0 In AMASS 5. 6, the FADS preprocessor is used by default when running the dbcheck command. The dbcheck -a option is assumed even if it is not specified, and you must include the full database path and name in the arguments. For example, if the file system is not active: dbcheck -a /usr/filesysdb/filesv4 Or, if the file system is active: dbcheck -a -R /usr/filesysdb/filesv4 The first time dbcheck is run, FADS creates companion files that are used to track the database records that require validation. As a result, the first time dbcheck is run, the validation process will take as long as it did in previous versions of AMASS. The next time dbcheck is run, the companion files are used to determine which records require validation. Only those records that are new or have changed since the last dbcheck will be validated. This results in a significantly shorter time for the validation process. Setting up a dbcheck Cron Job To realize the full speed benefits of the FADS preprocessor, run dbcheck frequently. The more often dbcheck is run, the fewer the number of records that require validation each time, and the faster the validation process. each day, add the following line to the amass crontab file: 10 2 * * * /usr/amass/utils/dbcheck ­a ­R /usr/filesysdb/filesv4 0 Running dbcheck in Legacy Mode If desired, you can run dbcheck in legacy mode without using the FADS preprocessor. (When dbcheck is run in legacy mode, database validation takes significantly longer. ) To run dbcheck in legacy mode, use the following syntax: dbcheck -a -L database_path 0 where database_path is the full path and name of the AMASS database to be validated. Support for Running Multiple Admin Requests0 [Update to Managing the AMASS File System (6-00028-01), pages 3-9, 3-61, and 3-158. ] With AMASS 5. 6, administrators can run multiple admin commands simultaneously. For example, with the enhanced support, an administrator can run any of the following command combinations: · · driveclean + amassbackup driveclean + driveclean New and Enhanced Features in AMASS 5. 6 5 AMASS for UNIX Version 5. 6. 1 Addendum Document 6-01238-03 Rev A April 2008 · · driveclean + volformat volformat + volformat Note: If an admin command uses a particular resource (such as a cleaning volume), a second command that requires the same resource will not start until the resource becomes available. While waiting for the required resource, the command prompt is unavailable. Updated Information for AMASS 5. 6 The following updates consist of changes to existing functionality that were previously documented in AMASS 5. 3: · · · · · · fileincache / fileonmedia healthcheck Resolving Check Drive Problems with Optical Media voldelete / volslot / volclean Removing Block Size and Compression Restrictions for Volume Groups Updated Clean Request Process 0 fileincache / fileonmedia 0 [Update to Managing the AMASS File System (6-00028-01), pages 3-79 and 4-57. ] For the -v option, the fileincache command now prints the resulting status to stdout, not stderr. [. . . ] When a drive cleaning request failed, the affected drive was taken offline. This means that multiple drive cleaning requests are queued and are completed without failing or causing the drive to go offline. Using the AMASS_CLN_INTERVAL Variable 0 The AMASS_CLN_INTERVAL environmental variable is new in AMASS 5. 6. Use this variable to specify how often tape drives are automatically cleaned. [. . . ]