Introduction

ARCserve* allows you to backup, copy or restore files to and from Windows NT* workstations, with Client Agent for Windows NT loaded, across the network. The Client Agent for Windows* NT is running as a Windows* NT service which you can start or stop through the service manager or the service admin interface provided by the Client Agent.

Installing Client Agent for Windows* NT

Client Agent for Windows* NT uses the IPX/SPX or TCP/IP protocol. Either one of the following 2 transports must be installed before you can run Client Agent for Windows NT:

• The NetWare* Link (NWLink) transport
• TCP/IP transport

For more information about the transport and its parameters, refer to the Windows* NT User's Guide.

Note: If your Windows* NT Version 3.1 is running NWCS (NetWare* Workstation Compatible Service) or CSNW (Client Service for NetWare*) , please see Section Notes issue #1 before running Client Agent for Windows NT.

Note: If you are running Windows* NT Version 3.5x or 4.0, please see Section Notes issue #2 before running Client Agent for Windows NT.

1. From the workstation where you are going to install the Client Agent, run SETUP.EXE . You will be given some choices on where the Client Agent will be installed. The following files will be installed to the directory you specified:
   • ADMIN.EXE
   • NTAGENT.EXE
   • README.WRI

   A Common group "ARCserve Client Agent for Windows NT" is created with one icon "Client Agent for Windows NT Admin".

2. You need to have ARCserve Version 5.01E or above installed on a NetWare server.

Using the Client Agent for Windows* NT Admin

The Client Agent for Windows NT Admin allows you to view the current activity of the Agent and provides you with IPX and TCP/IP addresses.

The SERVICE button brings up the Service Dialog box, where you can Start, Stop or Pause the Client Agent Service.

The CONFIG button brings up the Configuration Dialog box. You will find the following options:

• Password Security
  You can set individual passwords for extra security. The Password Security is disabled by default.

• Restore Registry
  This setting specifies whether the restore operation needs to restore the NT Registry or not, given that the specific session contains NT Registry files.

• Packet Size Configuration
  You can set the packet size that the agent will communicate with ARCserve. Your options are:
  default
  512 Bytes
  1KB

• Pre / Post Operations
  You can configure batch programs to run prior to and after a backup operation.

• Execution Delay
  You can set the time to wait before the job starts. This allows time for the pre/post applications to finish processing.

You can exclude directories or drives on a Windows NT workstation with Client Agent for Windows NT, so ARCserve will not be able to back them up or browse them from the ARCserve Manager.

To exclude any directories or drives, use a text editor, create a file named ARCAGENT.LOG similar to the one below, containing the names of directories and/or drives to be excluded from the backup. This file must be in the root directory of the C: drive.

C:\letters
D:\mydir
E:

The Client Agent for Windows NT will automatically search for ARCAGENT.LOG before a backup job or browsing.

Client Agent for Windows* NT Features

Client Agent for Windows NT provides the following workstation data management functions:

• Query
  From ARCserve manager, users can browse drives, directories and files on a Windows NT machine with Client Agent for Windows NT. File names are displayed in Long Name format if the file system being queried is HPFS or NTFS.

• Backup
  Windows NT supports FAT, HPFS and NTFS file systems. Client Agent for Windows NT is capable of backing up long filenames, file data, security data, extended attributes and alternate data streams supported under these file systems.

• Copy
  ARCserve Manager can copy files and directories from a Windows NT workstation to a server volume or to the local PC client drive.

• Restore
  Client Agent for Windows NT allows restoring files to a file system different from the one they were backed up from.

  Note: Restoring files backed up from NTFS file system to a FAT file system may result in the loss of security data and extended attributes. Restoring files backed up from FAT to an NTFS file system will generate system default security data for these files.

• Compare
  Client Agent for Windows NT provides a compare function so ARCserve can verify the data written to tape with the data on the local NT machines.

• NT Registry Backup/Restore
  Client Agent for Windows NT allows users to backup/restore the Register information which is stored in the NT system config directory , C:\WINNT\SYSTEM32\CONFIG. Any attempt to backup files in this directory will trigger the checking and backup of Registry files.

  Restoration of the Registry occurs if the Registry_Restore option is turned on and the session which is going to be restored contains the current NT workstation's system config path, C:\WINNT\SYSTEM32\CONFIG. Client Agent for Windows NT restores (swaps) the Registry files in directory \TEMP under Windows NT boot drive.

  Note: Under Windows NT, only users with "administrator" privileges can do complete registry backup/restore. Otherwise, an error message will be generated in Client Agent for Windows NT's status log file.

