EZADSM Package for OS/2 -- ezreadme.txt Updated: March 24, 1995 March 2, 1995 ======================================================================= Quick Start ======================================================================= The EZADSM package is available as a self-extracting zip file named ezadsm.exe. When extracted, EZADSM will take up about 6.8MB of disk space on your hard drive. To get started, place ezadsm.exe in its own directory and run it as: ezadsm -d Note that the -d is required so that the original directory structure will be restored. The following sequence of steps can be used to get started quickly: c: md adsm cd adsm copy or download ezadsm.exe into c:\adsm ezadsm -d del ezadsm.exe The following directory hierarchy will exist: c:\adsm\ezadsm c:\adsm\adsmtour You can now cd into c:\adsm\ezadsm and run your choice of adsmutil.exe adsminst.exe clientfs.exe The ADSM tour is available from the adsmutil.exe program. Please see the following sections for more detailed information. ======================================================================= Contents ======================================================================= Introduction Requirements Package Contents Unpacking 1. adsminst.exe -- The ADSM installer. 2. clientfs.exe -- The ADSM file-server-based client installer 3. adsmutil.exe -- ADSM utilities Known Problems and Limitations How to Report Bugs and Usability Suggestions Change History ======================================================================= Introduction ======================================================================= EZADSM is a package that is being developed to simplify the installation and configuration of ADSM clients and servers. EZADSM is nearing completion on OS/2, although there are still several areas that need work. A short list of limitations will be given below. The package is being provided to IBM customers on both Compuserve (go ibmstorage) and the internet (ftp index.storsys.ibm.com) so that feedback can be obtained and rolled back into the EZADSM package before releasing it at some point in the future. ======================================================================= Special Requirements ======================================================================= The programs in this package run on OS/2 v2.1 or later. The ADSM utilities program does not require any software other than what is included in this package. The two easy installation programs, adsminst.exe and clientfs.exe, require access to the GA version of the ADSM client distribution (4 diskettes) and the GA version of the ADSM server distribution (3 diskettes). You may purchase the ADSM GA packages from your IBM representative or software distributor. For more information on ADSM, please call: 1-800-442-6773 ======================================================================= Package Contents ======================================================================= The EZADSM package consists of three independent programs: 1. adsminst.exe -- The ADSM installer 2. clientfs.exe -- The ADSM file-server-based client installer 3. adsmutil.exe -- ADSM utilities ======================================================================= Unpacking ======================================================================= EZADSM is distributed as a self-extracting zip file. If you receive the file EZADSM.exe electronically, be sure to download it in binary and place it in its own directory. If you receive it on diskette, copy it into its own directory. Once ezadsm.exe is in its own directory, issue the command: ezadsm -d IMPORTANT -- you must include -d as an argument so that the self-extracting zip file will create the required directory structure. ezadsm will create two directories under the current directory as follows: \ezadsm \adsmtour ezadsm will unzip itself into the following files: \ezadsm\adsminst.exe -- ADSM installer \ezadsm\adsminst.hlp -- ADSM installer help \ezadsm\adsmutil.exe -- ADSM utilities \ezadsm\adsmutil.hlp -- ADSM utilities help \ezadsm\clientfs.exe -- ADSM file-system-based client installer \ezadsm\test.cfg -- A sample configuration file for use with clientfs.exe \ezadsm\*.inf -- ADSM online books and information \adsmtour\*.* -- ADSM demo files You can run the programs by changing directory (cd'ing) into the ezadsm subdirectory and by then entering the name of the .exe file. For example, to run the ADSM utility program enter the following in an OS/2 window: cd ezadsm adsminst If you see a message that says: Error -- Failed to load help Manager, make sure that you are running the executable from the same directory that the executable and help file are located. ======================================================================= 1. adsminst.exe -- The ADSM installer. ======================================================================= The installer provides quick install, custom install, update, and deinstall options for ADSM Servers and Clients. Features: All of the installation options allow you to install ADSM from either diskettes or a file server. Quick install -- installs an ADSM server, an ADSM administrative client, and an ADSM backup-archive client all on the same machine. The quick install procedure creates an ADSM database and recovery log, along with backup and archive storage volumes. The local administrative and backup-archive clients are automatically registered with the server. The storage volumes are defined to the server. Communications are detected (TCP/IP and named pipe detection/configuration is currently supported) and both server and client options files are created. Quick install will also perform an installation verification test (IVT) to ensure that ADSM is properly configured. After running quick install (and rebooting), a person may begin interacting with the ADSM server using the server command line console and/or the local administrative client and can begin backing up and restoring data using the ADSM backup-archive client. Note -- Quick install is the recommended method of installing an ADSM server. Custom install -- allows you to modify database, recovery log, and storage volume sizes. It allows you to selectively install components and to specify different locations for individual components. The custom install treats the Server and Clients separately and will not perform an installation verification test. Note -- Custom install should only be used by experienced system administrators. Update -- allows you to update existing ADSM components. De-install -- allows you to remove ADSM components from your system. ======================================================================= 2. clientfs.exe -- The ADSM file-server-based client installer ======================================================================= ADSM will typically be installed in a computing environment that includes one or more network file servers. The ADSM file-server-based client installer can be used to simplify the installation of any number of ADSM clients. For example, the scenario depicted by the following diagram may exist. +----------------+ +------------------+ +------------------+ | ADSM Server 1 | | Node Kirk | | Node Spock | | OS: OS/2 | | OS/2 | | OS/2 | | TCP Address: | | | | | | 9.117.4.1 | | mount x: fs1:d:\ | | mount x: fs1:d:\ | +----------------+ +------------------+ +------------------+ | | | +================================================================== | | +---------------+ | |File Server | d:\bin\clientfs.exe | | FS1 | d:\bin\setup1.cmd | | | d:\bin\config1.dsm |-| d: | d:\bin\setup2.cmd | | | d:\bin\config2.dsm | | nfs export d: | d:\adsm\server\(ADSM server distribution files) | | | d:\adsm\client\(ADSM client distribution files) | +---------------+ | +================================================================== | | | +----------------+ +-----------------+ +-----------------+ | ADSM Server #2 | | Node Picard | | Node Rieker | | OS: AIX | | OS/2 | | OS/2 | | TCP Address: | | | | | | 9.117.4.2 | | mount x: fs1:d\ | | mount x: fs1:d\ | +----------------+ +-----------------+ +-----------------+ Here there are 2 ADSM Servers (1 on OS/2 and 1 on AIX), 1 file server, and 50 new client nodes (4 of which are shown). The file server is exporting its drive d:. Each client node has mounted the file server's d: drive as drive x: (typically at system bootup). Furthermore, each client node has x:\bin in its path statement. As the ADSM administrator you know you have 50 new workstations that need to be setup to work with your existing ADSM servers. To balance the workload between ADSM servers you would like the first 25 nodes (including Kirk and Spock) to use ADSM Server #1 and the second 25 nodes (including Picard and Reiker) to use ADSM Server #2. You would like the ADSM clients to be installed on each node, but you don't want to explain TCP/IP and ADSM option file details to everyone. Instead, you let the first 25 people know that they should enter the command SETUP1 and you let the second 25 people know they should enter the command SETUP2. The only choice each client node will have to make is where on one of their hard drives they would like to install ADSM. Clientfs (which is invoked by setup1.cmd and setup2.cmd) even simplifies that choice by only displaying the drives that have enough free space to install the ADSM clients. Contents of Setup1.cmd and Setup2.cmd ===================================== setup1.cmd contains the single line: clientfs x:\bin\config1.dsm setup2.cmd contains the single line: clientfs x:\bin\config2.dsm Note that this simply runs clientfs.exe while providing a configuration file as a parameter. Contents of config1.dsm and config2.dsm ======================================= config1.cmd contains the following lines: adsm_admin_contact="Your name, Your phone number, your email address" update_if_client_exists=true commmethod=tcpip tcpserveraddress=9.117.4.1 tcpport=1500 source_path=x:\adsm\client config2.cmd contains the following lines: adsm_admin_contact="Your name, Your phone number, your email address" update_if_client_exists=true commmethod=tcpip tcpserveraddress=9.117.4.2 tcpport=1500 source_path=x:\adsm\client Note the meaning of the current set of options: adsm_admin_contact -- information that will appear on any error messages that are displayed so that people know who to contact in case of any problems. Whatever information you enter for this option must be enclosed in double quotes ("). update_if_client_exists -- true if you as the administrator want each node's copy of ADSM to be automatically updated each time this program is run. commmethod -- communication method to use to establish a connection with the adsm server. (Although ADSM supports many protocols, clientfs is currently only supporting tcpip and named pipes. This option will be updated to support the full set of ADSM communication protocols (TCP/IP, IPX/SPX, NetBios, Named Pipes, SNA ) soon. tcpserveraddress -- the tcp/ip address of the ADSM server the node will connect to. tcpport -- the tcp port number the server will be listening on (matches the value in the particular ADSM server's options file or 1500 by default). source_path -- specifies the location of the ADSM client distribution files. Soon there will be a utility to setup a file server distribution area, but in the mean time, an administrator can simply create a directory and then copy the contents of all 4 of the ADSM client disks into this single directory. Note -- more options will be coming soon. For example, it will be possible to install an ADSM client on the file server and have clientfs setup an option file, environment variables, and path statements to point to the file server copy. Scheduling option will also be provided as well as more communications options. All suggestions are welcome. ======================================================================= 3. adsmutil.exe -- ADSM utilities ======================================================================= Currently the ADSM utilities provides a Graphical User Interface (GUI) based server options file editor, storage volume formatter, SCSI device detector, sequential medial labeller, and an ADSM server diagnostics utility. Soon it will provide a GUI based version of the ADSM client option file editor. The utilities program provides a convienient way to access all ADSM documentation on-line. It also provides access to an on-line version of common ADSM questions and answers. The utilities program also provides a convienient way to access the ADSM tour which provides an interactive graphical overview of ADSM. As a sneak preview, the Motif (Unix) version of adsmutil also provides an ADSM server console as it's main window which allows server command recall/editing as well as a scrollable server output area. The utilities and on-line material are available through adsmutil/6000's main menu. The Motif version is in progress, but is not yet ready for review. ======================================================================= Known problems and limitations ======================================================================= 1. If loading from floppy diskettes, quick install takes a long time to load the progress bar (5 minutes or more) on slow machines with less than 16MB of memory. The problem has been seen on slow 386 and notebook computers. This problem does not appear on fast machines with 16MB or more or even on slow machines that install from a file server instead of the diskettes. It appears that there is contention between the swapper and the floppy drive -- and the floppy drive looses... The memory footprint of the installer is being reduced along with other size/speed optimizations in order to fix this problem. 2. There is currently a problem that will show up if a floppy drive is installed as something other than drive A: or B: 3. A problem may occur if a lan server drive becomes disconnected (ie if a lan server goes down, but your drives are still connected). -- Certain dialogs will come up slowly as they are having a hard time detecting drive information for those drives and an GetFSInfo failed error message will be displayed. Note -- these issues are being worked on and will be taken care of in a future release. Please report any other problems that you come across. ======================================================================= How to report Bugs and Usability suggestions ======================================================================= Please send all comments/feedback to: Compuserve: 73373,1422 Internet: ecollins@vnet.ibm.com IBM: ecollins at tucvm3 ======================================================================= Change History ======================================================================= March 24, 1995 ADSMUTIL -- No changes CLIENTFS -- No changes ADSMINST -- As follows 1. FIXED a problem with the custom install client option. The ADSM client custom install sequence was not being properly completed. Because of this, no client option file was created and the client would not be usable after custom installation. 2. UPDATED to allow PTF installation as well as GA (PLA) installation of both the client and the server (PTF 7 has been tested). Note that to properly install the level 7 PTF of the ADSM server (IP20255), you must first install IP20151 or have installed the shrink-wrapped server package (also known as the PLA). ======================================================================= End of Readme =======================================================================