Problem

A basic introduction to the NetWare for NetBackup client (Target and Non-Target versions)

Solution
Default locations for install paths for NBU for NetWare NetBackup NLMs SYS:\VERITAS\NBUCLT - NetBackup 5.0 onwards Target file locations SYS:\VERITAS\NBUCLT\NETBACK\TGTS - NetBackup 5.0 onwards Log Locations SYS:\VERITAS\NBUCLT\NETBACK\LOGS - NetBackup 5.0 onwards Note: There is no bpbkar log for NetWare, the BPCD log combines the bpbkar and bpcd logs into one log. This should be the log you request when troubleshooting issues on the client. Default installation paths for the client SYS:\VERITAS\NBUCLT - NetBackup 5.0 onwards Common files to request from the customer 1 - A copy of the bp.ini. This is found in the SYS:\VERITAS\NBUCLT directory on the NetWare client 2 - A config.txt, this can be generated by typing Load Config /all at the console prompt of the NetWare server. This file will be created in the SYS:\SYSTEM directory. The config module is a similar utility to NBSupport. The output will produce a complete configuration of the client. There is no progress indication to show when the config file creation is complete, it will be necessary to monitor the size of the config.txt and wait for the file size to stop increasing. 3 - A copy of the BPCD log

4 - A copy of the Abend.log (if applicable) from the SYS:\SYSTEM directory. This is the equivalent of a Windows crash dump. Target version common "gotchas" If the backup is returning a status 71, check the policy type on the Master server is set to Standard and not NetWare. If the policy type is set to Standard, then check the password on the account being used to create the target files has not been changed (usually this will be the admin account). If the password has been changed, then it will be necessary to reconfigure the targets to reflect the new password. If the common target logon feature is used to create the target and the password for that account changes then it will be necessary to reconfigure all targets using this logon method. Don't copy target files between servers, some information in them is encrypted and is server specific. Always create new targets on each server. The same is true for the bp.ini file. Non-Target common "gotchas" The Non-Target client software installed on a Windows PC will not run unless IPX is running on the NetWare client and also loaded on the Windows machine. If the customer wants to run NetBackup for NetWare on an IP only network they will have to use the Target method which supports the use of IP. Make sure that a drive is mapped to the SYS volume of the server you wish to back up from the Windows PC where the Non-Target software is installed. If the backup fails with a status 71 check the policy type is set to NetWare and also check the files list, there should be a string such as /SERVER/SERVER.NetWare File System/SERVER/VOL The W in NetWare must be a capital letter. General Suggestions If the backup is failing and the configuration appears OK, the running an SMDR NEW command at the NetWare server console might be useful. Ensure that the TSA related NLMs are unloaded prior to doing this (you can run the command SMSSTOP to do this and then run SMSSTART after the recompilation). The SMDR NEW command will reconfigure the SMDR.CFG. SMDR is short from Storage Management Data Requester and information is sent via this NLM to the archive engine (i.e. NetBackup) by the TSAs (Target Service Agents). Occasionally problems occur with sending data via SMDR and recompiling it can cure the problem.

NetWare and NetBackup compatibility Below is a list of which versions of NetWare are supported by NetBackup, All are supported with the GA release unless otherwise stated. For details on caveats, please refer to the compatibility lists at http://support.veritas.com

NetBackup 5.x NetBackup 6.0 NetBackup 7.0 5.1 6.0 6.5 5.1 6.0 6.5 6.5

Tuning NetBackup on NetWare systems This is one of the most common questions asked. Below are links to some tuning documents and other suggestions that may help.

If possible either turn off any anti virus software during the backup, or set the scan engine to scan inbound traffic only (we have had some big issues with the Mcafee scanner in the past) Turn off OFM if possible Check the LIST_FILES_TIMEOUT value (especially on NT Master Servers) and ensure that this value is at least 1800 It may also be worth setting the buffer size in the bp.ini to a larger value, the default is 16 so an increase to 32 or 64 can be beneficial Set the debug level to 0 in the bp.ini

The bp.ini file This is the file that contains the configuration settings for NetBackup on the NetWare client. It

can be edited using any text editor. Below is information on the most common sections that will need adjusting. [bp] Buffer_Size = 32 32 is the default, this can be increased to try and improve throughput. A setting of 64 usually helps Use_Archive_Bit = yes Set this to No to run backups based on last touched time for files.

NW_Uncompress = no Set this to Yes if you want data to be uncompressed when being transferred to tape. This is useful if restoring data to an uncompressed volume, backup times will be slow however. [debug] Level = 0 This section is for setting the verbose logging level. The ranges are from 0 (minimum) to 2 (maximum) [otm] Cache_File = By default this is the SYS volume, a lot of the time the SYS volume is not large enough to accommodate the cache file so it can be moved to another volume by entering the location here. If you only enter a volume name the cache will be placed on the root of that volume. Cache_Control = 0 Cache_Size_Init = 10 Cache_Size_Max = 50 Error_Control = 0 Logging = 0 Quiescent_Wait = 5 Quiescent_Timeout = 60 Current = 0 Exclude = 0 Sync_Timeout = 60 Use = yes To disable OTM just set this to No. All other OTM settings can be manipulated the same way as Windows clients. After any changes are made to the bp.ini, the BPCD.NLM will need to be unloaded and reloaded on the client. Note: After the release of NetBackup 5.0 OTM was replaced by OFM and the cache is managed

dynamically. There is only one entry in the bp.ini under the [ofb] section which is Use = yes Changes to Configuration File Settings for the Open File Backup Option It is strongly recommended that you use the default settings for the Open File Backup Option. However, if you need to modify configuration information, you can use a text editor to edit the configuration files:

NetWare System Component Configuration (OFMNW.CFG)

NetWare NSS Configuration (OFMCDM.CFG)

Some parameters in the two configuration files are for internal use only and should not be modified. The NetWare NSS Configuration file is located in SYS:\SYSTEM. Both the NetWare System Component Configuration file and the NetWare Pass-Through Agent Definitions file are located in SYS:\SYSTEM\OFM. The Tech note below gives further information on modifying the above files (the document refers to Backup Exec but the files are the same for NetBackup). http://support.veritas.com/docs/268831 The NetBackup NetWare Loadable Modules (NLMs) These are listed below BPCD.NLM - The NBU client service BPSRV.NLM - Only needs to be loaded if doing non-target backups BP.NLM - Loads the NBU interface on the client