• NT Event Logs
  Event Log files are also located under the NT system config directory. Client Agent for Windows NT retrieves the contents of event log files and generates files with .BAK extension. For example, Event Log file "SYSEVENT.EVT" will be backed up as "SYSEVENT.BAK" by Client Agent for Windows NT.

  
  Notes

  1. If you are using Windows NT Version 3.1 and have Microsoft CSNW, Client Service for NetWare, installed on Windows NT, a communication time-out (E5042) might occur between Client Agent for Windows NT and ARCserve during a backup operation. This is possibly caused by a fragmentation problem in NWCS. To work around this problem, you can use the Windows NT registry editor to change NWLINKIPX parameters by following the instructions below. For more information on NWCS fragmentation problem, please contact Microsoft technical support. If you do not need NWCS services, removing NWCS from Windows NT will also solve this problem.

     To change the NWLINKIPX parameter:

     1. From a Command Prompt under Windows NT, type regedt32 then press Enter key. This should bring up Windows NT's registry editor.

     2. Focus on the HKEY_LOCAL_MACHINE window inside the registry editor. You should be able to see several subkeys, including HARDWARE, SAM... etc., under HKEY_LOCAL_MACHINE key.

     3. Double click on SYSTEM subkey under HKEY_LOCAL_MACHINE key.

     4. Double click on CurrentControlSet subkey under SYSTEM key.

     5. Double click on SERVICES subkey under CurrentControlSet key.

     6. Double click on NWLINKIPX subkey under SERVICES key.

     7. Double click on PARAMETERS subkey under NWLINKIPX key.

     8. With PARAMETERS key hi lighted, select 'Add Value' under 'Edit' pull down menu. Type in RouterMtu in the Value Name input field. Select REG_DWORD in the Data Type selection. Click on OK.
        Note: RouterMtu is a case sensitive value name.

     9. A DWORD Editor should popup. From Radix group, select Decimal button. Type in 2000 in the Data entry field. Then, click on OK.

     10. You can verify these values on the right-hand side of the window. Select Close under Registry pull down menu to close the registry file. Close Registry Editor.

     11. These updates will take effect after a REBOOT of the NT workstation.

  2. A similar problem may occur when running Client Agent for Windows NT under Windows NT Version 3.5x or 4.0 with or without CSNW installed.

     To work around this problem:

     If your Windows* NT is running under Ethernet network, you can use the NT registry editor to change NwlnkSpx parameters by following the instructions below:

     To change the NwlnkSpx parameter:

     1. From a Command Prompt under Windows NT, type regedt32 then press Enter key. This should bring up Windows NT's registry editor.

     2. Focus on the HKEY_LOCAL_MACHINE window inside the registry editor. You should be able to see several subkeys, including HARDWARE, SAM... etc., under HKEY_LOCAL_MACHINE key.

     3. Double click on SYSTEM subkey under HKEY_LOCAL_MACHINE key.

     4. Double click on CurrentControlSet subkey under SYSTEM key.

     5. Double click on SERVICES subkey under CurrentControlSet key.

     6. Double click on NwlnkSpx subkey under SERVICES key.

     7. Double click on PARAMETERS subkey under NwlnkSpx key.

     8. With PARAMETERS key hi lighted, select 'Add Value' under 'Edit' pull down menu. Type in RouterMtu in the Value Name input field. Select REG_DWORD in the Data Type selection. Click on OK. Note: RouterMtu is a case sensitive value name.

     9. A DWORD Editor should popup. From Radix group, select Decimal button. Type in 2000 in the Data entry field. Then, click on OK.

     10. You can verify these values on the right-hand side of the window. Select Close under Registry pull down menu to close the registry file. Close Registry Editor.

     11. These updates will take effect after a REBOOT of the NT workstation.

     If your Windows* NT is running under Token Ring network:

     1. Run Client Agent for Windows NT with 512 byte packet size. To do so, Check the 512 byte packet size in the Admin Config dialog.

  3. The above registry changes only apply if you are using the NWLink protocol. If you need to associate the NT Workstation and or Server via IP, setup the association as follows:
     1. Assign a static IP address to the Storage Express* using the Configuration option from Central Console.

     2. From Central Console, choose "Set up Login to Workstation."

     3. Choose "Associate Unlisted Workstation" from the button at the bottom of the screen.

     4. In the first box titled "Workstation," place the IP address of the NT Server/Workstation between two @ signs. (@127.1.1.1@)

     5. In the "Net Address" dialog box, put a unique number as the last two digits, and leave the remaining digits as 0.

     6. Enter a Password, if needed.

     7. Type in the netBIOS name of the NT Server/Workstation in the Comments field.

  4. Presently, a Windows* NT node cannot be automatically tracked with ARCserve's Client Tracker NLM. In order to display a Windows NT node address in the ARCserve manager screens, such as Backup or Database, you will need to add a record in the Client database for each Windows NT workstation running Client Agent for Windows NT. Please refer to the ARCserve manual or online documentation pertaining to "Managing Databases" (Client database section).

This applies to:

StorageExpress™ Systems