When exclude lists using wildcards are used on NetBackup 7.0 clients on UNIX/Linux, extra files and directories may be incorrectly excluded from a backup.

ALL NETBACKUP 7.0 UNIX/LINUX CLIENTS utilizing exclude lists which include "*" wildcards

A quick summary of the issue(s) covered in this Alert:

If your include list entry contains the asterisk wildcard, the entry may unintentionally match - and exclude - files which only match a substring of that entry.  For example, a common exclusion is *.dbf - but due to this issue, that entry not only matches files ending in .dbf, but also files ending in .db, .d or even a single period (.) - this can lead to a lot of files and/or directories getting excluded which the customer is expecting to be able to restore!

http://seer.entsupport.symantec.com/docs/355972.htm 

Alert has been sent today for NetBackup 7.x (Vmware)

A potential for data loss has been identified with VMware clients that are using Changed Block Tracking (CBT) if a reversion is performed to an older snapshot. This is a VMware issue that in turn affects NetBackup client backups.

More details

http://entsupport.symantec.com/docs/355390

VOS NetBackup, an online tool that simplifies the upgrade and installation process for NetBackup 7.0 customers.

VOS NetBackup, an online tool that simplifies the upgrade and installation process for NetBackup 7.0 customers is great tool.

https://vos.symantec.com

NBU and SF

NetBackup Media Server Decommission Part II

This is very nice application to do the decommissioning of a Media-Server

http://support.veritas.com/docs/346487

DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Media Server Decommissioning Tool for NetBackup 6.5.3.

http://support.veritas.com/docs/346486
DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Media Server Decommissioning Tool for NetBackup 6.5.4. 

http://support.veritas.com/docs/346046
 DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Media Server Decommissioning Tool for NetBackup 6.5.5

Now was very easy to do Decommission of a Media-Server , I did not test yet, But I will try do some test this week.

Who did some testing, can add some comments, would be nice

How to create a blank NetBackup NBDB database

Procedure used to recovery database in case of crash.
Important: the new database should be created in the same path of original database.

Symantec Tech Note:
http://seer.entsupport.symantec.com/docs/284299.htm

Microsoft Exchange Information Store restore fails with error message: "FS_CreateObj() Failed! (0xFFFFFE30:)"

Problem caused because administrative shares are unavailable

Symante Tech Note
http://seer.entsupport.symantec.com/docs/272543.htm

How to configure and use Exchange Granular Restore in NetBackup 6.5.3

Symantec Technote

http://seer.entsupport.symantec.com/docs/316982.htm

Correctly Decommission a NetBackup Media Server

This is a great topic, because nobody know how do this correct.

How to correctly decommission a NetBackup Media Server and remove it from the NetBackup environment
http://support.veritas.com/docs/230047

What is the process for decommissioning a NetBackup 6.5 media server 
http://support.veritas.com/docs/306838

The technotes above are good fonts to consult when is need to do this process

=)

NetBackup Services are randomly shutting down on Windows servers after applying a patch for McAfee McShield 8.5 or 8.7i.

McAfee McShield 8.5 patch 3 and newer as well as 8.7i

NetBackup services randomly shut down including:

• NetBackup Resource Broker Service (nbrb.exe)
• NetBackup Notification Service (nbnos.exe)
• NetBackup Policy Execution Manager Service (nbpem.exe)
• NetBackup Service Layer Service (nbsl.exe)

Active Jobs finish but tapes are not moved from drives back to slots

Active Jobs which need to span media sit at Waiting for next media: Any

Queued Jobs do not go active

The above symptoms can happen once or twice per day and can occur on the smallest or largest installations.  The NetBackup services are shutting themselves down because inter-process sockets are being disconnected.  The processes attempt to reconnect, but are unable to do so, and as a result the processes and services shut down.

These symptoms have been seen on systems running McAfee McShield 8.5 patches 3 and newer and 8.7i with NetBackup 6.0 (all patches) and NetBackup 6.5 (all patches).

Log Files:
12/20/07 01:53:56.227 137 PID:7184 TID:7556 [TAO] ACE_Select_Reactor_Notify::notify [handle=0x1f8]: write to notification pipe handle failed: An existing connection was forcibly closed by the remote host. (10054)
12/20/07 01:53:56.227 137 PID:7184 TID:7556 [TAO] sleep_hook failed: An existing connection was forcibly closed by the remote host.
12/20/07 01:53:56.242 137 PID:7184 TID:920 [TAO] handle_notify_pipe_close - taking action REOPEN
12/20/07 01:54:17.336 137 PID:7184 TID:920 [TAO] handle_notify_pipe_close: failed to re-open notification pipe: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.


