User manual QUANTUM AMASS 5.3 INSTALLING REV A

[. . . ] Installing AMASS AMASS Version 5. 3 August 2002 6-00027-01 Rev A Trademark Notice ADIC, AMASS, CentraVision, DataMgr, DAS, FileServ, and VolServ are either trademarks or registered trademarks of Advanced Digital Information Corporation. All other product names and identifications are trademarks or registered trademarks of their respective owners. Copyright Notice © 1996-2002 ADIC® All rights reserved. No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the express written permission of: ADIC 11431 Willows Road, NE PO Box 97057 Redmond, WA 98073-9757 USA Phone: 425-881-8004 FAX: 425-881-2296 U. S. Government Rights Restricted Use, duplication, or disclosure of either the software or documentation is subject to restrictions set forth by the U. S. [. . . ] Refer to "Extracting Files from CD" on page 2-21 to complete the installation. Note If the installation fails, do not perform another backup before continuing the install. Step 6. Step 7. Run install_tests to verify the installation. For instructions, refer to "Test the Installation (All Platforms)" on page 2-43. 6-00027-01 Rev A Site-Specific Tasks 3-21 Installing AMASS Step 8. Perform a full backup of the AMASS database by entering the following command and arguments after the installation is successful and AMASS is running, This backup insures that any changes to the database tables are saved on the backup volume. # /usr/amass/bin/amassbackup -fv 3-22 Site-Specific Tasks 6-00027-01 Rev A 4 Troubleshoot Install Problems Installing AMASS NOTES 4-2 Troubleshoot Install Problems 6-00027-01 Rev A Installing AMASS makeall in tools Fails The installamass script fails and returns the message shown in the following illustration: chown amass amassmain chmod 4755 amassmain ~ *** Signal 10 make: Fatal error: Command failed for target `amassrecovery' . /makeamass: command `/usr/amass/tools/makeall' failed in /usr/amass/tools; please contact your vendor for assistance. Problem building the amass filesystem. . . please contact your vendor for assistance. Script done, file is typescript. Solution Make sure that you have enough disk space available, particularly in the /tmp directory. 6-00027-01 Rev A Troubleshoot Install Problems 4-3 Installing AMASS Unrecognized Device on Solaris Only Solaris only: If an "unrecognized" device is attached to a Solaris system with multiple SCSI controllers, Solaris does not see the bus and consequently does not build the appropriate device files, hence AMASS fails to install. Solution Step 1. Add the device node directory manually, for example, QLCG, isp@1, 10000. Install AMASS. 4-4 Troubleshoot Install Problems 6-00027-01 Rev A Installing AMASS NIS Issues The following table lists the problems and solutions for Network Information Service (NIS), the client/server administrative tool: Issue Password File Problem If your site uses NIS, the last entry in the /etc/passwd file must be an NIS entry. However, as part of the installation process, AMASS, creates a user named "amass" that is appended to the end of this file. Consequently, the /etc/passwd file is now invalid. Solution Use a text editor, for example vi, to edit the /etc/passwd file and move the amass entry up at least one row to allow the NIS entry to be the last entry in the file. Ownership Files On machines running NIS, Add amass as a valid AMASS incorrectly reads the user to the local ownership files from the password file. local password file instead of from the network. 6-00027-01 Rev A Troubleshoot Install Problems 4-5 Installing AMASS Solaris Only - Cannot Build Device Drivers Solaris only: The installamass script fails trying to build AMASS device drivers and returns the messages shown in the following illustration. You may also receive these messages after running the deinstallamass script. Cannot get major number for: amass ***Error code 1 (ignored) ~ Problem with making new kernel. Please correct this and re-run. Solution Reboot and run the installamass script again. 4-6 Troubleshoot Install Problems 6-00027-01 Rev A Installing AMASS Insufficient Space in File System hp Tru64 UNIX only: If your root file system has insufficient space, the installamass script issues a warning as shown in the following illustration: Warning: Your root directory has insufficient space (xxxxxx blocks remaining) to hold the new kernel. AMASS will leave this new kernel in "/sys/HOSTNAME/vmunix" (xxxx KB). After resolving the disk space conflict, manually copy "/sys/HOSTNAME/vmunix" to your root file system. Solution AMASS will leave the new kernel in the /sys/HOSTNAME/vmunix file. Replace your "old" kernel with the new AMASS-created kernel by manually moving the new kernel to root (/). Reboot the Tru64 UNIX machine. Step 3. 6-00027-01 Rev A Troubleshoot Install Problems 4-7 Installing AMASS Messages Generated by AMASS AMASS generates the following types of messages as described in the following table: Message Operator Interactive Description Because most AMASS commands and AMASS utilities are operator interactive, they use standard in (stdin) and standard error (stderr). Lists are written to standard out (stdout), which you can redirect to either a file or a printer. Technical support-specific AMASS message appear under the /usr/amass/logs directory. These messages are neither intended for customers nor are they documented for customers. Customer-specific AMASS daemon, database, kernel, and operation messages appear in the /usr/amass/logs/parms file and are sent to the system log file for viewing by the AMASS system administrator. (They are sent to the /usr/amass/logs/tac file as well. ) These system log messages help you to: assess system operation, resolve problems, check system health, and monitor performance. [. . . ] If you need to reinstall AMASS, while using the installamass script, you must deinstall the AAPjuke driver and then a few questions later in the script reinstall it. F-4 Fibre Channel Support 6-00027-01 Rev A Installing AMASS NOTES 6-00027-01 Rev A Fibre Channel Support F-5 Installing AMASS F-6 Fibre Channel Support 6-00027-01 Rev A G Partition Cache on HP-UX Installing AMASS NOTES G-2 Partition Cache on HP-UX 6-00027-01 Rev A Installing AMASS Partitioning the HP-UX Cache The cache for HP-UX can be partitioned in one of the following ways: · · · Use Separate Disk Use Fixed Partition Use Logical Volume Manager Following is a description of each method. Use Separate Disk The simplest method is to use a dedicated disk drive. The device files for the disk drive look similar to the following example. Logical unit number is 2 (c2) Character device file = /dev/rdsk/c2d0s2 Block device file = /dev/dsk/c2d0s2 Specifies partition number 2 (s2) or the entire disk. Drawback The drawback to this method is that you must dedicate the entire disk as the cache. This may be more disk space than your site requires. 6-00027-01 Rev A Partition Cache on HP-UX G-3 Installing AMASS Use Fixed Partition This method uses one of the predefined hard partitions on the disk. They are called hard partitions because the sizes of the various partitions are fixed and cannot be changed. [. . . ]