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. [. . . ] Back up the new host system using your normal system backup procedure. Create an amass login on the new system. Use the amass login on the old host as an example. Change ownership of the newly copied AMASS database and journal directories and files to amass by entering the following path and command: # cd /usr/filesysdb # chown -R amass Step 5. Create the target entries on the new host if you want to relocate the /usr/amass directory to a different partition. Refer to see "AMASS Files" on page C-13. 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. Use the probe-scsi-all command to display the attached devices. 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. Running `make install' on kernel rem_drv vg. ***Error code 1 (ignored) rem_drv amass. 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. [. . . ] Create a physical volume for the specified device. In our example, we create volume group 03. Note This volume group is not the same as an AMASS "volume group" assignment. # vgcreate -s2 /dev/vg03 /dev/rdsk/c1d0s2 Step 3. Create a logical volume of 100 MB in volume group vg03. # lvcreate -L100 /dev/vg03 Step 4. Use the command and option shown in the following illustration to view the logical volumes on your system. [. . . ]