StorageWorks_Desktop_Backup/Archiver__________ Installation Guide Order Number: AA-Q6UEB-TH Revision Information: This is an updated manual. Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, June 1994, Second Printing, October, 1995 The information is this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19 or FAR 52.227-14, Alt. III, as applicable. © Digital Equipment Corporation 1994, 1995. All Rights Reserved. Printed in the U.S.A. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, DECwindows, EtherWORKS, PATHWORKS, Rdb/VMS, StorageWorks, OpenVMS, ThinWire, ULTRIX, VAX, VAXDOCUMENT, VMS, VT, VXT, and the DIGITAL logo. The following are third-party trademarks: MS-DOS and Microsoft are registered trademarks of Microsoft Corporation. Windows and Windows NT are trademarks of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. AppleTalk and Macintosh are registered trademarks of Apple Computer, Inc. S2340 All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents About This Guide......................................... ix 1 Product Overview Overview..................................... 1-1 Product Information...................... 1-1 Desktop Backup Server.................... 1-1 Desktop Backup Client.................... 1-1 MS-DOS Client............................ 1-2 Windows Client........................... 1-2 Macintosh Client......................... 1-3 2 Installation Overview Overview..................................... 2-1 Definitions of Client and Server......... 2-1 Definition of the Backup Manager Process.................................. 2-1 In this Chapter.......................... 2-2 Pre-installation Guidelines for the Server... 2-2 Pre-installation Requirements for the MS-DOS/Windows Client........................ 2-2 MS-DOS Installation Upgrade Issue (V1.0 to V2.x)........................................ 2-3 Installation Order of Client/Server Software................................. 2-3 Pre-installation Requirements for the Macintosh Client............................. 2-4 Guidelines for Macintosh Consoles Running AppleTalk................................ 2-4 Summary: Client Requirements for Backup...... 2-6 Active Clients........................... 2-6 iii Ways to Activate a Client................ 2-6 Running a Client............................. 2-7 Starting the Launcher.................... 2-7 Exiting the Main Client Image............ 2-8 Purpose of Client Option Switches........ 2-8 Selecting Option Switches................ 2-9 Client Option Switches Description....... 2-10 Starting the Client Software (Windows Client or Windows for Workgroups)................... 2-11 To Start a Windows Client or Windows for Workgroups............................... 2-11 Starting the Management Console.......... 2-11 Starting the Backup Client Image on a Windows Client........................... 2-12 Starting the Client Software (Macintosh Client)...................................... 2-12 Overview................................. 2-13 Starting the Client Software: System 7.0.x.................................... 2-13 Starting the Client Software: System 6.0.x.................................... 2-13 Common Behaviors and Information between System 6 and System 7 Machines........... 2-13 3 Server Software Installation Overview..................................... 3-1 Server Installation General Information.............................. 3-1 In this Chapter.......................... 3-1 Preparation.................................. 3-2 Overview................................. 3-2 Distribution Kit Contents................ 3-2 Required Software........................ 3-3 Hardware Configuration................... 3-3 Account Privileges....................... 3-4 Process Account Quotas................... 3-4 Disk Space Requirements.................. 3-4 License Registration..................... 3-6 VAXcluster Considerations.................... 3-8 Introduction............................. 3-8 Loading the License for a VAXcluster..... 3-8 Password Structure/Security.................. 3-9 iv Introduction............................. 3-9 The Instances of Passwords............... 3-9 Preinstallation Tasks........................ 3-10 Product Licenses......................... 3-10 Making Network Links Available........... 3-11 Verifying Clients in the Network Database................................. 3-13 Rdb/OpenVMS Support...................... 3-14 Installing Desktop Backup on a Server........ 3-15 Overview................................. 3-15 Length of Time........................... 3-15 About this Example....................... 3-15 About this Example....................... 3-21 Installing StorageWorks Desktop Backup/Archiver on an Alpha OpenVMS System... 3-25 Migrating StorageWorks Desktop Backup/Archiver from VAX/OpenVMS to Alpha/OpenVMS................................ 3-26 Overview................................. 3-26 Procedure................................ 3-26 Post-installation Tasks...................... 3-27 Starting up the Server................... 3-28 Shutting down the Server................. 3-28 Changing the Password on the DTB$SERVER Account.................................. 3-28 OpenVMS V6.0 Considerations.............. 3-29 VAX Rdb/VMS Upgrades..................... 3-30 4 MS-DOS/Windows Client Installation Overview..................................... 4-1 The Client Installation Process.......... 4-1 Ensuring PATHWORKS is Set Up for Windows.................................. 4-2 Mail Notification with PATHWORKS......... 4-2 Windows Client Priorities................ 4-3 Server Commands for Setting up a File Service.................................. 4-3 Connecting to the File Service from the Client System............................ 4-4 Setting Up a File Service Under PATHWORKS V5.0 for MS-DOS.......................... 4-4 v General Procedure for Installing an MS-DOS Client............................ 4-6 Client Software Installation................. 4-8 Starting Setup........................... 4-8 MS-DOS/Windows Installation Window....... 4-10 Choosing the Destination Path............ 4-11 Choosing the Include Path................ 4-12 Launcher................................. 4-13 Exclude Path............................. 4-14 Selecting the Management Console......... 4-15 Entering the Server Node Name where the Backup Manager Resides................... 4-16 Providing User Names and Passwords....... 4-18 Confirming Your Installation Choices..... 4-19 The Connection Program................... 4-20 Setup Creates a Program Group and Program Items.................................... 4-21 Starting the Client Software (MS-DOS Client)...................................... 4-22 Starting an MS-DOS Client................ 4-22 Client Idle State........................ 4-22 Manual MS-DOS/Windows Installation Process... 4-23 NFT Copy................................. 4-23 Norton Desktop........................... 4-23 Source Directory for Local Installations............................ 4-25 Pre-Disaster Recovery Setup Procedure for MS-DOS....................................... 4-25 Overview................................. 4-25 Procedure for Creating a Key Disk: PATHWORKS V4.x Client.................... 4-26 Procedure: PATHWORKS V5.x Client......... 4-27 Implementing Disaster Recovery........... 4-31 5 Macintosh Client Installation Overview..................................... 5-1 Pre-installation Considerations.......... 5-1 Communications Toolbox................... 5-1 The Client Installation Process.......... 5-1 Client Installer......................... 5-2 Server Commands for Setting up a File Service.................................. 5-2 vi Installing the Macintosh Client.............. 5-2 General Procedure for Installing a Macintosh Client......................... 5-3 Selecting a File Server.................. 5-4 Connecting to the File Server as a Registered User.......................... 5-5 Select the Items on the File Server You Want to Use.............................. 5-6 Starting the Desktop Backup Installer.... 5-7 The Install Startup Screen............... 5-8 Deciding Which Software to Install....... 5-9 Selecting the Location for the Console and Client Software...................... 5-10 Setting Client Parameters................ 5-11 Entering Client Information.............. 5-13 Starting the Client Software (Macintosh Client)...................................... 5-14 Overview................................. 5-14 Starting the Client Software: System 7.0.x.................................... 5-14 Starting the Client Software: System 6.0.x.................................... 5-14 Common Behaviors and Information between System 6 and System 7 Machines........... 5-14 Pre-Disaster Recovery Set-up Procedures for Macintosh.................................... 5-15 Overview................................. 5-15 Procedure................................ 5-15 Implementing Disaster Recovery........... 5-15 Glossary Index vii Examples 3-1 Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product.... 3-15 3-2 Installing With No Previous Version of the Product.............................. 3-21 Figures 2-1 Client Option Switches................... 2-9 2-2 The Management Console Icon.............. 2-11 2-3 Client Software Icon..................... 2-12 2-4 StorageWorks Desktop Backup/Archiver Windows Client Screen ................... 2-12 4-1 Starting Setup........................... 4-9 4-2 Client Installation...................... 4-10 4-3 Destination Path......................... 4-11 4-4 Include Path............................. 4-12 4-5 Exclude Path............................. 4-14 4-6 Management Console Selection............. 4-15 4-7 Backup Manager Node Name................. 4-16 4-8 Client Information....................... 4-18 4-9 Installation Confirmation................ 4-19 4-10 Connection to the Server................. 4-20 4-11 The Desktop Backup Program Group......... 4-21 4-12 MS-DOS Client Pause Screen .............. 4-22 5-1 Choosing a File Server................... 5-4 5-2 Connect to the File Server............... 5-5 5-3 Selecting Items on the File Server....... 5-6 5-4 Starting the Installer................... 5-7 5-5 The Install Startup Screen .............. 5-8 5-6 Software Choices for Installation........ 5-9 5-7 Console and Client Software Location Choices.................................. 5-10 5-8 Settings................................. 5-11 5-9 Entering Client Information.............. 5-13 viii Tables 2-1 Client Option Switches................... 2-10 3-1 Process Account Quotas for the Installing Account.................................. 3-4 3-2 Disk Space Requirements.................. 3-5 3-3 Registering a License.................... 3-6 3-4 Rdb/OpenVMS Support...................... 3-14 3-5 Alpha OpenVMS Rdb Version Support........ 3-14 ix ________________________________________________________________ About This Guide GENERAL PRODUCT INFORMATION StorageWorks Desktop Backup/Archiver (also called Desktop Backup) is a client/server software application that is a high-performance network backup solution for PCs that provides unattended backup of multiple PCs to one or more servers. You use it to back up data from and restore data to PCs on a network. Desktop Backup supports OpenVMS operating system servers and PATHWORKS for MS-DOS and Macintosh clients. Use of StorageWorks Desktop Backup/Archiver can facilitate recovery from a disaster. AUDIENCE This guide is intended for system and network administrators who are responsible for installing and maintaining software. HOW THIS GUIDE IS STRUCTURED o Chapter 1 gives an overview of the product. o Chapter 2 describes pre-installation considerations. o Chapter 3 explains how to install the server portion of the software. o Chapter 4 explains how to install a MS-DOS/Windows client. o Chapter 5 explains how to install a Macintosh client. ix CONVENTIONS The following conventions are used in this guide: __________________________________________________________ Convention__________Meaning_______________________________ MB1 and MB2 For a right-handed mouse, MB1 indicates the left mouse button, and MB2 indicates the right mouse button. (You can redefine the mouse buttons.) The box represents an on-screen button, which can be selected either using the mouse or the keyboard. The boldface character inside the box, or the underlined character on some screen text, is the enabling character you use from the keyboard to enable the button. Alt A or Ctrl A These sequences mean you hold down the first key and simultaneously press the second. Example: Hold down the key and type A. boldface type Indicates user input in code examples. italic type Indicates the first occurrence of terms in text and the complete titles ____________________of_manuals._Also_used_for_emphasis.___ x 1 ________________________________________________________________ Product Overview ________________________________________________________________ Overview PRODUCT INFORMATION Digital's StorageWorks Desktop Backup/Archiver software (also called Desktop Backup) is a high-performance network backup solution for PCs. You use it to back up data from and restore data to PCs on a network. It is a client /server layered software product that provides unattended backup of multiple PCs to one or more servers. Desktop Backup supports OpenVMS operating system servers and PATHWORKS for MS-DOS and Macintosh clients. Use of StorageWorks Desktop Backup/Archiver can facilitate recovery from a disaster. DESKTOP BACKUP SERVER A typical Desktop Backup server consists of an OpenVMS platform with any supported tape drive. DESKTOP BACKUP CLIENT Desktop Backup clients are single or several PCs that run the MS-DOS, Windows, or Macintosh operating systems that have local disks that require backup. Multiple clients on the network can be backed up by a single Desktop Backup system. Product Overview 1-1 Overview MS-DOS CLIENT The MS-DOS client software consists of two programs: o The Client program locks the MS-DOS client for exclusive use by the Desktop Backup server. No other activity occurs until the client program is exited. o The Launcher TSR (terminate and stay resident) program allows the Desktop Backup server to activate the client program across the network. This sets an MS-DOS client for unattended backups. The Launcher can be run from the C:\> prompt or from the AUTOEXEC.BAT file. The Launcher does not need to be run if you intend to run the client program manually. WINDOWS CLIENT The Windows client software consists of two applications: o The management console user interface application defines or changes schedules, include and exclude paths, and user information for that specific Windows client. It is only run when the initial definition or subsequent changes need to be made. o The Backup client application sets the Windows client for access by the Desktop Backup server as a background task. This allows other applications to run while the backup is running. ________________________Note ________________________ Modifying files during a backup or restore may leave files in an inconsistent state. _____________________________________________________ 1-2 Product Overview Overview MACINTOSH CLIENT The Macintosh client software consists of two applications, the client and the management console. It sets the Macintosh client for background access or exclusive access by the Desktop Backup Server. ________________________Note ________________________ Modifying files during a backup or restore may leave files in an inconsistent state. _____________________________________________________ Product Overview 1-3 2 ________________________________________________________________ Installation Overview ________________________________________________________________ Overview StorageWorks Desktop Backup/Archiver is a client/server application. There are several programs, also called processes that must be installed on the server system or systems, as well as software that must be installed on each of the client systems. DEFINITIONS OF CLIENT AND SERVER A typical Desktop Backup server consists of an OpenVMS platform with any supported tape or disk drive. A typical Desktop Backup client is one IBM-compatible PC (or several PCs) that runs MS-DOS, Windows, or Macintosh computers and has local disks that require backup. Multiple clients on a network can be backed up by a single StorageWorks Desktop Backup/Archiver system. DEFINITION OF THE BACKUP MANAGER PROCESS The most important piece of the server software is the Backup Manager process. The Backup Manager maintains all information on backup jobs, clients, and users. The server software must be installed and running before you install software on any of the clients. The reason for this is that as you install a client, the client connects to the Backup Manager process on the server and writes information to the Backup Manager's database. Installation Overview 2-1 Overview IN THIS CHAPTER This chapter contains the following information: o Pre-installation guidelines for the server o Pre-installation requirements for the MS-DOS/Windows client o Pre-installation requirements for the Macintosh client ________________________________________________________________ Pre-installation Guidelines for the Server If the device on which you install Desktop Backup/Archiver is used for your OpenVMS page and swap files, note that the I/O requirements of these files may impact the performance of Desktop Backup. If you want, the product may be installed to a disk and directory of your choice by answering the "Enter product destination device:[directory] (SYS$SPECIFIC:[DTB])" question during the installation process to indicate where you want to install the product. The server must be running before you install a client. ________________________________________________________________ Pre-installation Requirements for the MS-DOS/Windows Client Proper installation of Desktop Backup requires that the Server and Manager software be installed on the OpenVMS system and the server must be running, then all client software installed. 2-2 Installation Overview MS-DOS Installation Upgrade Issue (V1.0 to V2.x) ________________________________________________________________ MS-DOS Installation Upgrade Issue (V1.0 to V2.x) INSTALLATION ORDER OF CLIENT/SERVER SOFTWARE Proper installation of Desktop Backup requires that the Server software be installed on the OpenVMS system first, then all client software installed. When the client software is installed, client information is registered (for a new client) or updated (for existing clients) in the scheduler database on the OpenVMS server, modifying the client type from a V1.0 client to a V2.x client. This is necessary only if you are upgrading from V1.0 to V2.0 of the product. If you have to reinstall the OpenVMS software (and reconvert your V1.0 databases to V2.x format), the client types will again be set as V1.0 clients in the converted database. You must then either reinstall the MS-DOS /Windows client or manually change any clients which have already been upgraded to use the V2.x software by issuing the following command under DBACKUP MANAGE: MANAGE> MODIFY CLIENT client_name/CLIENT=DOS SHOW CLIENT client_name should then show the client type field as "MS-DOS" (V1.0 clients show the client type field as "MS-DOS (pre-V2.0)"). ______________________ Warning ______________________ Attempting to back up a V2.x MS-DOS/Windows client when the database has that client listed as a V1.0 client will more than likely hang that PC when the client is backed up. _____________________________________________________ Installation Overview 2-3 Pre-installation Requirements for the Macintosh Client ________________________________________________________________ Pre-installation Requirements for the Macintosh Client Macintosh clients can be backed up using DECnet or AppleTalk. The installation procedure checks for the existence of the file SYS$SHARE:ATK$APPLETALK_RTL.EXE to determine if AppleTalk is available on the OpenVMS server. If AppleTalk is not available, Macintosh clients will only be capable of being backed up over DECnet. If this is not desirable, you are given the opportunity of aborting the installation. If at some time in the future, you want to add AppleTalk support for Macintoshes, you will need to reinstall Desktop Backup. GUIDELINES FOR MACINTOSH CONSOLES RUNNING APPLETALK You should be aware that there is a limit to the number of Macintosh Consoles and Macintosh Clients that can be run simultaneously if you are using AppleTalk. Each Macintosh Console and Client consumes a certain amount of dynamic memory (nonpaged pool) which is deducted from the Backup Manager process. The /BUFFER_LIMIT qualifier in the DTB$STARTUP.COM command file determines the amount of dynamic memory (BYTLM) available to the Backup Manager process. The /BUFFER_LIMIT is normally set at 30000 bytes. Each Macintosh Console consumes approximately 9000 bytes of dynamic memory. Each Macintosh Client consumes approximately 5000 bytes of dynamic memory during user verification. When actually performing a backup operation, approximately 1500 bytes are consumed. Digital recommends that you plan for the maximum consumption of 5000 bytes should you need to adjust /BUFFER_LIMIT. Given the default setting of 30000 bytes, you should plan on running no more than two consoles and one client simultaneously. Be aware that this figure includes overhead required for Backup Manager initialization and startup. If you want to run more than two consoles simultaneously, increase the /BUFFER_LIMIT value by 9000 bytes for each console. 2-4 Installation Overview Pre-installation Requirements for the Macintosh Client If you exhaust the Backup Manager's dynamic memory, the Backup Manager process will enter a MUTEX wait state. (The DCL command SHOW SYSTEM will provide you with this information). Should this condition occur, all Macintoshes with active DTB/A sessions will be hung. It will be necessary to reboot one or more Macintoshes to free the Backup Manager from the MUTEX state. Installation Overview 2-5 Summary: Client Requirements for Backup ________________________________________________________________ Summary: Client Requirements for Backup ACTIVE CLIENTS In order for a client system to be backed up, the client system needs to be active; that is, the client software must be running. There are three types of clients: o MS-DOS clients (which can use the Launcher TSR) o Windows clients o Macintosh clients WAYS TO ACTIVATE A CLIENT These are the possible ways for a client to be active (or ready to be activated): o For Windows: A Windows client must be running, though you can make it an icon. o For MS-DOS: - An MS-DOS client must be running (the Desktop Backup Client screen displays on the monitor), or - The Launcher must be loaded so that the MS-DOS client can be started when needed, unless it will be manually started before the backup. o For a Macintosh: - Check the application menu. The DTB client should display. A Macintosh client can be backed up while other software applications are being used. - The client software can be used while other software applications are running. 2-6 Installation Overview Running a Client ________________________________________________________________ Running a Client This chapter describes the software that must be set up on each client to let the StorageWorks Desktop Backup /Archiver perform backup and restore operations correctly. This software includes: o The MS-DOS client software, including the Launcher TSR (Terminate and Stay Resident) program o The Windows client software o The Macintosh client software STARTING THE LAUNCHER The Launcher is an MS-DOS Terminate and Stay Resident (TSR) program that lets the backup server activate the Main Client Image across the network. With these two images, you can set an MS-DOS client for unattended backups. The client installation procedure optionally modifies the AUTOEXEC.BAT file on the MS-DOS client to let the system know the location of the StorageWorks Desktop Backup/Archiver images. To run the Launcher, type the following command at the C:\> prompt (or add it to your AUTOEXEC.BAT file): C>C:\DTB\Launcher C:\DTB ________________________Note ________________________ As you proceed with the installation, if you made the decision to place the Launcher in the AUTOEXEC.BAT file so it is automatically loaded into memory when the client is booted, you do not use the command above. The software starts automatically. _____________________________________________________ Installation Overview 2-7 Running a Client DTB is the default directory on drive C that the install program uses for the Desktop Backup files. If you use a different directory, substitute your directory in both places in the above command. EXITING THE MAIN CLIENT IMAGE Use this procedure to exit the MS-DOS Main Client Image. __________________________________________________________ Step_Action______________Result___________________________ 1. Press any keyboard The prompt "Enter Client key. Password" displays. 2. Enter your Client The "Client Pause Password" is Pause Password. set up during Client installation As you type on the User Profile installation your password, screen. You can change your asterisks (****) Client pause password using the display on the Client option switches, described screen under the in the next section. _____word_"Idle."_________________________________________ Once you exit the MS-DOS Main Client Image, your system is ready for normal MS-DOS commands; that is, the StorageWorks Desktop Backup/Archiver client is no longer running. PURPOSE OF CLIENT OPTION SWITCHES For an MS-DOS client system, there are several option switches that you can use to make changes to a client setup. You can use the option switches to: o Modify the server node name. o Modify or disable your password. o Modify the display to use: - Client Idle Screen only - Client Idle Screen, plus Client Pause Screen o Exit to MS-DOS prompt after backup is complete. 2-8 Installation Overview Running a Client SELECTING OPTION SWITCHES To select the main Client image option switches (see Table 2-1), at the MS-DOS prompt enter the following command: C:\>CLIENT /? The system displays the client option switches as shown in Figure 2-1. Figure 2-1 Client Option Switches See Table 2-1 for a description of the client option switches. Installation Overview 2-9 Running a Client CLIENT OPTION SWITCHES DESCRIPTION Table 2-1 describes the client option switches. Table_2-1_Client_Option_Switches__________________________ Switch___________Function_________________________________ /? Displays the client option switches. /NOPAUSE Displays the Client Idle screen only; does not display the pause screen (Figure 4-12). /NOPASSWORD Use this switch only if you want to eliminate the need for entering a password to exit the Client Pause screen. /EXIT Exits the Client Idle mode after backup is complete. Note: If needed, use Ctrl/Alt/Del to reboot the PC. /Sxxx Sets the Backup Manager node name, where xxx is the node name; for example: CLIENT /STAPE, where TAPE is the node name. /Pxxx Sets pause password, where xxx is the password; for example: CLIENT /PSECRET, _________________where_SECRET_is_the_password.____________ 2-10 Installation Overview Starting the Client Software (Windows Client or Windows for Workgroups) ________________________________________________________________ Starting the Client Software (Windows Client or Windows for Workgroups) TO START A WINDOWS CLIENT OR WINDOWS FOR WORKGROUPS There are two things to consider when you start a Windows client: 1. Starting the management console. 2. Starting the client software that actually handles the backup tasks. STARTING THE MANAGEMENT CONSOLE Use the management console to initially define, or later to make changes to, schedules, include and exclude paths, and user information for that specific client. To access these functions, double-click on the management console icon. See Figure 2-2. Figure 2-2 The Management Console Icon Once you define the user and schedule information, the only software that needs to be activated for subsequent backups of this client is the Backup Client Image. Installation Overview 2-11 Starting the Client Software (Windows Client or Windows for Workgroups) STARTING THE BACKUP CLIENT IMAGE ON A WINDOWS CLIENT To start the Backup Client Image on a windows client: __________________________________________________________ Do_this..._______This_happens...__________________________ Double-click The "Desktop Backup Client" screen on the Backup displays (Figure 2-4). Client icon. See_Figure_2-3.___________________________________________ Figure 2-3 Client Software Icon Figure 2-4 StorageWorks Desktop Backup/Archiver Windows Client Screen ________________________________________________________________ Starting the Client Software (Macintosh Client) 2-12 Installation Overview Starting the Client Software (Macintosh Client) OVERVIEW Once the client software has been installed, use this procedure for starting the client software. The client software must be running for a backup of this client to take place. STARTING THE CLIENT SOFTWARE: SYSTEM 7.0.X After installation, restart the Macintosh or double-click on the "Client" icon located in the Startup Items folder. STARTING THE CLIENT SOFTWARE: SYSTEM 6.0.X Double-click on the "Client" icon located in the System Folder. COMMON BEHAVIORS AND INFORMATION BETWEEN SYSTEM 6 AND SYSTEM 7 MACHINES The first time the client software is run, a setup dialog displays. This is the same dialog displayed when you choose Setup from the File menu. Enter the name of the OpenVMS node on which the DTB manager process is running and choose a processor utilization setting. "High- Priority" means that once a backup of this client starts, no other work on this client can be done until the backup finishes. "Low-Priority" means that the client gives up the processor so that you can do other work while a backup is running. ________________________Note ________________________ Modifying files during a backup or restore may leave files in an inconsistent state. _____________________________________________________ Installation Overview 2-13 3 ________________________________________________________________ Server Software Installation ________________________________________________________________ Overview SERVER INSTALLATION GENERAL INFORMATION The StorageWorks Desktop Backup/Archiver server software must be installed and running before you attempt to install any of the client systems' software. Follow the steps in this chapter to install the server software. IN THIS CHAPTER This chapter contains the following information: o How to prepare for the StorageWorks Desktop Backup /Archiver installation o VAXcluster system considerations o Password structure o Pre-installation tasks o Installing Desktop Backup on a server o Troubleshooting o Installing Desktop Backup on a client Server Software Installation 3-1 Preparation ________________________________________________________________ Preparation OVERVIEW Installing the Desktop Backup server software kit is similar to installing other OpenVMS layered products. This table provides an overview of the preparation you need to make. __________________________________________________________ Step___Action_____________________________________________ 1. Check the software distribution kit for contents. 2. Verify that your system has the prerequisite software. 3. Verify your system's hardware configuration. 4. Ensure that you have special account privileges. 5. Ensure that you have enough disk space. 6._____Register_and_load_the_Desktop_Backup_licenses._____ DISTRIBUTION KIT CONTENTS Each Desktop Backup distribution kit contains the following: o A bill of materials and indented bills report o The distribution medium for Desktop Backup software o Documentation for the product o The Product Authorization Key (PAK) To be sure that you have a complete kit, check the kit contents against the bill of materials and the indented bills report. If your kit is damaged or if you find parts missing, contact your Digital representative. 3-2 Server Software Installation Preparation REQUIRED SOFTWARE The following software versions are required: o A valid OpenVMS operating system configuration running V5.5-2 or later (VAX), or V1.5 or later for Alpha, V6.1 for VAX. o VAX Rdb/VMS V4.0-3 (or later) for VAX, V5.1 for Alpha. ________________________Note ________________________ You can load Standard Rdb/VMS and Multiversion Rdb/VMS on the same machine. Then, if you want to run Multiversion Rdb/VMS and StorageWorks Desktop Backup/Archiver, you must also load one of the standard versions. For example if you have Multiversion Rdb/VMS 4.1 and Standard Rdb/VMS 4.1 loaded on the same machine, StorageWorks Desktop Backup/Archiver can be run. _____________________________________________________ o Run-time version of Rdb. o PATHWORKS for OpenVMS V4.0 or later - Optional: If you want to back up Macintosh machines using AppleTalk, you need PATHWORKS for VMS Macintosh V1.3. HARDWARE CONFIGURATION Desktop Backup software supports all hardware configurations supported by a OpenVMS V5.5-2 (for VAX), or OpenVMS V1.5 for Alpha and later operating system. See the StorageWorks Desktop Backup/Archiver Software Product Description for details on supported hardware configurations. Server Software Installation 3-3 Preparation ACCOUNT PRIVILEGES To install the Desktop Backup (server), you must have the specific SYSPRV account privileges. Most system administrators install software from the SYSTEM account. ________________________Note ________________________ The VMSINSTAL command procedure turns off BYPASS privileges at the beginning of the installation. _____________________________________________________ PROCESS ACCOUNT QUOTAS The account you use to install Desktop Backup must have sufficient quotas to enable you to perform the installation. Table 3-1 summarizes the requirements. Table 3-1 Process Account Quotas for the Installing __________Account_________________________________________ Account_Quota____Value____________________________________ ASTLM 24 BIOLM 18 BYTLM 32768 DIOLM 18 ENQLM 200 FILLM 40 PRCLM 10 WSDEF____________256______________________________________ DISK SPACE REQUIREMENTS You use the VMSINSTAL command procedure to install Desktop Backup software. For VMSINSTAL to run correctly, there must be sufficient disk storage space and the correct system parameter settings to accommodate the installation. Desktop Backup's requirements for free disk storage space are different during installation and after installation. Table 3-2 summarizes the storage requirements. 3-4 Server Software Installation Preparation Table_3-2_Disk_Space_Requirements_________________________ During Kit_________Installation_____After_Installation___________ VAX 20000 Blocks 15000 Blocks Alpha_______16000_Blocks_____15000_Blocks_________________ ________________________Note ________________________ Be aware when installing Desktop Backup that the History Database (the part of Desktop Backup that tracks everything that has been backed up and restored from and to clients) can grow quite large. There is a way to prune that database (see the StorageWorks Desktop Backup/Archiver System Administrator's Guide), Chapters 8 and 9, but keep in mind that it may still require significant disk space. The installation procedure for Desktop Backup lets you decide on a disk on which to install the product. Some users may want to consider not installing the product on their system disk. _____________________________________________________ If the device on which you install Desktop Backup/Archiver is used for your OpenVMS page and swap files, note that the I/O requirements of these files may impact the performance of Desktop Backup. If you want, the product may be installed to a disk and directory of your choice by answering the "Enter product destination device:[directory] (SYS$SPECIFIC:[DTB])" question during the installation process to indicate where you want to install the product. The server must be running before you install a client. Server Software Installation 3-5 Preparation LICENSE REGISTRATION ________________________Note ________________________ If you are installing on a VAXcluster, refer to the next section of this chapter. _____________________________________________________ You must register and load the product license before you install or use the product. The information you need for this is in the Desktop Backup Product Authorization Key (PAK) that comes with the Desktop Backup software. The PAK is a paper certificate that contains data about your license. ______________________ Caution ______________________ If you do not register and load the license before installing the Desktop Backup software, the installation will not complete. _____________________________________________________ Table 3-3 describes how to register a license. Table_3-3_Registering_a_License___________________________ Step_Action_______________________________________________ 1. Log into a privileged account. Example: the system manager's account, SYSTEM. 2. Choose one of the following procedures to register the license: Use the @SYS$UPDATE:VMSLICENSE.COM procedure. When prompted for information, respond with the data from your PAK. Use the DCL commands LICENSE REGISTER and LICENSE LOAD with the correct qualifiers that correspond to information on the PAK. _____The_second_method_is_faster_for_experienced_users.___ 3-6 Server Software Installation Preparation For additional information, see the License Management Facility section in your OpenVMS documentation set. Server Software Installation 3-7 VAXcluster Considerations ________________________________________________________________ VAXcluster Considerations INTRODUCTION You can install Desktop Backup on a particular node of a VAXcluster. Because Desktop Backup is installed in a system specific area and not in a cluster common area, the product should be run from one member node in the cluster. You can install the backup server process on separate or different nodes in the cluster, but the Backup Manager process must be run from one node. LOADING THE LICENSE FOR A VAXCLUSTER This product must run on one single node, not cluster- wide. If a license is loaded on a node in a cluster, upon reboot, a different node in the cluster may load the license. As a result, Desktop Backup will not start properly. Use the LICENSE/MODIFY/INCLUDE=(node name) command described in the OpenVMS License Management Utility manual to avoid this problem. 3-8 Server Software Installation Password Structure/Security ________________________________________________________________ Password Structure/Security INTRODUCTION Desktop Backup provides security for your data on client systems through the use of passwords. During the server installation procedure, there are two separate and distinct instances of password protection with which you need be concerned. THE INSTANCES OF PASSWORDS 1. The DTB$SERVER account password. You choose this password when prompted by the server software installation procedure. DTB$SERVER is an OpenVMS account. This account and password are associated with the DECnet network object in order to run Desktop Backup/Archiver. 2. The Desktop Backup Administrator username/password pair. You choose this username/password pair during the server software installation procedure as well. This username/password pair identifies the person who will be managing Desktop Backup (the Administrator). This person can access all of the functions of Desktop Backup, and all the data backed up and restored during operation. The Administrator can also assign privilege levels to other users. This username/password pair is associated with a client system and provides ownership information when the client data is moved into savesets on the server system. This username/password pair is not an OpenVMS account username and password; rather, it is a Desktop Backup username/password pair used for security. More than one user can eventually be assigned Administrator privileges, though only one can be assigned those privileges during the installation procedure. Server Software Installation 3-9 Preinstallation Tasks ________________________________________________________________ Preinstallation Tasks PRODUCT LICENSES You should check certain system parameters to ensure that PATHWORKS is installed and working correctly before you install Desktop Backup. The information below lists the checks that you should perform and shows examples of results. The actual results you see may be different than those shown here, depending upon your particular system configuration. 1. Make sure both server and client licenses are loaded into the OpenVMS License Management Facility (LMF) database. Use the SHOW LICENSE command from the OpenVMS ($) prompt. $ SHOW LICENSE ________________________Note ________________________ Depending on how many licenses you have on your system, the result of the SHOW LICENSE command may be a significant amount of information printed to your screen. The licenses you are checking for contain the entries: Either One or the Other: o PWKS-DT-BKSVR License for the OpenVMS (VAX) server software. o SWKS-DT-SVR-AXP License for the OpenVMS (Alpha) server software. 3-10 Server Software Installation Preinstallation Tasks Either One or Both: o PWKS-DT-BK-CL License for the MS-DOS or Windows client software.[1] o SWKS-DT-UCL-USER The universal client license for any client type. _____________________________________________________ MAKING NETWORK LINKS AVAILABLE Make sure the server and the PC client(s) each have enough network links available. The client requires at least three network links, and the server requires two links per backup and one link for every user interface. This is the difference between the number of possible links and the number of current links. To determine the number of current links, issue the following command on the server: $ MCR NCP SHOW KNOWN LINKS Known Link Volatile Summary as of 15-APR-1994 11:04:14 Link Node PID Process Remote link Remote user |- 8193 18.117 (ELWD1) 2CE000A1 _TWA3: 8291 CTERM |->| 8195 18.117 (ELWD1) 2CE000A0 _TWA2: 344 CTERM | | 8203 63.165 (NTBK22) 2CE000A3 _TWA5: 8204 CTERM | |_ 8204 63.165 (NTBK22) 2CE000A6 REMACP 8203 CHAUVIN | |______ NOTE: This list shows the links being used; for example, in this configuration, a total of four network links are in use. ___________________ [1] Use the LICENSE command (DCL) to display system-level information regarding the number of units available on your system. Make sure that you have enough units available (100 units per client). Server Software Installation 3-11 Preinstallation Tasks On a client PC, to determine the number of possible links, issue the following command, and look for the "Maximum Links" entry: C:\> NCP SHOW EXEC CHARACTERISTICS Executor Characteristics as of 13-Apr-1994 12:56:52 Executor node = 62.734 (NETBK7) Driver version number = 3.1.0 State = On Executor Identification = PATHWORKS for DOS V4.1 client. Executor version = 4.2.0 Node name = NETBK7 Node address = 62.734 Incoming timer = 45 Outgoing timer = 60 Confidence timer = 15 Incoming proxy = Disabled Outgoing proxy = Enabled Active links = 0 NSP version = 4.0.0 Maximum links = 12 <---- Maximum links for this client Delay factor = 32 Delay weight = 2 Inactivity timer = 30 Retransmit factor = 12 Routing version = 2.0.0 Routing type = Nonrouting IV Maximum buffers = 16 Buffer size = 1498 Segment buffer size = 576 Receive password = (password is not set) Transmit password = (password is not set) Database path = C:\DECNET\ Transmit pipe quota = 6 Receive pipe quota = 6 PC type = IBM PC or Compatible Nak quota = 0 Autoboot = Enabled 3-12 Server Software Installation Preinstallation Tasks ________________________Note ________________________ The significance of the "maximum number of links" and the "links being used" is in the difference between those two numbers. Be sure the difference between the maximum number and the number being used can support your intended configuration. If you need to assign more links, use the DEFINE EXECUTOR MAX LINKS command on the PC or OpenVMS. _____________________________________________________ VERIFYING CLIENTS IN THE NETWORK DATABASE 1. Make sure the VAX has the PC client(s) listed in the network database. Also, make sure that PC client(s) have the server defined in their network database. To see if a node is in the server database, use the MCR NCP LIST NODE command and indicate a node name, for example, NETBK4, as follows: $ MCR NCP LIST NODE NETBK4 Node Permanent Summary as of 15-APR-1994 11:05:13 Remote node = 62.731 (NETBK4) No information available On a client PC, you can use the NCP LIST KNOWN NODES command: C:\> NCP LIST KNOWN NODES On a Macintosh client, select the DECnet for Macintosh folder. There is a DECnet Network Control Program (NCP) option. Select the Node Definitions option to display the known nodes list box. Server Software Installation 3-13 Preinstallation Tasks RDB/OPENVMS SUPPORT Table_3-4_Rdb/OpenVMS_Support_____________________________ Rdb/VMS_Version___________Yes____No_______________________ Standard Rdb/VMS Pre X V4.0-3 Standard Rdb/VMS V4.0-3 X Standard Rdb/VMS V4.1 X Standard Rdb/VMS V4.2 X Standard Rdb/VMS V5.0 X Standard Rdb/VMS V5.1 X Standard Rdb/VMS V6.0 X Multiversion Rdb/VMS X (any)_____________________________________________________ Table_3-5_Alpha_OpenVMS_Rdb_Version_Support_______________ Rdb/VMS_Version___________Yes____No_______________________ Standard Rdb V5.1/VMS X Standard Rdb/VMS V6.0 X Multiversion Rdb/VMS X (any)_____________________________________________________ ________________________Note ________________________ You can load Standard Rdb/VMS and Multiversion Rdb/VMS on the same machine. Then, if you want to run Multiversion Rdb/VMS and StorageWorks Desktop Backup/Archiver, you must also load one of the standard versions. For example if you have Multiversion Rdb/VMS 4.1 and Standard Rdb/VMS 4.1 loaded on the same machine, StorageWorks Desktop Backup/Archiver can be run. _____________________________________________________ 3-14 Server Software Installation Installing Desktop Backup on a Server ________________________________________________________________ Installing Desktop Backup on a Server OVERVIEW To install Desktop Backup on a server, you invoke the SYS$UPDATE:VMSINSTAL installation procedure at the system prompt, then provide responses to the screen prompts. LENGTH OF TIME You should allow about 10 minutes for the installation to complete (or longer if the installation is an update because of the database conversion) and another 5 minutes to run the Installation Verification Procedure (IVP). ABOUT THIS EXAMPLE This next example shows the command you enter to start the installation and the responses you enter at the system prompts. Note that your answers to the questions may differ from our example, based upon your system configuration. Use the VMSINSTAL command as follows: @SYS$UPDATE:VMSINSTAL DTB021 MKA400: where DTB021 is the kit name and MKA400: is the tape drive name. This example shows an upgrade from the V1.x product for which a Desktop Backup database conversion is necessary. Example 3-1 Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product $ @SYS$UPDATE:VMSINSTAL DTB021 MKA400: VAX/OpenVMS Software Product Installation Procedure V5.5-2 It is 13-APR-1994 at 14:22. (continued on next page) Server Software Installation 3-15 Installing Desktop Backup on a Server Example 3-1 (Cont.) Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$TE_005C _FTA9: _FTA10: * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DTB V2.1 Beginning installation of DTB V2.1 at 14:23 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installation of StorageWorks Desktop Backup/Archiver V2.1 **************************************************************************** ** ** ** Copyright (c) Digital Equipment Corporation 1993, 1994, 1995 ** ** All Rights Reserved. ** ** ** ** This software is proprietary to and embodies the confidential ** ** technology of Digital Equipment Corporation. Possession, use, or ** ** copying of this software and media is authorized only pursuant to ** ** a valid written license from Digital or an authorized sublicensor. ** ** ** ** Restricted Rights: Use, duplication, or disclosure by the U.S. ** ** Government is subject to restrictions as set forth in ** ** subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, ** ** or in FAR 52.227-14 Alt. III, as applicable. ** ** ** **************************************************************************** The installation can be aborted at any time by pressing CTRL/Y. (continued on next page) 3-16 Server Software Installation Installing Desktop Backup on a Server Example 3-1 (Cont.) Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product The following install options will allow you to customize the installation of the StorageWorks Desktop Backup/Archiver software. You may choose to install only the Backup Manager software or only the Backup Server software, or both. 0 - Backup Manager software 1 - Backup Server software 2 - Both Backup Manager and Backup Server * Enter the option number [2]: 2 AppleTalk and Macintosh are registered Trademarks of Apple Computer, Inc. To backup Macintosh clients via AppleTalk, the shareable image file SYS$SHARE:ATK$APPLETALK_RTL.EXE must be present on your system. Since this file could not be found, Macintosh clients will only be capable of being backed up via DECNET. Should you wish to add AppleTalk support for Macintosh at a future date, you will need to reinstall StorageWorks Desktop Backup/Archiver. Please enter 'Y' if you do not require AppleTalk support and wish to continue this installation. Or enter 'N' to exit this installation. * Continue installation? Enter Y or N: y * Enter product destination device:[directory] (SYS$SPECIFIC:[DTB]): * Do you want to purge files replaced by this installation [YES]? y Product: PWKS-DT-BKSVR Producer: DEC Version: 1.0 Release Date: * Does this product have an authorization key registered and loaded? y Product: PWKS-DT-BK-CL and/or SWKS-DT-UCL-USER Producer: DEC Version: 1.0 Release Date: (continued on next page) Server Software Installation 3-17 Installing Desktop Backup on a Server Example 3-1 (Cont.) Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product * Does this product have an authorization key registered and loaded? y * Do you want to run the IVP after the installation [YES]? y The following StorageWorks Desktop Backup/Archiver IVP files will be moved to SYS$SPECIFIC:[SYSTEST]: DTB$IVP.COM DTB$IVP.EXE You may run the IVP manually at any time after the installation by executing @SYS$TEST:DTB$IVP.COM . %VMSINSTAL-I-RESTORE, Restoring product save set B ... StorageWorks Desktop Backup/Archiver V2.0 requires a new database format. The history database files HISTORY.RDB and HISTORY.SNP are now named DTB$HISTORY.RDB and DTB$HISTORY.SNP, respectively. The scheduler database files SCHEDULER.RDB and SCHEDULER.SNP are now named DTB$SCHEDULER.RDB and DTB$SCHEDULER.SNP, respectively. This installation will COPY your existing databases to the V2.0 filenames and then convert the new databases to the new format. Your previous databases will be left intact. Enter 'Y' to allow your existing databases to be copied and converted and continue with this installation. Or enter 'N' to exit this installation. * Continue installation? Enter Y or N: y Copying your existing databases to the V2.0 filenames. Copy complete. Converting databases to the V2.0 format. Please check the log file SYS$LOGIN:DTB$DCU.LOG should any errors occur during the conversion process. Conversion complete. No further questions will be asked during this installation. This installation will take approximately 5 to 10 minutes to complete. (continued on next page) 3-18 Server Software Installation Installing Desktop Backup on a Server Example 3-1 (Cont.) Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product %VMSINSTAL-I-SYSDIR, This product creates system specific directory [DTB]. %CREATE-I-EXISTS, VMI$SPECIFIC:[DTB] already exists %VMSINSTAL-I-SYSDIR, This product creates system specific directory [DTB.DB]. %CREATE-I-EXISTS, VMI$SPECIFIC:[DTB.DB] already exists %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT]. %CREATE-I-EXISTS, VMI$SPECIFIC:[DTB.CLIENT] already exists %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.DOS]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC.MSAF$RESOURCES]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC.MSAF$VOLINFO]. Please add the following text to your startup command procedure: @SYS$STARTUP:DTB$STARTUP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting the Backup Manager %RUN-S-PROC_ID, identification of created process is 000000AB Waiting for the Backup Manager to complete startup. Backup Manager successfully started. Installation Verification Procedure for StorageWorks Desktop Backup/Archiver V2.1 Running the StorageWorks Desktop Backup/Archiver V2.1 IVP Copyright (c) 1993, 1994, 1995 Digital Equipment Corporation. All rights reserved. Adding a Desktop Backup user... Success Adding a Desktop Backup client... Success Adding a backup job... Success Removing a backup job... Success Removing Desktop Backup client... Success Removing Desktop Backup user... Success (continued on next page) Server Software Installation 3-19 Installing Desktop Backup on a Server Example 3-1 (Cont.) Upgrading/Installing the StorageWorks PATHWORKS Desktop Backup V2.1 Product Testing the server network object The following tape drives were found: LEMMA$MKA400 Network object test successful Desktop Backup IVP completed successfully VMSINSTAL procedure done at 14:29 3-20 Server Software Installation Installing Desktop Backup on a Server ABOUT THIS EXAMPLE o No database copy/conversion is needed. o Additional questions about the Backup Manager account, password, OpenVMS DTB$SERVER account UIC and password are asked. Example 3-2 Installing With No Previous Version of the Product $ @sys$update:vmsinstal dtb021 mka400: VAX/OpenVMS Software Product Installation Procedure V5.5-2 It is 14-APR-1994 at 08:44. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$TE_005C _FTA9: _FTA10: * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: DTB V2.1 Beginning installation of DTB V2.1 at 08:45 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installation of StorageWorks Desktop Backup/Archiver V2.1 (continued on next page) Server Software Installation 3-21 Installing Desktop Backup on a Server Example 3-2 (Cont.) Installing With No Previous Version of the Product **************************************************************************** ** ** ** Copyright (c) Digital Equipment Corporation 1993, 1994, 1995. ** ** All Rights Reserved. ** ** ** ** This software is proprietary to and embodies the confidential ** ** technology of Digital Equipment Corporation. Possession, use, or ** ** copying of this software and media is authorized only pursuant to ** ** a valid written license from Digital or an authorized sublicensor. ** ** ** ** Restricted Rights: Use, duplication, or disclosure by the U.S. ** ** Government is subject to restrictions as set forth in ** ** subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, ** ** or in FAR 52.227-14 Alt. III, as applicable. ** ** ** **************************************************************************** The installation can be aborted at any time by pressing CTRL/Y. The following install options will allow you to customize the installation of the StorageWorks Desktop Backup/Archiver software. You may choose to install only the Backup Manager software or only the Backup Server software, or both. 0 - Backup Manager software 1 - Backup Server software 2 - Both Backup Manager and Backup Server * Enter the option number [2]: 2 * Enter product destination device:[directory] (SYS$SPECIFIC:[DTB]): * Do you want to purge files replaced by this installation [YES]? y Product: PWKS-DT-BKSVR Producer: DEC Version: 1.0 Release Date: * Does this product have an authorization key registered and loaded? y (continued on next page) 3-22 Server Software Installation Installing Desktop Backup on a Server Example 3-2 (Cont.) Installing With No Previous Version of the Product Product: PWKS-DT-BK-CL and/or SWKS-DT-UCL-USER Producer: DEC Version: 1.0 Release Date: * Does this product have an authorization key registered and loaded? y * Do you want to run the IVP after the installation [YES]? y The following StorageWorks Desktop Backup/Archiver IVP files will be moved to SYS$SPECIFIC:[SYSTEST]: DTB$IVP.COM DTB$IVP.EXE You may run the IVP manually at any time after the installation by executing @SYS$TEST:DTB$IVP.COM . In order to ensure that the Backup Server runs correctly, this installation procedure will create an account named DTB$SERVER. * Enter UIC for DTB$SERVER account (include brackets) [[375,100]]: * Enter password for DTB$SERVER account: * Verify password for DTB$SERVER account: * Desktop Backup Administrator username [ADMINISTRATOR]: * Desktop Backup Administrator password: * Verify Desktop Backup Administrator password: %VMSINSTAL-I-RESTORE, Restoring product save set B ... No further questions will be asked during this installation. This installation will take approximately 5 to 10 minutes to complete. (continued on next page) Server Software Installation 3-23 Installing Desktop Backup on a Server Example 3-2 (Cont.) Installing With No Previous Version of the Product %VMSINSTAL-I-SYSDIR, This product creates system specific directory [DTB]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory [DTB.DB]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory _ [DTB.CLIENT.DOS]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC.MSAF$RESOURCES]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory_ [DTB.CLIENT.MAC.MSAF$VOLINFO]. %DTB-I-CREACC, Creating account DTB$SERVER for the Backup Server %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DTB$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DTB$SERVER value: [000375,000100] added to rights data base %UAF-I-RDBADDMSGU, identifier DECNET value: [000375,177777] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DTB$SERVER. %UAF-I-MDFYMSG, user record(s) updated Please add the following text to your startup command procedure: @SYS$STARTUP:DTB$STARTUP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... (continued on next page) 3-24 Server Software Installation Installing Desktop Backup on a Server Example 3-2 (Cont.) Installing With No Previous Version of the Product Starting the Backup Manager %RUN-S-PROC_ID, identification of created process is 00000183 Waiting for the Backup Manager to complete startup. Backup Manager successfully started. Adding Backup Administrator account. Installation Verification Procedure for StorageWorks Desktop Backup/Archiver V2.1 Running the StorageWorks Desktop Backup/Archiver V2.1 IVP Copyright (c) 1993, 1994, 1995 Digital Equipment Corporation. All rights reserved. Adding a Desktop Backup user... Success Adding a Desktop Backup client... Success Adding a backup job... Success Removing a backup job... Success Removing Desktop Backup client... Success Removing Desktop Backup user... Success Testing the server network object The following tape drives were found: LEMMA$MKA400 Network object test successful Desktop Backup IVP completed successfully Installation of DTB V2.1 completed at 08:53 VMSINSTAL procedure done at 08:53 ________________________________________________________________ Installing StorageWorks Desktop Backup/Archiver on an Alpha OpenVMS System Installation differs slightly for Alpha OpenVMS: Server Software Installation 3-25 Installing StorageWorks Desktop Backup/Archiver on an Alpha OpenVMS System o Saveset C will be restored instead of saveset B. o No database conversion is necessary since there are no previous versions of the StorageWorks Desktop Backup /Archiver for Alpha servers. ________________________________________________________________ Migrating StorageWorks Desktop Backup/Archiver from VAX/OpenVMS to Alpha/OpenVMS OVERVIEW This procedure explains how to migrate the necessary files and databases from the VAX platform to the Alpha platform. A prerequisite is that the databases must be migrated from V2.0 of Desktop Backup; V1.x databases cannot be migrated directly to the Alpha platform. PROCEDURE First, install Desktop Backup on the Alpha machine. This will produce new versions of the DTB$HISTORY.RDB and DTB$SCHEDULER.RDB database files. DTB$HISTORY.SNP and DTB$SCHEDULER.SNP (snapshot files) are also created. Also install V2.1 on the VAX machine. Once Desktop Backup is installed on the Alpha machine, perform the following steps: 1. Shut down the Backup Manager on both the VAX and the Alpha machines. Use the command DBACKUP STOP from the DCL prompt as follows (see also Chapter 9 of the StorageWorks Desktop Backup/Archiver System Administrator's Guide): $ DBACKUP MANAGE /USER=xxx /PASS=yyy MANAGE> STOP 3-26 Server Software Installation StorageWorks Desktop Backup/Archiver from VAX/OpenVMS to Alpha/OpenVMS 2. Next, copy all files in the DTB$ROOT:[DB] directory associated with the existing installation of Desktop Backup (the .RDB files, the .SNP files, and the .DAT files for all the clients) from the VAX to the Alpha machines. Use VMS BACKUP for this function as follows: $ BACKUP/LOG DTB$ROOT:[DB...]*.* Saveset_Name.BCK/sav The command above creates a saveset with all the necessary files. Copy the saveset to the Alpha machine. 3. On the Alpha machine, use VMS BACKUP to unpack the saveset, as follows: $ BACKUP/LOG Saveset_Name.BCK/Sav [...] 4. Next, use the RMU Convert command of Rdb to convert the databases, as follows: RMU/CONVERT/COMMIT/NOCONFIRM DTB$HISTORY.RDB RMU/CONVERT/COMMIT/NOCONFIRM DTB$SCHEDULER.RDB ________________________________________________________________ Post-installation Tasks Note that when you run the IVP, the product is automatically started. If you do not run the IVP during the installation, you must manually start the product. To manually start Desktop Backup, type the following command: @SYS$STARTUP:DTB$STARTUP If you want Desktop Backup to start up each time you boot your system, follow the procedure described in the next section. Server Software Installation 3-27 Post-installation Tasks STARTING UP THE SERVER For VAX systems running V5.0, edit the SYS$STARTUP_V5.COM file. For Alpha and OpenVMS V6.0 systems, edit the SYS$STARTUP_VMS.COM file. Add the following line to your startup command procedure: @SYS$STARTUP:DTB$STARTUP.COM If you are using Appletalk, on occasion, the DTB$STARTUP command file may produce a message when you start the product as follows: Unable to connect to remote module You should make certain that AppleTalk is up and running prior to starting Desktop Backup. If you see this message upon startup, shut down Desktop Backup using the DTB$SHUTDOWN command file, then invoke the DTB$STARTUP file again. SHUTTING DOWN THE SERVER The DTB$SHUTDOWN.COM command procedure is invoked manually by typing the following: @SYS$STARTUP:DTB$SHUTDOWN CHANGING THE PASSWORD ON THE DTB$SERVER ACCOUNT If the password on the DTB$SERVER account changes (for example, if you have set the password as pre-expired), Desktop Backup will not work. However, if the DTB$SERVER password was set as pre-expired, the Installation Verification procedure would work. This might result in some confusion. So, if the DTB$SERVER account password changes for any reason, you need to reset the password. Also, the DTB$SERVER account password must match the password of the network object BACKUP$TAPE. So, if the DTB$SERVER password changes, you must execute a two step procedure: 1. Use the NCP utility to change the BACKUP$TAPE object, as follows: $ NCP SET OBJECT BACKUP$TAPE PASS new-password 3-28 Server Software Installation Post-installation Tasks The example above fixes the problem until the system is rebooted. $ NCP DEFINE OBJECT BACKUP$TAPE PASS new-password The example above makes the changes permanent. 2. Next, change the DTB$SERVER account password as follows: $ SET DEFAULT SYS$SYSTEM $ MCR AUTHORIZE UAF> MODIFY DTB$SERVER/PASSWORD=new-password (Note: This is the same as BACKUP$TAPE.) UAF> EXIT $ OPENVMS V6.0 CONSIDERATIONS The following is an extract from the OpenVMS V6.0 release notes that explains the Device Protection changes new to V6.0 that affect StorageWorks Desktop Backup/Archiver: "There is enhanced device protection in OpenVMS VAX Version 6.0. When mounting or initializing a disk or tape volume, the operating system now checks access to the device as well as access to the volume. To initialize or mount a volume on a device, you must have read, write, or control access to the device. System managers and users with the privilege SYSPRV have this type of access." Unless you have read, write or control access to a device, you cannot use it. The default owner of the device in OpenVMS V6.0 is SYSTEM and the default protection is S:RWLP, O:RWLP, G:R, W:. As a result, in OpenVMS V6.0, a non-privileged user, like DTB$SERVER, has no access to a tape device by default. All scheduled operations performed by DTB use the DTB$SERVER account to access the device. There are three workarounds to correct this problem: o Grant a specific ACL on the device which gives read privilege to DTB$SERVER. This is the best solution since it only gives DTB$SERVER access to the devices it needs, but does require the ACL to be applied to Server Software Installation 3-29 Post-installation Tasks each and every tape device it may want to use. Use the following command: SETSECURITY/CLASS=DEVICE/ACL=(IDENTIFIER=DTB$SERVER,ACCESS=READ)device o Change the protection on the tape device so that world (W:) has read privilege. This may be an extreme solution, since it gives all users access to the device. This is not our recommended solution, but it does work. Use the following command: $ SET SECURITY/CLASS=DEVICE/PROTECTION=W:R device o Grant the DTB$SERVER account READALL privilege. This is less extreme than solution 1 above but it still gives DTB$SERVER the READALL privilege to all files and devices on the system when you only want to grant access to a few tape devices. The command to grant READALL in UAF is as follows: UAF> MOD DTB$SERVER/PRIV=READALL/DEF=READALL Desktop Backup/Archiver also includes a DCL interface to the backup server. The DBACKUP SAVE, RESTORE and LIST commands cause the backup server to run in the user's process context, not DTB$SERVER. This means that any user entering these commands requires the same tape device access as the DTB$SERVER account. The options above can be used to provide access for the user's account. VAX RDB/VMS UPGRADES If the version of VAX Rdb/VMS on your system is upgraded at any time, you should make certain that the Desktop Backup Rdb databases are upgraded to remain compatible with the new version of Rdb. The procedure upgrading is normally documented in the release notes that ship with Rdb, but for convenience, it is listed here. The steps you need to take are as follows: From your OpenVMS SYSTEM account, shut down Desktop Backup. This must be done prior to performing the actual Rdb installation. Failure to shut down the Backup Manager process before upgrading Rdb will more than likely result in database files which are unrecoverable (for example, doing an RMU/CONVERT produces the message "%RMU-F- MUSTRECDB, database must be closed or recovered" message, 3-30 Server Software Installation Post-installation Tasks which is extremely difficult and sometimes impossible to recover from): 1. Shut down the StorageWorks Desktop Backup/Archiver as follows: $ @SYS$STARTUP:DTB$SHUTDOWN 2. As a precaution, make copies of your Desktop Backup databases (optional): $ COPY DTB$ROOT:[DB]DTB$HISTORY.RDB - DTB$ROOT:[DB]DTB$HISTORY.RDB_SAVE $ COPY DTB$ROOT:[DB]DTB$SCHEDULER.RDB - DTB$ROOT:[DB]DTB$SCHEDULER.RDB_SAVE $ COPY DTB$ROOT:[DB]DTB$HISTORY.SNP - DTB$ROOT:[DB]DTB$HISTORY.SNP_SAVE $ COPY DTB$ROOT:[DB]DTB$SCHEDULER.SNP - DTB$ROOT:[DB]DTB$SCHEDULER.SNP_SAVE 3. Install the Rdb upgrade. 4. Convert the databases to match the new version of Rdb: $ RMU/CONVERT/COMMIT/NOCONFIRM DTB$ROOT:[DB]DTB$HISTORY $ RMU/CONVERT/COMMIT/NOCONFIRM DTB$ROOT:[DB]DTB$SCHEDULER 5. If there are no problems during the conversion, restart Desktop Backup: $ @SYS$STARTUP:DTB$STARTUP Server Software Installation 3-31 4 ________________________________________________________________ MS-DOS/Windows Client Installation ________________________________________________________________ Overview THE CLIENT INSTALLATION PROCESS Before installing the StorageWorks Desktop Backup/Archiver client software on a client system, the StorageWorks Desktop Backup/Archiver server software must be installed and running. See Chapter 3 for the server installation instructions. Before you begin your installation, it is advisable to refer to the "Pre-Disaster Recovery Setup Procedure for MS-DOS" section of this chapter. That section contains instructions for creating a key disk. The installation procedure described in this chapter calls for the key disk. Once the server software is installed and running, you need to attach to a file service on the machine running the server software and install the appropriate client files to the client machine over the network. The files are located in the DTB$ROOT area on the server. The required files are under the DTB$ROOT logical, and include the client type. For example, the software for an MS-DOS/Windows client is located at SERVER::DTB$ROOT:[CLIENT.DOS]*.*. MS-DOS/Windows Client Installation 4-1 Overview ENSURING PATHWORKS IS SET UP FOR WINDOWS Ensure PATHWORKS is properly set up to run under Microsoft Windows before you use the Windows backup client. For details, see the PATHWORKS installation information. If this installation is not done correctly, a Windows Protection Fault error results. Check the network setup by executing file transfers. o Use the NFT utility on the client and copy a file from the client to the OpenVMS server. NFT is the master; it initiates the file copy. o Use the FAL (File Access Listener) utility on the client PC to copy a file from the OpenVMS server. FAL is the slave; it accepts the copied file. If the test was successful, continue with the installation. ________________________Note ________________________ The Server Kit must be installed and the Backup Manager must be running before the client kits are installed. _____________________________________________________ If the test was unsuccessful, recheck the network setup, then call Digital's Customer Support Center (CSC) at 1-800-354-9000. Desktop Backup will not work correctly unless PATHWORKS is working correctly. MAIL NOTIFICATION WITH PATHWORKS ______________________ Warning ______________________ If a mail notification or a broadcast message is sent to a DOS client, the client hangs when a backup is attempted. You can start the client again by pressing any key, but a backup job scheduled for that client will not run. The client must be rescheduled for a backup. _____________________________________________________ 4-2 MS-DOS/Windows Client Installation Overview To avoid this problem, you can turn off all mail notification in PATHWORKS by typing RCV/T:0 at the command prompt. To turn mail notification back on, type RCV/T:1. WINDOWS CLIENT PRIORITIES Some screen savers on Windows clients run at a higher priority than the Desktop Backup Client, if the Desktop Backup Client is set at medium or low priority. The Windows client should be set at High Priority in the Desktop Backup Client Setup dialog if you are using a screen saver on the client. From the Windows Client Options menu, select Setup... and set the Client Priority Level to High. SERVER COMMANDS FOR SETTING UP A FILE SERVICE The command for setting up a file service on the server is as follows (executed from the OpenVMS prompt on the server): PCSA ADD SERVICE /DIRECTORY service-name /root=logical:[directory] For example: $ PCSA ADD SERVICE /DIRECTORY dtbfiles /ROOT=DTB$ROOT:[CLIENT] The example above creates a file service called DTBFILES, and points to the area on the server that contains the client install files. If you connect to this area from the client system, there are subdirectories for each client type. To grant access to the file service, enter the following command. $ PCSA GRANT /GROUP PUBLIC service-name Now the file service is established and anyone can connect to it. MS-DOS/Windows Client Installation 4-3 Overview CONNECTING TO THE FILE SERVICE FROM THE CLIENT SYSTEM To connect to the file service on the server, use this command from the MS-DOS prompt on a MS-DOS/Windows client: USE ?: \\SERVER-NAME\DTBFILES Then, when you look in the File Manager from Windows (or do a directory of the "virtual drive" from the MS-DOS command line), you will see the subdirectories that point to each of the client types. SETTING UP A FILE SERVICE UNDER PATHWORKS V5.0 FOR MS-DOS Before you begin, log into the OpenVMS server where you are setting up the file service. From the OpenVMS server prompt, use the following steps. 1. Type the following: $ ADMIN 2. Log in using your User id (for example, ADMIN) and Password. Click on OK. 3. Click on OK on the Successful Logon window. 4. From the PATHWORKS LAN Manager menu, use the arrow keys, the mouse, or the Tab key to access the View pull-down menu. Activate the View pull-down menu and select the Shared resources option. 5. To add a file service, click on the AddShare button using the arrow keys, the mouse, or the Tab key. 6. From the "What would you like to share?" pop-up window, select the default option, Disk Directory. Use X for select or 0 for not selected. Click on OK. 7. From the Share a Directory with the Network menu, enter Sharename as whatever you intend to call it, for example, DTB_Files: Sharename: DTB_Files Path: SYS$SPECIFIC:[DTB.CLIENT] Remark: DTB/A V2.x File Service User Limit: X Unlimited Permit 0 Max User 0 Admin Only NOTE: You cannot use blank spaces in the Sharename field. 4-4 MS-DOS/Windows Client Installation Overview Then click on OK. 8. RMS Settings for the file service, for example, DTB_ Files: 0 Personal Share 0 Sequential Fixed X Stream 0 Undefined The file and directory protections must be set as follows. The default protection is "None." Default File Protection Default Directory Protection World: RE World: RE Group: RE Group: RE Sys/Owner: WRE Sys/Owner: WRE Then click on OK. 9. From the File Permission menu, click on the Perm button: - Default Permission: RX - Select the user or groups of users that you want to have access to the file service, then click on the Permit button. - Click on the PrmtTree button to apply the protection to subdirectories and files. The system displays the following message: Permit Tree (this may take some time)? Click on OK to continue. - From the Permit directories only ? message, click on yes. - Click on OK. 10.To return to the File Permissions window, click on OK on the Shared Resources window. Back out of this window and use the View option. Exit application. The system will ask, "Are you sure?" Click on Yes. 11.In Windows, start the File Manager. MS-DOS/Windows Client Installation 4-5 Overview 12.Select Disk/Network Connections ..., for Windows 3.1 or Disk/Connect Network Drive ..., for Windows for Workgroups. 13.In the Network Drive Connections window, enter the Network Path, for Windows 3.1 or enter the Path, for Windows for Workgroups. For example, type the following: \\DTB23\DTB_Files DTB23 is the node name of the OpenVMS server where the file service is set up. 14.Click on the Connect button. Click on the Close button. The file service containing the installation files for the MS-DOS/Windows clients and consoles are added as a new drive. GENERAL PROCEDURE FOR INSTALLING AN MS-DOS CLIENT The general procedure for installing an MS-DOS/Windows client is as follows: 1. Run SETUP.EXE (for Windows) or run INSTALL.EXE (for MS-DOS). 2. Continue (click on the Continue button) the installation and go to the Client Install window. 3. Enter the destination path for the installation and click on the Continue button. 4. You can click on the Set Include Path option to indicate that the files in that path are to be included in the general backup job. The default is as follows: C:\>*.* You can click on the Set Exclude Path option to indicate that the files in that path are not to be included in the backup. The default is as follows: NONE 5. Select the options you want and click on OK. 6. Select none, one, or both of the Windows console options and click on the Continue button. 4-6 MS-DOS/Windows Client Installation Overview 7. Enter the node name of the Backup Manager. 8. Enter the user name for the Backup client, the password twice (the second time as a confirmation), and click on the Continue button. 9. If the information entered for the client is correct, click on the Correct button. MS-DOS/Windows Client Installation 4-7 Client Software Installation ________________________________________________________________ Client Software Installation STARTING SETUP Run SETUP.EXE to begin installing the client software. See Figure 4-1 and follow the instructions on subsequent pages. ________________________Note ________________________ If you are installing an MS-DOS client, without using Windows, run the file INSTALL.EXE from the file service to start the installation program. Using INSTALL.EXE provides a character-cell user interface when installing StorageWorks Desktop Backup/Archiver. The screens look similar to those shown in this guide, and they perform the same function. They look slightly different, however, because they do not use the Windows graphical user interface. _____________________________________________________ 4-8 MS-DOS/Windows Client Installation Client Software Installation Figure 4-1 shows the StorageWorks Desktop Backup/Archiver Introduction window. Click on Continue to proceed with the installation. Figure 4-1 Starting Setup MS-DOS/Windows Client Installation 4-9 Client Software Installation MS-DOS /WINDOWS INSTALLATION WINDOW Figure 4-2 shows the Client Install window. Figure 4-2 Client Installation When you click on the Set Location button in the Install to: section of the Client Installation window, the setup program displays the Destination Path window. 4-10 MS-DOS/Windows Client Installation Client Software Installation CHOOSING THE DESTINATION PATH Figure 4-3 calls for the destination path for the installation. Enter a destination path on the client for the client files. Figure 4-3 Destination Path MS-DOS/Windows Client Installation 4-11 Client Software Installation CHOOSING THE INCLUDE PATH If you clicked on the Set Include Path button on the main client installation screen (see Figure 4-2), setup displays the Include Path window. This is the default include path for this client; that is, when you execute a backup, the files in this path will be included in that backup. See Figure 4-4. Figure 4-4 Include Path 4-12 MS-DOS/Windows Client Installation Client Software Installation LAUNCHER The Launcher is an MS-DOS-loadable terminate and stay resident (TSR) image that allows the backup server to activate the Main Client Image. With these two images-the Launcher and the Main Client Image-a PC can be set for unattended backups. The Launcher is not needed with the Windows client nor the Macintosh client. Both installation procedures (optionally) modify the AUTOEXEC.BAT file of a MS-DOS PC client to start the launcher automatically at boot time. ________________________Note ________________________ Because the Launcher takes memory space, you may choose not to have the installation modify the AUTOEXEC.BAT file, so that the Launcher is not automatically loaded when the PC is booted. It is the Launcher's responsibility to activate the client image. Therefore, if the Launcher is not loaded, you must activate the client image by typing Client at the C:\> prompt. _____________________________________________________ If you select the Modify AUTOEXEC.BAT to Load Launcher TSR option, the AUTOEXEC.BAT file on the client system will be modified so that the launcher Terminate and Stay Resident (TSR) is loaded into memory. The following line is added to the AUTOEXEC.BAT. C:\DTB\LAUNCHER.EXE C:\DTB\ MS-DOS/Windows Client Installation 4-13 Client Software Installation EXCLUDE PATH If you clicked on the Set Exclude Path button on the main client installation screen (see Figure 4-2), setup displays the Exclude Path window. This is the default exclude path for this client; that is, when this client is backed up, the files in this path will be excluded from the backup. See Figure 4-5. Figure 4-5 Exclude Path 4-14 MS-DOS/Windows Client Installation Client Software Installation SELECTING THE MANAGEMENT CONSOLE You can use this client to manage Desktop Backup (as long as you give the associated user the appropriate privileges). You can give the user Administrator privilege, Personal Backups privilege, Personal Restores privilege, and Modify Client Profile privilege. The management console takes advantage of all of the above functions. See the StorageWorks Desktop Backup/Archiver System Administrator's Guide for more details. Figure 4-6 shows the Console Options window. Select none or one of the Windows console options. Figure 4-6 Management Console Selection MS-DOS/Windows Client Installation 4-15 Client Software Installation ENTERING THE SERVER NODE NAME WHERE THE BACKUP MANAGER RESIDES Figure 4-7 shows the system prompt for the node name of the Backup Manager. Figure 4-7 Backup Manager Node Name Enter the node name of the system on which the Backup Manager process resides. The Backup Manager stores information about all clients, users, and backup jobs. See Figure 4-7. 4-16 MS-DOS/Windows Client Installation Client Software Installation ________________________Note ________________________ The Backup Manager is designed to run on a single OpenVMS VAX or Alpha node. Therefore, VAXcluster aliases should not be used as the Backup Manager node name. If you enter an alias, there is no guarantee that either the Desktop Backup/Archiver client software or graphical user interface will be able to connect to the Backup Manager. _____________________________________________________ MS-DOS/Windows Client Installation 4-17 Client Software Installation PROVIDING USER NAMES AND PASSWORDS There is a different screen display for passwords in a Windows client installation versus an MS-DOS client installation. o The non-Administrator username/password pair for a Windows client. During a client installation, you are prompted for another username/password pair for the user who will be associated with that client (this is part of that client system's profile). By default, that user is not granted any privileges. This username/password pair is used to log in to the user interface of the Desktop Backup/Archiver Backup Manager process. o The MS-DOS screen saver password. There is also a screensaver password that can be set on an MS-DOS client, using the CLIENT /P switch from the MS-DOS prompt. This password is only to exit from the Desktop Backup/Archiver screensaver on an MS-DOS client. You can also use the CLIENT /NOPASSWORD switch to avoid using a password to exit the MS-DOS Main Client Image. Enter the user's name assigned to this client, as well as the associated password. See Figure 4-8. Figure 4-8 Client Information 4-18 MS-DOS/Windows Client Installation Client Software Installation CONFIRMING YOUR INSTALLATION CHOICES Before completing the client installation, the system prompts you to confirm your installation selections. If they are correct, click on the Correct button. If they are not correct, click on the Incorrect button. You then have an opportunity to make changes. The system stores all your installation selections, so you need only enter corrections. Figure 4-9 shows your installation selections. Figure 4-9 Installation Confirmation MS-DOS/Windows Client Installation 4-19 Client Software Installation THE CONNECTION PROGRAM After you confirm your installation selections, the installation procedure moves client files from the VAX machine, it then runs the connection program to establish a connection with the Backup Manager. The client and user information are added or modified in the Backup Manager's database. See Figure 4-10. Figure 4-10 Connection to the Server 4-20 MS-DOS/Windows Client Installation Client Software Installation SETUP CREATES A PROGRAM GROUP AND PROGRAM ITEMS When all the installation tasks have been completed, the client setup program creates a Windows Program Group and Items. See Figure 4-11. Figure 4-11 The Desktop Backup Program Group Click on the DTB Client Icon to start the client software. See Figure 4-11. If you selected the Windows Management Console option from the Console Options window (Figure 4-6), the Desktop Backup/Archiver window displays a DTB Management Console icon. Click on the DTB Console icon to start the graphical user interface so that you can manage Desktop Backup. MS-DOS/Windows Client Installation 4-21 Starting the Client Software (MS-DOS Client) ________________________________________________________________ Starting the Client Software (MS-DOS Client) STARTING AN MS-DOS CLIENT To start an MS-DOS client: __________________________________________________________ Type_this..._____This_happens...__________________________ C>\DTB>: CLIENT esktop Backup Client" screen displays so you know that the Main Client Image is running. After a short time, the MS-DOS client pause screen appears, unless you use the following: C\>DTB>: CLIENT/NOPAUSE . _________________See_Figure_4-12._________________________ Figure 4-12 MS-DOS Client Pause Screen CLIENT IDLE STATE When no one is using a MS-DOS client, you can leave it in the "idle state." When the client is idled, it can still be backed up at the date and time defined in the backup job. The idle state locks the client for data protection. 4-22 MS-DOS/Windows Client Installation Manual MS-DOS/Windows Installation Process ________________________________________________________________ Manual MS-DOS/Windows Installation Process NFT COPY If you copy the Windows client files from the file server to the PC using NFT COPY, you should be aware that the following files will NOT be copied correctly if you use NFT COPY/IMAGE or NFT COPY/BLOCK (you must use NFT COPY without qualifiers). Copying these files with the /IMAGE or /BLOCK qualifiers will result in "Initialization List file has been corrupted" messages when attempting the install. o SETUPAPI.INC o DTBSETUP.INF o SETUP.LST Should you require the file DECPW.386, it must be copied using NFT COPY/BLOCK. When using NFT COPY, Digital advises that it be run from MS-DOS, not from the MS-Windows DOS prompt. If you are using PATHWORKS V5, the Windows NFT utility may be used to copy the files from the file server to the PC. NORTON DESKTOP If you are running Norton Desktop for Windows on your PC, you will experience problems using the Desktop Backup Windows Setup procedure to install the software. As a workaround, you must perform the following steps to successfully install the product under Norton Desktop: 1. From the File Menu in the Norton Desktop Manager Menu bar, choose Run... 2. Enter PROGMAN as the command and set the Run Style to Minimized. 3. Click the OK button to start the standard Program Manager. MS-DOS/Windows Client Installation 4-23 Manual MS-DOS/Windows Installation Process 4. Install Desktop Backup following the normal installation procedure as outlined in this guide. 4-24 MS-DOS/Windows Client Installation Manual MS-DOS/Windows Installation Process SOURCE DIRECTORY FOR LOCAL INSTALLATIONS If you elect to copy the installation files to your PC and install locally, rather than from a file service, do not copy them into the same directory in which the product will reside. Doing so results in file access conflicts for the Desktop Backup message file, causing the installation to fail. ________________________________________________________________ Pre-Disaster Recovery Setup Procedure for MS-DOS It is important to prepare each PC on your cluster as you set it up so that if a disaster occurs, you can recover from it quickly. Though your information management specialists may keep these items secured, the following items must be available to whoever is restoring your system: o Key disk built for your version of PATHWORKS o Current system backups (these may be archived to disks on your OpenVMS system or on tapes) The quality of the recovery depends upon how recently your system was backed up. OVERVIEW If you need to replace or reformat the disk that failed and caused the disaster, use the MS-DOS fdisk command. To recover from a catastrophic data loss (reformat the disk, replace the disk, and so forth), on a client, you need to create a bootable diskette (called a key disk) that contains a minimal set of required DECnet files, along with the files necessary for partitioning and reformatting the system disk. You also need to include the Desktop Backup files necessary for a restore operation on your key disk (these files are listed below). MS-DOS/Windows Client Installation 4-25 Pre-Disaster Recovery Setup Procedure for MS-DOS To create the key disk, use the Format Disk option from the disk pull-down menu on the File Manager (if you are using Windows, this option is located on the Main window) and select the Make System Disk option. Put a 1.44 MB diskette in the disk drive and confirm that you want to format the disk. Create the key disk as follows. PROCEDURE FOR CREATING A KEY DISK: PATHWORKS V4.X CLIENT The procedure to create a key disk for V4.x is documented in the PATHWORKS for DOS Client Installation and Configuration Guide with Diskettes. Copy the following files to the root directory of your PATHWORKS key disk: From your default DTB directory (usually C:\DTB\) copy these files: o CLIENT.EXE o DTBCFG.DAT o DTB-MSG.DAT From your DOS directory copy these files: o FORMAT.COM o FDISK.EXE o CONFIG.SYS If you are running MS-DOS V6.0 with PATHWORKS V4.x, you will also need to copy SETVER.EXE from your DOS directory and then edit the CONFIG.SYS file on the key disk adding the following command: device=\setver.exe Once booted, CLIENT.EXE can now be run, waiting for the restore operation to be started by the server. See the procedure at the end of this section. 4-26 MS-DOS/Windows Client Installation Pre-Disaster Recovery Setup Procedure for MS-DOS PROCEDURE: PATHWORKS V5.X CLIENT PATHWORKS V5.x does not provide for a key disk, but one can be made using the PWSETUP program and selecting the DTB/A Key Disk configuration. MS-DOS/Windows Client Installation 4-27 Pre-Disaster Recovery Setup Procedure for MS-DOS Steps: 1. Make a bootable system diskette (either by using the FORMAT/S or SYS command) as follows: C:\>format/s a: 2. Create a PW (PATHWORKS) directory on the diskette as follows: A:\>mkdir a:\pw 3. Copy the CFG0001.TPL file from your default DTB directory (usually C:\DTB\) to the bootable diskette as follows: C:\DTBV21>copy cfg0001.tpl a:\pw\*.* 4. Refer to the PATHWORKS V5.x for DOS and Windows Client Installation and Configuration Guide with Diskettes for the location of the PWSETUP.EXE file on the file service, connect to the file service, and run PWSETUP.EXE follows: E:\PCAPP>pwsetup From the Please Enter Software Destination screen, use the Tab key to advance to the software destination line and modify the destination as follows: a:\pw Press the Return key. The system displays a message as follows: Please insert a diskette into drive A:. As the configuration proceeds, the PATHWORKS software will be copied onto the diskette. Click on OK. The system reads the information from the server. - On the Select a configuration option: screen, select the following: Customize 4-28 MS-DOS/Windows Client Installation Pre-Disaster Recovery Setup Procedure for MS-DOS - On the Customize: Select a workstation template: screen, select the following: DTB/A Key Disk - On the Customize: Modify Workstation Configuration screen, select the following: Under Template, select PATHWORKS Services - On the Customize: Select PATHWORKS Service for workstation screen, select the following and click on OK: DECnet and Utilities Add>> - On the Customize: Additional Startup Commands, leave the screen blank and click on OK. - On the Customize: Additional Startup Commands, select the following: Customize: Hardware Information Then verify that the information is correct. Then click on OK. - On the Customize: Additional Startup Commands, select the following: Network Adapter Information Then choose the appropriate device(s). Then click on OK. - On the Customize: Additional Startup Commands, select the following: DECNET Information Then enter the client and server node name and address information. You can obtain this information when you type NCP from the OpenVMS prompt. - On the Customize: Additional Startup Commands, select the following: Save Template to Disk The system displays the Copying required File screen and shows the percentage of files copied. MS-DOS/Windows Client Installation 4-29 Pre-Disaster Recovery Setup Procedure for MS-DOS - On the Customize: Configuration Completed screen, click on OK to exit. - On the Select a Configuration Option screen, select the following: EXIT 5. Delete the PWICON.EXE and COWHELP.EXE files. Then copy the files listed below. ________________________Note ________________________ If you do not delete PWICON.EXE and COWHELP.EXE before you copy the additional files, you will not have enough space on the disk for all the files that you need to have on your key disk. _____________________________________________________ 6. Copy the following files to the top level of the same diskette: From your default DTB directory copy these files: o CLIENT.EXE o DTBCFG.DAT o DTB-MSG.DAT From your DOS directory copy these files: o FORMAT.COM o FDISK.EXE 4-30 MS-DOS/Windows Client Installation Pre-Disaster Recovery Setup Procedure for MS-DOS IMPLEMENTING DISASTER RECOVERY After a disaster (such as a disk failure) occurs, use these steps. 1. Boot your PC with the key disk in drive A and use the STARTNET command as follows: A:\>\PW\STARTNET The system displays a message as follows: Bad command or file name. Ignore this message. 2. When the system displays the PATHWORKS Configuration Selection Utility screen, select the DTB/A Key Disk configuration. 3. Type CLIENT at the MS-DOS prompt as follows: A:\>client The system displays client interface. 4. Invoke the Desktop Backup/Archiver Management Console on a terminal or system connected to your VAX. 5. Select the drives and files you want to restore on the PC. Use the Restore procedure documented in the StorageWorks Desktop Backup/Archiver System Administrator's Guide. 6. Back on the PC where you are running the Desktop Backup/Archiver client, the system displays the file path and file name of each file as it restore them. 7. When the restoration of the files is complete, reboot your PC without the key disk. All files and data should now be restored to your system. MS-DOS/Windows Client Installation 4-31 5 ________________________________________________________________ Macintosh Client Installation ________________________________________________________________ Overview PRE-INSTALLATION CONSIDERATIONS Before installing the StorageWorks Desktop Backup/Archiver client software on a client system, the StorageWorks Desktop Backup/Archiver server software must be installed and running. See Chapter 3 for instructions. COMMUNICATIONS TOOLBOX The Macintosh client needs the DECnet Communications Toolbox Tool. The DECnet tool is used for the DECnet connections and is available as part of the PATHWORKS for Macintosh Client or from Thursby Software System, Inc. System 6 users note that the ADSP init is needed for the AppleTalk ADSP to work. THE CLIENT INSTALLATION PROCESS Once the server software is installed and running, you need to set up a file service to the machine running the server software and install the appropriate client files to the client machine over the network. The files are located in the DTB$ROOT area on the server. The required files are under the DTB$ROOT logical, and include the client type. The software for a Macintosh client is located at SERVER::DTB$ROOT:[CLIENT.MAC]*.*. Macintosh Client Installation 5-1 Overview CLIENT INSTALLER There is a MacBinary version of the Macintosh client installer (DTB-INSTALLER.MBIN) in the same directory as the file service. If file services are not available, you can download the installer from this directory using NetCopy or a communications program. SERVER COMMANDS FOR SETTING UP A FILE SERVICE Set the root of the file service to: DTB$ROOT:[CLIENT.MAC] The command for setting up a file service on the server is as follows, using the commands from PATHWORKS for OpenVMS (Macintosh): $ admin/msa add volume "DTB Mac Client"/root=dtb$root:[client.mac] $ admin/msa mount "DTB Mac Client" ________________________________________________________________ Installing the Macintosh Client The Macintosh installation procedure copies one or two files to the client system: o Desktop Backup Client, which is the StorageWorks Desktop Backup/Archiver client software o Console software, which is optional Desktop Backup Client is copied into the Startup Items folder on System 7 machines and into the System Folder on System 6 machines. On System 7 machines, the client is run each time the Macintosh is restarted. On System 6 machines, you need to manually start the client (click on the icon) each time the machine is restarted. 5-2 Macintosh Client Installation Installing the Macintosh Client GENERAL PROCEDURE FOR INSTALLING A MACINTOSH CLIENT The general procedure for installing a Macintosh client is as follows: 1. Connect to the file service you set up on the server. 2. Select the items you want to use and click on OK. 3. Click on the DTB Installer icon. 4. Click on OK on the Installer window. 5. Choose to install just the client software or the console as well. 6. Decide where you would like to store the software folder. 7. Enter the manager node name and zone, choose high or low priority for the client, and choose the network type. Note that zone information is not used for DECnet communications. 8. Enter client information, including the user name and password. Make selections for default include and exclude paths for backups and restores of this client. Choose traverse folders if required. Macintosh Client Installation 5-3 Installing the Macintosh Client SELECTING A FILE SERVER Select the file server as shown Figure 5-1. Figure 5-1 Choosing a File Server 5-4 Macintosh Client Installation Installing the Macintosh Client CONNECTING TO THE FILE SERVER AS A REGISTERED USER Connect to the file server as shown in Figure 5-2. Figure 5-2 Connect to the File Server Macintosh Client Installation 5-5 Installing the Macintosh Client SELECT THE ITEMS ON THE FILE SERVER YOU WANT TO USE The system manager will have already installed the server software; you will connect to SERVER::DTB$ROOT:[CLIENT.MAC] item. See Figure 5-3. Figure 5-3 Selecting Items on the File Server 5-6 Macintosh Client Installation Installing the Macintosh Client STARTING THE DESKTOP BACKUP INSTALLER Start the installer program as shown in Figure 5-4. Double-click on the Installer icon to start the installer program. Figure 5-4 Starting the Installer Macintosh Client Installation 5-7 Installing the Macintosh Client THE INSTALL STARTUP SCREEN When you double-click on the Installer icon, you see the install startup screen with the StorageWorks Desktop Backup/Archiver logo. See Figure 5-5. Click on the Continue button to proceed with the installation. Figure 5-5 The Install Startup Screen 5-8 Macintosh Client Installation Installing the Macintosh Client DECIDING WHICH SOFTWARE TO INSTALL You can install just the client software (the program that allows the Macintosh client to be backed up), or you can install both the client software and the management console (the program that lets you have access to the Desktop Backup/Archiver functions). Figure 5-6 Software Choices for Installation Macintosh Client Installation 5-9 Installing the Macintosh Client SELECTING THE LOCATION FOR THE CONSOLE AND CLIENT SOFTWARE Decide in which folder you want the Desktop Backup software to reside. See Figure 5-7. Figure 5-7 Console and Client Software Location Choices 5-10 Macintosh Client Installation Installing the Macintosh Client SETTING CLIENT PARAMETERS Figure 5-8 shows the Client Setup window. Figure 5-8 Settings Enter the name of the OpenVMS VAX node on which the Desktop Backup Manager process is running. Choose a processor utilization setting and a network type. See Figure 5-8. The Backup Manager keeps information on all users, clients, and backup jobs. Macintosh Client Installation 5-11 Installing the Macintosh Client ________________________Note ________________________ The Backup Manager is designed to run on a single OpenVMS VAX node. Therefore, VAXcluster aliases should not be used as the Backup Manager node name. If an alias were used, there is no guarantee that either the Desktop Backup/Archiver client software or graphical user interface will be able to connect to the Backup Manager. _____________________________________________________ High Priority means that once a backup starts, no other work can be done on the machine until the backup completes. Low Priority means that the client will give up the processor so that a user can do other work while a backup is running. ________________________Note ________________________ Modifying files during a backup or restore can cause files to be left in an inconsistent state. _____________________________________________________ 5-12 Macintosh Client Installation Installing the Macintosh Client ENTERING CLIENT INFORMATION Figure 5-9 shows the Client Information window. Figure 5-9 Entering Client Information Enter the user name of the user assigned to this client. Enter also the password, an include and an exclude path. The include and exclude paths are those areas that you want specifically included and/or excluded from backups and restores. Macintosh Client Installation 5-13 Starting the Client Software (Macintosh Client) ________________________________________________________________ Starting the Client Software (Macintosh Client) OVERVIEW Once the client software has been installed, use this procedure for starting the client software. The client software must be running for a backup of this client to take place. STARTING THE CLIENT SOFTWARE: SYSTEM 7.0.X After installation, restart the Macintosh or double-click on the "Client" icon located in the Startup Items folder. STARTING THE CLIENT SOFTWARE: SYSTEM 6.0.X Double-click on the "Client" icon located in the System Folder. COMMON BEHAVIORS AND INFORMATION BETWEEN SYSTEM 6 AND SYSTEM 7 MACHINES The first time the client software is run, a setup dialog displays. This is the same dialog displayed when you choose Setup from the File menu. Enter the name of the OpenVMS node on which the DTB manager process is running and choose a processor utilization setting. "High- Priority" means that once a backup of this client starts, no other work on this client can be done until the backup finishes. "Low-Priority" means that the client gives up the processor so that you can do other work while a backup is running. ________________________Note ________________________ Modifying files during a backup or restore may leave files in an inconsistent state. _____________________________________________________ 5-14 Macintosh Client Installation Pre-Disaster Recovery Set-up Procedures for Macintosh ________________________________________________________________ Pre-Disaster Recovery Set-up Procedures for Macintosh It is important to prepare each Macintosh on your cluster as you set it up so that if a disaster occurs, you can recover from it quickly. Though your information management specialists may keep the following items secured, these items must be available to whoever is restoring your system: o Operating system software disks o PATHWORKS software disks o Desktop Backup/Archiver software disks o Current system backups (these may be archived to disks on your OpenVMS system or on tapes) Type the NCP at the OpenVMS prompt to invoke the Network Control Program Utility and to get the client and server information for each Macintosh on your cluster. You will need this information to implement your disaster recovery procedure. OVERVIEW The quality of the recovery depends upon how recently your system was backed up. PROCEDURE The time that it takes to recover from a disaster (such as a disk failure) depends upon whether the software disks and backups listed above are available to whoever is performing the recovery procedure. If the items are accessible, the disaster recovery can take 30-45 minutes. IMPLEMENTING DISASTER RECOVERY 1. Ensure that the computer and hard drive are functional. Either replace the fixed disk or have it repaired. Macintosh Client Installation 5-15 Pre-Disaster Recovery Set-up Procedures for Macintosh 2. Install the System software. It is advisable to use the same version of the operating system that was on the client before it failed. When the full restore is performed, pieces of the operating system software will be overwritten with the old version unless the System area is excluded from the restore. 3. Run the control panel "Sharing Setup" and set the "Owner Name" and "Macintosh Name" to what they were before the disk disaster. This ensures that the Desktop Backup Manager can locate the client by name using AppleTalk. 4. Install PATHWORKS for Macintosh client software or communications Toolbox tools from Apple's Basic Connectivity Set. This step is necessary so that the install procedure can communicate with the Desktop Backup Manager. If a DECnet connection is used, be sure to set up the DECnet connection using the NCP (Network Control Program) utility. Use the same settings as before the disk disaster. This ensures that the Desktop Backup Manager can locate the client by name using DECnet. 5. Install the Desktop Backup client software. During the installation procedure, the install software will try to register the user name and the client name with the Desktop Backup Manager. This will cause an error since the user and client already exist. Ignore this message. At the point the message is generated, all of the Desktop Backup Client software has been installed. 6. Double-click on "Desktop Backup Client." 7. Perform a full restore. 8. Restart the client to load newly restored control panel, INITs, and startup applications. ________________________Note ________________________ It is possible to create a bootable System 6 disk containing the system, network software, and Desktop Backup Client software. It is recommended, however, 5-16 Macintosh Client Installation Pre-Disaster Recovery Set-up Procedures for Macintosh that you use the above procedure to restore a client to a previous state. _____________________________________________________ Macintosh Client Installation 5-17 ________________________________________________________________ Glossary The terms that appear in the text of this manual in italics are explained in this glossary. Terminology defined in this glossary may be defined differently for the Desktop Backup/Archiver than for other applications and systems. Attended backup A backup is attended if the media must be changed during the backup process. Backup (n.) A copy of the contents of an entire disk, directory, or file. Back up (v.) To copy the contents of an entire disk, directory, or file. Backup job Consists of the specifications needed to back up a group of client systems to a specific tape or disk device (and can specify a date, time, and a repeat schedule). Backup manager Provides the following functions: o Scheduler database o Backup history database o Event logger Glossary-1 o Security Backup server The Backup server is responsible for the following: o Writing the OpenVMS backup saveset o Reading the OpenVMS backup saveset and transmitting the requested files o Creating lists for input into the backup history database o Obtaining lists from the backup history database o Interacting with the host system for media mount and dismount Client A personal computer or workstation, connected to the network, that can access resources on a server. Hardware or software that receives resources from a server. See also server. Compression Compression is a process that converts data into a form that takes less space. Desktop Backup can turn on the compression feature found in many tape drives. Console The manual control unit integrated into the central processor, which enables the operator to start and stop the system, monitor system operations, and run diagnostics. The management console feature of the Desktop Backup /Archiver gives administrator-privileged users access to all functions of the software. The software gives some or all users the ability to do their own backup and restore operations. The user console is a subset of the management console. Destination path The drive, file, or media to which a user is copying or moving information. Also called a target. Glossary-2 Directory tree A directory tree is a group of files and directories that are contained in a directory. The files or directories maybe contained directy or indirectly. Directory A list of a set of files stored on a storage device such as a file service or disk. File server A network program that lets a client connect to available file and printer services. File service Directories, subdirectories, and files on a file server. Users can use network commands from a client to access a file service and then store and retrieve data. A file service provides read/write access to applications and services for many users simultaneously. Full backup A backup of all files on a selected client(s). Group A group is a collection of objects. History The list of savesets with the dates and times they were created. A Backup Administrator can display the history of data. A general user can only display the history for the client system that the user owns. IVP Installation Verification Procedure. Part of the installation procedure. Glossary-3 key disk (n.) A disk that is used to start up the personal computer or workstation and make network connections. The key disk stores files with configuration information, optional user-specific information, and some MS-DOS utilities. The key disk is a type of boot media that can be created. Launcher TSR A function of the Desktop Backup/Archiver software that starts the backup client image when requested and provides both backup and restore services. The Launcher is a TSR (terminate and stay resident) function. This program stays in memory, running in the background, even after the user closes the application. Log/Error log A log is a list or journal of errors and events. PAK Product Authorization Key. Part of the product kit. Privileges The level of access to the system or service that a user is allowed. Also, a characteristic assigned to a user or program that determines what operations the user or program can perform. Resource A service that is available to the client. A source of information or an available means to complete a task. Examples of network resources are applications, file services, disk services, and printers. Resources can be either local or remote. Restore Put back data on a client system. Root directory The boot directory, which contains the operating system. Glossary-4 Saveset A group of files saved as a unit and given one saveset name. There is one saveset per client per job. A job with multiple clients contains multiple savesets. Selective backup A backup of a subset of files on a selected client(s). Server A computer running software that controls access to resources such as file, print, disk, or communications services. See also client. Subset A subset is part of a larger group. Glossary-5 ________________________________________________________________ Index A Client (cont'd) ___________________________ invoking, 2-7 Alpha Server Launcher Macintosh client support, functions, 4-13 2-13, 5-14 running, 2-7 AUTOEXEC.BAT file option switches, 2-7, 2-9 modification by Launcher, password, 4-18 2-7 typical, 1-1 Client Idle State B__________________________ defined, 4-22 Backup Manager, 2-1 Client software connecting to a client, file location on the 4-20 server, 4-7 node name on the MS-DOS Console /Windows client, 4-16 manager, 4-15 Bill of materials, 3-2 Conventions, x C D__________________________ ___________________________ Disk Client space requirements, 3-5 assigned username, 4-18 Distribution kit, 3-2 considerations, option DTB$SERVER account switches, 2-9 change in password, 3-28 considerations, running DTB$SHUTDOWN.COM, 3-28 in idle state, 2-7 considerations, running E__________________________ the Launcher, 2-7 Example destination path, 4-11 installation on a server, Exclude path, 4-14 3-15 exiting the idle state, 2-8 Include path, 4-12 information, 4-18 Index-1 Example (cont'd) Installation (cont'd) installation on a server Installation Verification where no previous Procedure (IVP), 3-6 version is installed, Macintosh client 3-21 file locations, 5-1 Exclude, 5-13 MS-DOS/Windows client, See also Include. 4-1 EXIT of software on a server, Client idle state, 2-8 3-15 Client password, 2-8 order, 2-2 Main Client Image, 2-8 preparation, 3-2 requirements for software F__________________________ on OpenVMS, 3-3 File Service selecting a file server, client commands, 4-4 5-4 server commands, 4-3, 5-2 server software, 2-1, 3-1 structure of the guide, H ix ___________________________ time to install on a Hardware server, 3-15 required configuration, 3-3 L__________________________ I Launcher, 4-13 ___________________________ AUTOEXEC.BAT modification Idle state , 4-13 exiting, 2-8 command to start, 2-8 Image running, 2-7 exiting the Main Client, License 2-8 registration, 3-6 invoking the Main Client, registration procedure, 2-6 3-6 MS-DOS Launcher, 4-13 running the Main Client, M__________________________ 2-6 Macintosh client Include, 5-13 entering client See also Exclude. information, 5-13 Installation starting the installer Backup Manager procedure, program, 5-7 2-1 user name and password, confirmation, 4-19 5-11 connecting to the file Main Client Image server, 5-5 exiting, 2-8 general information, 2-1 invoking, 2-6 Index-2 Main Client Image (cont'd) running, 2-6 R__________________________ Rdb/VMS software N__________________________ minimum version required, Network 3-3 backup solution, 1-1 Registering the product typical clients, 1-1 license, 3-6 ___________________________ S__________________________ OpenVMS software Server minimum version required, installation of software, 3-3 3-15 shut down, 3-28 P__________________________ starting, 3-27 Password typical, 1-1 backup administrator, Setup program group, 4-21 3-29 program items, 4-21 client, 3-29 Software required Desktop Backup for VAX Rdb/VMS, 3-3 Administrator, 3-9 Stand-by idle state DTB$SERVER account, 3-9, exiting, 2-8 3-28 Starting the Setup Program MS-DOS screensaver, 4-18 MS-DOS/Windows, 4-8 non-administrator, 4-18 StorageWorks Desktop Backup structure, 3-29 /Archiver user, 4-18 bill of materials, 3-2 Pre-Disaster Recovery Set- Client considerations, up 2-7 Macintosh client, 5-15 distribution kit, 3-2 Pre-Disaster Recovery Setup for MS-DOS software, 1-1 MS-DOS client, 4-25 installation on a server, Preparation tasks, 3-2 3-15 Prerequisite installation verification software for OpenVMS, 3-3 procedure, 3-6 VAX hardware, 3-3 license registration, 3-6 Product Authorization Key Main Client Image, 2-6 (PAK), 3-2, 3-6 password for the backup administrator, 3-29 password for the client, 3-29 password structure, 3-29 preparation tasks, 3-2 Index-3 StorageWorks Desktop Backup /Archiver (cont'd) T__________________________ prerequisite hardware, Time to install 3-3 the software on a server, product authorization 3-15 key, 3-6 required OpenVMS software V__________________________ , 3-3 VAX Rdb/VMS software SYS$STARTUP_VMS.COM, 3-27 minimum version required, 3-3 upgrades, 3-30 VAXcluster considerations, 3-8 Index-4