Workarounds:
There are several workarounds, any of which can be implemented:
1. Uninstall McAfee McShield 8.5 (or 8.7i) and reboot.  (Simply stopping McShield services is not sufficient.)
2. Roll-back to McAfee McShield 8.0.
3. Rename the McAfee Anti-Virus Mini-Firewall Driver file C:\WINDOWS\system32\drivers\MFETDIK.sys and reboot.  Note that this also removes the functionality provided by this file (port blocking access protection rules and identification of source IP Address for a remote attacker).

Best Practice:
In addition to the workarounds listed above, it is always a best practice to configure McAfee by accounting for NetBackup files in three areas of McAfee.

1. Add NetBackup processes to McAfee's Low-Risk Processes list.  (Master Servers, Media Servers)
2. Add NetBackup directories to McAfee's Exclude list. (Master Servers, Media Servers)
3. Uncheck the McAfee setting Scan files opened for Backup. (Master Servers, Media Servers, Clients)

How to add critical NetBackup Master Server and Media Server processes to McAfee's Low-Risk Processes List.
This same process can be used to add exclusively the bpinetd.exe and bpbkar32.exe process on machines that only run the NetBackup Client Service.

1. Launch the McAfee VirusScan Console.
2. Right-click on On-Access Scanner and select Properties:
 

3. Navigate to All Processes > Processes tab.
4. Switch the radio button to "Use different settings for high-risk and low-risk processes:"
 

5. Navigate to Low-Risk Processes > Processes tab > click Add > click Browse:
 

6. Process by process - add this list of NetBackup processes to the list of Low-Risk Processes:

Processes located in \VERITAS\Volmgr\bin\
avrd.exe - Automatic Volume Recognition Daemon
ltid.exe - NetBackup Device Manager Service
vmd.exe - NetBackup Volume Manager Service

Processes located in \VERITAS\NetBackup\bin\
bpbkar32.exe - NetBackup Backup Engine
bpbrm.exe - NetBackup Backup and Restore Manager
bpcd.exe - NetBackup Connection Daemon
bpcompatd.exe - NetBackup Compatibility Service
bpdbm.exe - NetBackup Database Manager Service
bpdm.exe - NetBackup Disk Manager
bpinetd.exe - NetBackup Client Service
bpjava-msvc.exe - NetBackup Java Authentication Service
bpjobd.exe - NetBackup Job Daemon
bprd.exe - NetBackup Request Manager Service
bptm.exe - NetBackup Tape Manager
nbconsole.exe - NetBackup Administration Console
nbemm.exe - NetBackup Enterprise Media Manager Service
nbevtmgr.exe - NetBackup Event Manager
nbjm.exe - NetBackup Job Manager Service
nbnos.exe - NetBackup Notification Service
nbpem.exe - NetBackup Policy Execution Manager Service
nbproxy.exe - NetBackup Proxy process
nbrb.exe - NetBackup Resource Broker Service
nbrmms.exe - NetBackup Remote Manager and Monitor Service
nbsl.exe - NetBackup Service Layer Service
nbstserv.exe - NetBackup Storage Lifecycle Manager Service
nbsvcmon.exe - NetBackup Service Monitor Service
nbvault.exe - NetBackup Vault Manager Service

Additional Processes:
\VERITAS\NetBackupDB\WIN32\dbsrv9.exe - Adaptive Server Anywhere - VERITAS_NB Service

C:\Program Files\VERITAS\VxPBX\bin\pbx_exchange.exe - Veritas (Symantec) Private Branch Exchange Service

C:\Program Files\VERITAS\VxPBX\bin\monitor_server.exe - Veritas process used when NBU is highly available

7. Once all of the above processes have been added, with Low-Risk Processes selected, select the Detection tab and uncheck When writing to disk and When reading from disk:
 


How to add NetBackup paths to McAfee's list of what not to scan:

1. Within On-Access Scan Properties, select Default Processes on the left column, then select the Detection tab.  Click on Exclusions for the category of What not to scan.

 

2. Click Add and individually browse out to these three locations adding each in turn:

