
				P R O S E R V E  CX

					README


				     Version 1.2

                    

April 26, 1994



Introduction

This README contains up-to-date information that became available after the ProServe CX Administrator's Guide and Installation Guide went to print.  Please read this file along with your guides.

This README file is divided into the following sections:

1.0  Device Driver Support
2.0  New Features
3.0  Known Limitations
4.0  Installation Updates
5.0  Documentation Updates (Administrator's Guide)

1.0  Device Driver Support

ProServe CX operates with the following device drivers:

Device Name				Driver Name Equivalent
Archive (Conner) 2525s				CXQIC.NLM
Archive (Conner) Python 4320, 
  4322, 4324,  4520, 4522			CXDAT.NLM
Exabyte  8200, 8505				CXDAT.NLM
HP 35470A, 35480A, C1520A,
  C2224B/C, C2225A/B, C1521A,			CXDAT.NLM
Tandberg Data - Panther 250/3660, 525/3820, 
  1200/4120, and 2500/4220			CXQIC.NLM
Tecmar QT525/Proline QIC 525, QT-1000/Proline 
  QIC 1000, Proline DAT 2/DataVault 2000, 
  THS-2200/Proline 2200, THS-5000/Proline 5000
  Proline DAT 8/DataVault 8000			CX8MM.NLM		
WangDAT 1300, 3100, 3200, 3400			CXDAT.NLM
Wangtek 5150ES, 5525ES, 51000ES
   95000ES					CXQIC.NLM
Wangtek 6200 DAT				CXDAT.NLM

The devices listed above are supported by the following host adapters:  Adaptec:  1510, 152x, 154x, 164x, 174x, and 274x.  Future Domain:  600, 700, 850, 1650, 1660, 1670, 1680, and 7000EX.
2.0  New Features

The following features are added to this release of ProServe CX:

2.1  Novell NetWare 4.01 Patches
This release of ProServe CX installs and runs successfully on a NetWare 4.01 file server.  However, you must load the following three patches on all NetWare 4.01 file servers that run either CXSERVER.NLM or CXPUMPN.NLM:
	
 	PM401.NLM.    	Patch for NetWare 4.01.
	SPXDDFIX.NLM.   Patch for SPX data delivery during termination and connection 
			request retrys.
	PXFIX2.NLM.   	Patch to handle SPX terminations on non-existent sessions.

NOTE:  When running the Setup program, you should allow it to modify your AUTOEXEC.NCF; otherwise, loading the NetWare patches fails.

2.2  Enhanced Tape Server Functionality
The Tape Server Application includes functionality improvements as follows:

The Operations pull-down menu displays the following new options:

	Backup Network.  Lets you perform an immediate full backup of the Tape Server
	and all registered clients to the default device and media set.   The default backup 
	parameters for this menu option are: 
 
		Backup Parameter		Default

		Include database		Enabled
		Include bindery information	Enabled
		Use h/w compression when available	Enabled
		Append to last media		Enabled
		Unattended		Enabled
		Retry busy files		Enabled
		Treat open files as busy		Enabled	
		The Auto-verify method		Compare Files
		Change files are determined by	Date and Time
		Dynamic Load Balancing 	Automatic

		NOTE:  You cannot change these default settings.

		TIP:  The default device is selected through Select Device under the System 
		menu.  The default media set is created by ProServe CX at startup for that 
		device type.

		Backup Tape Server.  Lets you perform an immediate full backup of the Tape 
		Server to the default device and media set.   The backup parameters for this 
		menu option are identical to the Backup Network menu option.

	 	Restore Tape Server.  Displays a message that directs you to the Auto Recovery
		option in the Tape Server and the Restore option in the Administrator 
		application.  Media Utilities (formerly named Tape Utilities).   Lets you 
		perform one of the following actions to the tape that is currently in the 
		selected tape drive:  Erase, Format, Retension, Identify Tape, or Import Media 
		(new feature).   Import Media lets you import a tape from the default device.  
		You are prompted to select either the default media set, or the named media 
		set on the tape as the the target media set.

		Exit (formerly under the System menu).   Lets you exit and unload the Tape 
		Server.

The System pull-down menu displays the following new options that were formerly found under the Operations menu:

		Select Device.   Lets you select the default device to be used by the Tape 
		Server.

		Add Device.   Lets you add recently installed devices to the device list.

	 	Rotation Management.   Lets you access the media rotation messages.

The Job Management option is removed from the Operations menu in the Tape Server Application and is replaced by the new Status window functionality.  To get job information in the Status window, follow these steps:

1.	Press the left arrow key until you have highlighted the operation that you want to 
	check.

2.	Press the up and down arrow keys to select the desired operation.  

	TIP:  Press the [Page Up] and [Page Down] keys to view all operations in the Status 
	window.  

3.	Select [Enter] to display a new menu that lets you perform one of the following actions 
	on the 	selected operation:

		View Operation Details.  Displays a Details window for a currently executed 
		Backup, Restore, Compare, or Media Import.  
		Suspend Job.  Temporarily halts the selected operation.
		Resume Job.  Resumes the selected operation that was previously halted.
		Cancel Job.  Cancels the selected operation from continuing.

The Alerts menu is a new feature in the Tape Server.  This menu has the following option:

		View Alerts.   Displays currently outstanding alert messages.

3.0  Known Limitations

3.1  NetWare Directory Services TSA
If using the Netware Directory Services TSA (TSANDS.NLM), load only one TSA per NDS tree.  

3.2  Running DOS TSA and CX TSR
Do not load the DOS TSA and the ProServe CX TSR (CXTSR.EXE) at the same time on  the same workstation as workstation lockups can occur.

3.3  Tandberg Tape Drives
You may experience problems using 6150 tapes in Tandberg drives as the block size does not get set correctly.

3.4  Exiting the Tape Server
Do not exit the Tape Server if Jobs are running.  This action cancels the job.

3.5  Destination Directories in the Setup Program
When running the Setup program, if the path of the destination directory to which you are installing ProServe CX is greater or equal to two levels deep, the installation fails with the following error:  "Error creating directory.  Error = 2."

3.6  OS/2 TSA
When running a restore, if the path of the destination directory is deeper than the source path, the tagged files are not restored.

3.7  Using a BUSTEK ASPI Driver
Downing the Tape Server and deleting the database, then starting the Tape Server causes an abend when using a BUSTEK ASPI Driver.

3.8  Powering Off During a Restore
Do not power off your system during a restore as this action may cause an application error.

3.9   Using DOMAIN 
If NetWare's DOMAIN is running, do not close Windows on a workstation when the Administrator is atttached to a NetWare 4.01 file server.  This action causes the file server to abend.  You should unload DOMAIN to avoid this problem.

4.0  Installation Updates

4.1  Novell NetWare TSAs and IPX Drivers
The ProServe CX Setup diskettes contain the following files:

The latest qualified Novell TSAs (OS/2 and NetWare 4.x NDS) and associated files are located on the DOS Client diskette (Disk #4) of the ProServe CX Setup diskettes.  You can decompress these files using the EXPAND.EXE utility found in the Windows directory.  TIP:  Type EXPAND /? for more information on using EXPAND.EXE.  

The TSA directory on the DOS Client Disk contains the following files:

TSA\31X
		SMDR31X.NLM	If the file server running the CX Tape Server is NetWare 3.x, you				must run this NLM for ProServe CX to see any TSA clients on the 
				network.

		TSA311.NLM	Can be run on any 3.11 file server if you want to back up the file 				server as a TSA client.

		TSA312.NLM	This NLM can be run on any 3.12 file server if you want to back
				up the file server as a TSA client.
 
TSA\4X
		SMDR.NLM	If the file server running the CX Tape Server is NetWare 4.x, 
				you must run this NLM for ProServe CX to see any TSA clients on
				the network.

		TSA400.NLM	This NLM can be run on any 4.x file server if you want to back 
				up the file server as a TSA client.  

		TSANDS.NLM	This NLM can be run on any 4.x file server if you want to back
				up the NetWare Directory Services (NDS) database.  Only one of 
				these should be loaded per NDS tree. 
TSA\DOS
		TSA_SMS.COM	This NLM can be run on any DOS machine that you want to back up 
				as a TSA client.

TSA\DOS\4X
		TSA_DOS.NLM	If the file server running the CX Tape Server is NetWare 4.x, 
		WS_MAN.NLM	you must run these NLMs for ProServe CX to see any DOS TSA
				clients on the network.

TSA\DOS\3X
     		TSA_DOS.NLM	If the file server running the CX Tape Server is NetWare 3.x, 
		WS_MAN.NLM	you must run these NLMs for ProServe CX to see any DOS TSA 
				clients on the network.

TSA\OS2
 		TSA_OS2.EXE	These NLMs can be run on any OS/2 machine that you want to back 		TSA_OS2.HLP	as a TSA client.
		TSA_RC.DLL
 
		TSA_OS2.NLM	You must run  this NLM on the file server running the 
				ProServe CX Tape Server application for ProServe CX to see any
				OS/2 TSA clients on the network.

		CAUTION:  After you run the Setup program, be sure to edit your AUTOEXEC.BAT and 
		remove the line that refers to TSA_NDS.NLM.   This step is necessary due to a 
		file name change in the latest version, which is TSANDS.NLM.

The latest IPX drivers that ProServe CX supports are added to Disk  #5 of the Setup diskettes.  To access the IPX drivers, run the two self-extracting executables called WINUP9.EXE and  DOSUP9.EXE.  To install these drivers, refer to Novell's NetWire forum (NDEVREL) on CompuServe or contact Novell at 1-800-638-9273. 

		TIP:   To register to join the Novell NetWire forum, select the Novell Programs
		menu from the main NetWire menu and choose Novell Professional Developers.


4.2  Installing ProServe CX 1.2
When installing version 1.2 and overwriting previous versions of ProServe CX, the existing database is preserved.  If you want to create a new database, you must manually delete the files in each database directory.

4.3  Setup Program User Interface Enhancements
The appearance of the windows and dialog boxes in the Setup program are improved; however, the functionality remains identical to the steps detailed in the ProServe CX Installation Guide.  

The following menus are added to the Setup Main window:  Install, Register, and Help.   These menus provide you with an alternative method for selecting the ProServe CX installation pushbutton options in the Setup Main Window.

Also, added to the Setup Main window is Fast Client User Setup.  This option lets you install the Administrator application and DOS and Windows Clients Pump to a workstation only.

4.4  Client Pump User Interface for DOS, NetWare, and Windows
The Client Pump interface for DOS, NetWare, and Windows displays the name of the Tape Server that is accessing that system.  The Client Pumps also display the last date and time that a full and partial backup of that client was completed by the preferred Tape Server.

4.5  Enhanced Media Set Flexibility (Administrator User Interface)
The Permit access by client option is replaced by the Client use access radio button group in the Media Set Properties dialog box.  The new button selections in the Client use access group are as follows:

		Read/write.  Lets the Administrator grant all client users permission to perform
		backup and restore operations to and from the media set. 

		Read-only.  Lets the Administrator grant all client users permission to perform
		Restore and Compare operations only, from the media set.  Only the Administrator
		may perform Backup operations to the media set.  This setting is the default for
		newly created media sets.

		None.  Prevents client users from performing any operation with the media set. 
		The Administrator has full access.

5.0  Documentation Updates (Administrator's Guide)

5.1  Correction to Chapter 11 
Change the name PRPUMP.EXL to CXPUMP.EXL of Step 1 on page 11-8 of the Administrator's Guide.

5.2  OS/2 2.1 Compatibility
The ProServe CX Administrator and Windows and DOS Client Pumps run as a full-screen application under OS/2 2.1 with the same features and functionality as when running under Windows.

5.3  Running the Workstation Installer on a 4.x File Server
The Workstation Installer (ChkAgent) runs correctly on a 4.x file server only if the following three lines are inserted into the system login script:

	MAP *1=SERVER\VOL:
	MAP S16:=SERVER\VOL:\PROCX\CHKAGENT
	#CHKAGENT

5.4  Database File Extensions
The following table lists ProServe CX database file extensions and their descriptions:

	Extension				Description
	.DBS					System database
	.JBM				 	Job manager state file, including schedule 							queues 
	.STF					Library database state file  
	.DSL				 	Contains a list of the backups that have been							performed with this database
	.MSL	Media Set List File   		List of media set known to Tape Server
	.MSD	Media Set Descriptor File 	Describes a media set
	.PLT	Pump List File 			List of clients currently backed by Tape Server		.PFT	Pump Table File 		Contains all  the sessions (maximum of 256) in							which a client has participated.
	.SIF	Session Information File 	Contains all the information about a session
	.DBB	Database File 			index structure for SIF files

6.0  Troubleshooting

6.1  System DLL Files
The Setup program, Administrator, and Windows Client Pump may not function correctly if your Windows workstation path has corrupt or old DLL files.  The Setup program reports this as a failure to execute the main setup executable file and prints out Error #20.  When this error occurs, the Setup program tells you that a DLL file that Windows is attempting to load is bad.  To solve this problem, you should search your entire path, including directories on your file server (this is a common place for old DLL files).  DLLs that are older than 1991 may not be needed.  Also, if you are not running Windows from a network, there should not be non-NetWare DLLs in your file server's public areas.