...\Veritas\Volmgr\*                             (be sure to append * to the path once each path has been added)
...\Veritas\NetBackup\*                       (be sure to append * to the path once each path has been added)
C:\Program Files\VERITAS\VxPBX\*   (be sure to append * to the path once each path has been added)

 

3. Within each path excluded, be sure Also exclude subfolders, On read and On write are all checked.
 


How to configure McAfee to not scan files open for backup:

1. Under Default Processes, Low-Risk Processes and High-Risk Processes, click on the Advanced Tab and uncheck Scan files open for backup:
 

Note:  Any machine - master server, media server or client - which is running McAfee should have its McAfee properties modified to disable Scan files opened for Backup.  NetBackup honors the API which is tied to this setting.  Each machine with a NetBackup client installed should be individually modified with this setting unless centralized changes can be made to all clients from a single location (for example, by using McAfee's Event Policy Orchestrator).

For additional information on these settings, please reference McAfee source material:

 http://mysupport.mcafee.com/Eservice/templatepage.aspx?sURL=3

KB55139
Understanding High-Risk, Low-Risk, and Default processes configuration and usage

KB58692
Creating Low-Risk Process exclusions in VirusScan Enterprise

KB55898
Understanding VirusScan Enterprise Exclusions


RESOLUTION:
McAfee has a resolution for the interference introduced by the Mini-Firewall driver mfetdik.sys

McShiled 8.5 - HotFix HF482720 (11 August, 2009)   This HotFix is not publicly available.  A call must be placed to McAfee Support to request the HotFix.

McShield 8.7i - The fix is due in Patch 2 due for release September 2009.  The HotFix and Patch 2 address several issues, one of which is this:

Issue:

In high I/O environments where Access Protection is enabled, a performance degradation symptom could be encountered, appearing as a hang. Internal processing by VirusScan drivers was occurring in a serialized fashion, contributing to a bottleneck when large volumes of I/O are being filtered.

Resolution:

The link and mini-firewall drivers will no longer cause a sequential release of objects containing gathered information on the I/O request.

Note:. Please follow all of McAfee's patch application instructions and reboot recommendations when applying patches.

How to benchmark the performance of the bpbkar process

A good way to determine the theoretical maximum read performance of the bpbkar daemon/process on the client is to run a dev null test. This test is usefully to isolate disk reads performances.

UNIX:
Create: /usr/openv/netbackup/logs/bpbkar directory and the /usr/openv/netbackup/bpbkar_path_tr touch file.

Run:
/usr/openv/netbackup/bin/bpbkar -nocont > /dev/null

example: /usr/openv/netbackup/bin/bpbkar -nocont /home > /dev/null

Note: Running this command will add I/O load to the system.
Before begin test change bpbkar log level to 5

The results can be found in the bpbkar log on the same client that the command was run from. It will give an idea ofhow quickly data is read from the file system being tested.

WINDOWS:
Create: \netbackup\logs\bpbkar folder
Run:
\netbackup\bin\bpbkar32 -nocont > NUL 2>

example: C:\program files\veritas\netbackup\bin\bpbkar32 -nocont E:\ > NUL 2> c:\temp.txt

Note: Running this command will add I/O load to the system.
Before begin test change bpbkar log level to 5

The results can be found in the bpbkar log on the same client that the command was run from. It will give an idea of how quickly data is read from the file system being tested.

http://seer.entsupport.symantec.com/docs/242918.htm

by TOCALS

NetBackup Troubleshoot - Howto

This isn't really a how to, is a quick reference with some commands to use to debug the main problems that happens with NetBackup.


1. Log files
- NetBackup Logs
/usr/openv/netbackup/logs (Unix)
Install_path\NetBackup\logs (Win)
- Unified Logs
/usr/openv/logs (Unix)
Install_path\NetBackup\logs (Win)
- NetBackup Media Manager Logs
/usr/openv/volmgr/debug (Unix)
Install_path\volmgr\debug (win)

Obs.: Media manager Logs need be created.
Be aware with log level, they can increase an fill the directory (File system) and the NetBackup will stop to work.

2. Name Resolution
You need ensure that name resolution is working correctly, verify DNS and DNS reverse.

3. Commands you can use for day by day trouble shooting

- Command to list Process are runing
/usr/openv/netbackup/bin/bpps -x

- All process
/usr/openv/netbackup/bin/bpps -a

- List Jobs
/usr/openv/netbackup/bin/admincmd/bpdbjobs

- Command used to confirm the successful lookup of the client name
/usr/openv/netbackup/bin/bpclntcmd -hn client_name
/usr/openv/netbackup/bin/bpclntcmd -ip client_ip

- Commands used to expire or to calculate a new retention for a media
/usr/openv/netbackup/bin/bpexpdate -m ACB001 -d 0
- Change expiration of copy 2, does not afect copy 1
/usr/openv/netbackup/bin/bpexpdate -backupid eel_0904219764 -d 12/20/2010 08:00:00
-copy 2
- If bpxpdate don't work to expire the media execute the command before use bpexpdate
/usr/openv/volmgr/bin/vmquery -deassignbyid media_ID pool_number stat
- To check pool_number and stat
/usr/openv/volmgr/bin/vmquery -m media_ID

- Command to list configured Storage Units
/usr/openv/netbackup/bin/admincmd/bpstulist -L

- Command to list configured Policies
/usr/openv/netbackup/bin/admincmd/bppllist policy_name -L

- Command used to perform operator functions on drives
/usr/openv/volmgr/bin/vmoprcmd

- Command used to display media status
/usr/openv/netbackup/bin/admincmd/bpmedialist -rl 1

- Script to make a media report
/usr/openv/netbackup/bin/goodies/available_media

- Command to unfreeze medias
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m ACB001

- Text interactive menu to administrate NetBackup when you can't access the GUI.
/usr/openv/netbackup/bin/bpadm

- Command to report media contents of a robotic library
/usr/openv/volmgr/bin/vmcheckxxx -rt tld -rn 1 -list

- Command to inventory a robotic library
/usr/openv/volmgr/bin/vmupdate -rt tld -rn 1 -full [-interactive] -use_barcode_rules

- Command to manager EMM server - bee careful using this command
/usr/openv/netbackup/bin/admincmd/nbemmcmd
This command can be used to list servers, medias, include new servers see nbemmcmd (1M)

- To delete a media manger
nbemmcmd -deletehost -machinename media_server -machinetype media

- To delete a tape
nbemmcmd -deletemedia -mediaid ABC001 -originhost server

- To tell you if which boxes are have a emmserver and if they are reachable
nbemmcmd -getemmserver

- Will let you know if there are any media conflicts
nbemmcmd -listmedia -conflicts

- Will let you know what hosts are seen as media_managers and master servers
nbemmcmd -listhosts

4. Sybase trouble shooting
- Database Files
/usr/openv/db/data (Unix)
Install_path\NetBackupDB\data (Windows)

- Binary Files
/usr/openv/db/bin (Unix)
Install_path\NetBackup\bin (win)

- To create a blank DBDB database for the recovery
http://seer.entsupport.symantec.com/docs/284299.htm

- Database Administration tool (since NetBackup 6.5.2)
/usr/openv/db/bin/dbadm (Unix)
\Veritas\NetBackup\bin\bpadm (Win)

Be careful to use this tool, some operations can stop and destroy database.

5. NetBackup Consistency Check (NBCC) utility
The NBCC command executes the NBCC utility that is used to confirm the integrity of portions of the NetBackup catalog related to tape media. This check includes the review of configured storage units, 5.x volume database hosts, 6.xEMMservers, tape media, and images associated with tape media.
If NBCC detects catalog inconsistencies, it generates a set of output files. It can create a support package bundle of these files by using available system utilities.
More information about the NBCC utility is available in the Using NetBackup Utilities section of the NetBackup Troubleshooting Guide.

By TOCALS

A Quick Reference Card for gathering and viewing NetBackup Unified Logs

NetBackup 6.x introduces a new type of logging, referred to as unified logging. This style of logging is used by new NetBackup daemons, such as the Intelligent Resource Manager (IRM) and the Enterprise Media Manager (EMM) daemons. Unified logs are written to the /usr/openv/logs directory on UNIX systems or the \NetBackup\logs directory on Windows systems. An example of a log file that would be generated would be: 51216-111-990921226-060318-0000000000.log

Some techs to help manage the unified logs
- Quick Reference
http://seer.entsupport.symantec.com/docs/332108.htm

- Some examples
http://seer.entsupport.symantec.com/docs/278059.htm

- How to configure log rotation (prevent full file system)
http://seer.entsupport.symantec.com/docs/279541.htm

- How to change log level
http://seer.entsupport.symantec.com/docs/279929.htm

- How to configure to write in a different directory
http://seer.entsupport.symantec.com/docs/281360.htm

by TOCALS

Status Code: 41 - network connection timed out

The server did not receive any information from the client for too long a period of time. This can occur when a network connection is broken during a backup or restore. This can also occur when a NetBackup timeout is exceeded.

See more:
ftp://ftp.support.veritas.com/pub/support/products/NetBackup_BusinesServer/277695.pdf

By TOCALS

Backup job will be interrupted suddenly on Netbackup server with SEP client installed

Backup job will be interrupted suddenly on Netbackup server with SEP client installed. During backup job working, there is an alert of MAC spoofing detected, and all traffic is blocked after then. Cause: It might be caused by SEP Anti-MAC spoofing fun

You can disable Anti-MAC spoofing on SEPM console:

Clients -> traget group -> Polices -> firewall rules -> Traffic and Stealth Settings -> Enable Anti-Mac spoofing (disable it)

ERR - Can't read a tape block from a backup file.

problems perform restore via rman using oracle database

When the restore using Rman appear erros on dbclient

Dbclient

13:00:53.765 [2196.6784] <16> VxBSAEndData: ERR - EndData unable to successfully close object
13:00:53.765 [2196.6784] <16> xbsa_EndData: ERR - VxBSAEndData: Failed with error:
Server Status: Communication with the server has not been iniatated or the server status has not been retrieved from the server.
13:00:53.765 [2196.6784] <8> close_image: Session being terminated abnormally, cleaning up
13:00:53.765 [2196.6784] <4> close_image: INF - restore FAILED
13:00:53.765 [2196.6784] <4> close_image: INF ---- end of Restore ---

13:00:53.765 [2196.6784] <16> int_ReadData: ERR - Can't read a tape block from a backup file.

Rman Log


ORA-19870: error reading backup piece bk_uiiktc8l7_s21074_p1_t701899431

ORA-19501: read error on file "bk_uiiktc8l7_s21074_p1_t701899431", blockno 21614081 (blocksize=512)

ORA-27190: skgfrd: sbtread2 returned erro

The system's device driver returned an error "13:00:53.765 [2196.6784] <16> int_ReadData: ERR - Can't read a tape block from a backup file"
while NetBackup was writing to removable media

If the media is tape, check for:

A defective or dirty drive, in which case, clean it or have it repaired (refer to the tpclean command for robotic drives).

Defective media. If this is the case, use the bpmedia command to set the volume to the FROZEN state so it
is not used for future backups.

The device has indicated that cleaning is required before further operations are attempted

When the backup/restore appear the message

The device has indicated that cleaning is required before further operations are attempted

Check the log BPTM

13:59:57.843 [552.6660] <2> check_serial_num: serial number match for drive with SCSI coordinates {4,0,5,0}, dos_path <\\.\Tape0>, drive serial number 1310007476, expected serial number 1310007476
14:00:17.843 [552.6660] <16> init_tape: GetTapeStatus() on <\\.\Tape0> (SCSI coordinates {4,0,5,0}), failed, The device has indicated that cleaning is required before further operations are attempted. (1165)
14:00:17.843 [552.6660] <2> db_error_add_to_file: dberrorq.c:midnite = 1245207600
14:00:17.843 [552.6660] <16> io_open: cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-TD4.000, The device has indicated that cleaning is required before further operations are attempted. (1165)
14:00:17.843 [552.6660] <2> send_MDS_msg: DEVICE_STATUS 1 11169 ferro 0004L4 4000013 IBM.ULT3580-TD4.000 2000004 OPEN_ERROR 0 0
14:00:17.843 [552.6660] <2> log_media_error: successfully wrote to error file - 06/17/09 14:00:17 0004L4 0 OPEN_ERROR IBM.ULT3580-TD4.000

Run the manual cleaning of the tape-drive

pack nb_clt_6.5.3 install incomplete.

when you are installing of NB_CLT_6.5.3 and NB_CLT_6.5.3.1 appear message.

preinstall script.
See /usr/openv/pack/pack.history for more details.
/usr/openv/netbackup/client/*/*/client_bin.tar.Z: No such file or directory
cp: cannot create /usr/openv/pack/NB_CLT_6.5.3/save: No such file or directory
cp: cannot create /usr/openv/pack/NB_CLT_6.5.3/save/NB_update.uninstall: No such file or directory
Save of NB_update failed
Pack NB_CLT_6.5.3 install incomplete.


We need to create manually

mkdir /usr/openv/pack/NB_CLT_6.5.3/save/

mkdir /usr/openv/pack/NB_CLT_6.5.3.1/save/

Execute the installing again

Status code 9 when backing lotus note

Check the bpbkar log from client.

Bpbkar

10:54:05.938: [3508.4052] <4> tar_backup::V_SetupJobData: INF - dwJobData: ffffffff
10:54:05.938: [3508.4052] <4> tar_backup::V_SetupJobData: INF - dwJob: ffffffff
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - user name: root
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup
10:54:05.953: [3508.4052] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D:
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: VMware Shared Folders
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Web Client Network
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
10:54:06.156: [3508.4052] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
10:54:06.281: [3508.4052] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = D:\Program Files\Lotus\Domino\data
10:54:06.281: [3508.1940] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
10:54:07.297: [3508.4052] <4> UpdatePath(): INF - Path updated with Lotus Program Dir 'D:\Program Files\Lotus\Domino\nserver.exe'
10:54:07.297: [3508.4052] <2> tar_base::V_vTarMsgW: FTL - The NetBackup Extension for Lotus Notes is not properly installed:SetCurrentDirectory (WIN32 267: The directory name is invalid. )
10:54:07.297: [3508.4052] <2> tar_backup_vxbsa::add: INF - called with 'D:\Program Files\Lotus\Domino\data'
10:54:07.297: [3508.4052] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 9: an extension package is needed, but was not installed
10:54:07.297: [3508.4052] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
10:54:07.297: [3508.4052] <4> OVStopCmd: INF - EXIT - status = 0
10:54:07.297: [3508.4052] <2> tar_base::V_Close: closing...

Check some steps

* The most common cause of Status 9 on Lotus Notes backup is incorrectly configuring the INI and PATH information. To add/modify the registry values using REGEDIT32:

1. Click on the Windows Start menu and click Run. In the Run box, type REGEDT32 and press Enter.
2. Select the HKEY_LOCAL_MACHINE key, and navigate the tree and select the SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config key
3. Click on the Config key.
4. Look for a LOTUS_NOTES_PATH value - if it does not exist, from the Edit menu, select Add Value. If it does exist, double-click on it and go to step 7.
5. Set the Value Name to LOTUS_NOTES_PATH.
6. Select REG_SZ for the Data Type, and press OK to add the value.
7. Enter the value data. This is the full directory path to where the nserver.exe file is located. So if, for example, in the environment, the nserver.exe file was located in D:\Lotus\Domino, the value for the LOTUS_NOTES_PATH would be D:\Lotus\Domino.
8. Press OK to accept the value.
9. Repeat steps 4 to 8 for the LOTUS_NOTES_INI value. Please note the value for the LOTUS_NOTES_INI value is the full directory path to the notes.ini file, along with the file name. So if, for example, in your environment, the notes.ini file was located in D:\Lotus\Domino, the value for the LOTUS_NOTES_INI would be D:\Lotus\Domino\notes.ini.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.


* Look to see if there are multiple copies of the files named js32.dll and nlsccstr.dll available to NetBackup (tm). In some cases, the NetBackup for Lotus Notes agent initiates, using older versions of these files found in the C:\winnt\system32 directory, causing the Status 9 error. By default, these files are not located in C:\winnt\system32 after a base Windows install.


By using the third party utility Dependency Walker (http://www.dependencywalker.com/), Support was able to determine that the nnotes.dll (from Lotus) and the nblotusnotes.dll (from Veritas) files were searching for and using two different versions of the same file names from different locations.

The nnotes.dll file (a Lotus installed binary used by NetBackup during the backup and restore process) was looking for the js32.dll and nlsccstr.dll files, and finding them in the d:\lotus\domino directory. In contrast, the NetBackup nblotusnotes.dll file was looking for them in the c:\winnt\system32 directory. Furthermore, when Dependency Walker was run against the nblotusnotes.dll file, both the js32.dll and nlsccstr.dll files displayed in red, indicating a problem with the relationship between NetBackup and the relative version of these DLL files.

Resolve this by renaming the js32.dll and nlsccstr.dll files in the c:\winnt\system32 directory to js32.old and nlsccstr.old, and then copy js32.dll and nlsccstr.dll from the :\lotus\domino directory into the C:\winnt\system32 directory.

make clearing the path and ini path in the client's properties

host properties -> client properties -> Windows Client -> Lotus Notes
clear the Lotus Notes Path and Lotus Notes INI Path fields