Is it possible to connect autoloader to virtual machine? autoloader will be connected to ESXi box physically. Can my vm in the ESXi see the autoloader and use it. RHEL is running on virtual machine

Need some info on Netbackup logs

What are the logs that consumes most of Netbackup server processing power? That I should be careful when I turned them on

What is the maximum and minimum verbose level settings? what is the optimal level of verbose setting?

Can netbackup archive those logs automatically at periodic intervals?

All

I am new to the Netbackups world and I have been researching an issue I have had since I began.

I am using NB 7.6.1.1 with 1 MAster and 1 Media Server.

Open Storage: Data Domain DD690

When policies are running they are only running off of the Master server so it seems like the Load Balancing is not working. I have verified the Storage unit's properties are set to use any media server available.

Hi,

I have a master server & a media server which is connected with tape drive . my master server is crashed & i need to rebuild with the catalog file . I have a DR file in email.

I have rebuilt the master server & copied the dr file to the server but when i run the bprecover -wizard command i get below error

ERR - Failed to execute command /usr/openv/netbackup/bin/bptm -restoretir -jobid 9 -cn 1 -b inhyizvmnbms001_1436689282 -c inhyizvmnbms001 on host INHYIZBKPSRV01 (40)

here - inhyizvmnbms001 is my master server

INHYIZBKPSRV01 - media server

Hi to everyone!

Have Symantec Netbackup 7.6.0.1

Master server installed on VM (Win Server 2008 R2).

Media server installed on physical host (Win Server 2008 R2).

Huawei VTL6900 emulating MSL4048 connected to media server via SAN switch.

VTL is detected on media server's OS as MSL autoloader and 4 tape drives (installed drivers from HP on media server).

Symantec Device configuration wizard fails to discover tape library.

Any ideas? What should I check first?

Hi folks, i have a little problem...

Everyday my TLD have status down, and my backups they are not made.

I do not know what to do.

chek this out.

before comand to drive up....

D:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -d
Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   QUANTUM.ULTRIUM5.000 hcart2 TLD(0)  DRIVE=1
      {3,0,3,0}                                                        UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = {3,0,3,1}

EMM Server = srv-***-nbkp.***

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================

D:\Program Files\Veritas\Volmgr\bin>vmoprcmd.exe -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart2   TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 QUANTUM.ULTRIUM5.000  No       -

D:\Program Files\Veritas\Volmgr\bin>

======================================================================

D:\Program Files\Veritas\Volmgr\bin>tpautoconf.exe -t
TPAC60 QUANTUM ULTRIUM 5       3210 HU1305UFMM 3 0 3 0 Tape0 - -

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================

D:\Program Files\Veritas\Volmgr\bin>scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 3; Bus: 0; Target: 3; LUN: 0
Inquiry    : "QUANTUM ULTRIUM 5       3210"
Vendor ID  : "QUANTUM "
Product ID : "ULTRIUM 5       "
Product Rev: "3210"
Serial Number: "HU1305UFMM"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 10
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 3; Bus: 0; Target: 3; LUN: 1
Inquiry    : "DELL    PV-124T         0091"
Vendor ID  : "DELL    "
Product ID : "PV-124T         "
Product Rev: "0091"
Serial Number: "CC3BH60676"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "DELL    PV-124T         CC3BH60676"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-2
Number of Drives : 1
Number of Slots  : 8
Number of Media Access Ports: 0
Drive 1 Serial Number      : "HU1305UFMM"
Flags : 0x0
Reason: 0x0

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================

D:\Program Files\Veritas\Volmgr\bin>vmoprcmd.exe -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart2   TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 QUANTUM.ULTRIUM5.000  No       -

D:\Program Files\Veritas\Volmgr\bin>

*======================================================================

D:\Program Files\Veritas\Volmgr\bin>vmglob.exe -listall
=====================================================================
device type:               robot
device name:               ROBOT0
serial number:             CC3BH60676
hostname:                  srv-***-nbkp.***
volume database hostname:  srv-***-nbkp.***
robot number:              0
robot drive number:        -1
robot type:                TLD
drive type:                -
flags:                     0x0
worldwide name:            -
worldwide name type:       0
inquiry:                   DELL    PV-124T         0090
library name:              -
vendor drive name:         -
robot control host:        -
ACS:                       -1
LSM:                       -1
PANEL:                     -1
DRIVE:                     -1
=====================================================================
device type:               drive
device name:               QUANTUM.ULTRIUM5.000
serial number:             HU1305UFMM
hostname:                  srv-***-nbkp.***
volume database hostname:  srv-***-nbkp.***
robot number:              0
robot drive number:        1
robot type:                TLD
drive type:                hcart2
flags:                     0x0
worldwide name:            -
worldwide name type:       0
inquiry:                   QUANTUM ULTRIUM 5       3210
library name:              -
vendor drive name:         -
robot control host:        -
ACS:                       -1
LSM:                       -1
PANEL:                     -1
DRIVE:                     -1
=====================================================================

D:\Program Files\Veritas\Volmgr\bin>

*=====================================================================

D:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -emm_dev_list
==============================================================================
Robot:                          ROBOT0
Robot Number:                   0
Robot Type:                     TLD(8)
Media Server:                   srv-***-nbkp.***
Port:                           3
Bus:                            0
Target:                         3
Lun:                            1
PartiallyConfigured:            0
Pird:                           0
Host:                           -
Apath:                          -
NDMP Attach Host:               -
VMhost:                         srv-***-nbkp.***
DAhost:                         srv-***-nbkp.***
SN:                             CC3BH60676
Inquiry:                        DELL    PV-124T         0090
WorldWideId:                    -
Old DAhost:                     srv-***-nbkp.***
RSM GUID:                       00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive:                          QUANTUM.ULTRIUM5.000
Index:                          0
Drive Type:                     hcart2(10)
Media Server:                   srv-***-nbkp.***
Occupy Index:                   0
Opr Count:                      0
Status:                         2
Saved Mode Bits:                0
Access Mode:                    82
Robot Type:                     TLD(8)
Robot Number:                   0
Loc1:                           1
Loc2:                           -1
Loc3:                           -1
Loc4:                           -1
Loc5:                           0
Port:                           3
Bus:                            0
Target:                         3
Lun:                            0
VH Saved Mode Bits:             0
Flags:                          0
PathFlags:                      0
DeviceFlags:                    0
Time Mounted:                   0
Total Time Mounted:             66
Cleaning Frequency:             0
Last Time Cleaned:              0
Vendor Device Num:              0
Tape Alert 1:                   0
Tape Alert 2:                   0
Last DA Call Time:              0
Application Type:               0
Drive Path:                     -
Volume Header Drive Path:       -
Vendor Drive Name:              -
Current RVSN:                   -
Current EVSN:                   -
Current User:                   -
Operator Comment:               -
SN:                             HU1305UFMM
Inquiry Info:                   QUANTUM ULTRIUM 5       3210
World Wide Id:                  -
NDMP Host:                      -
Scan Host:                      -
Assign Host:                    -
RSM GUID:                       00000000-0000-0000-0000-000000000000
APPL_GUID:                      00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Master Server:                  srv-***-nbkp.***
NetBackup Version:              7.6.1(761000)
Host OperatingSystem:           11
MachineState:                   ACTIVE
==============================================================================
Virtual Machine Host Name:           srv-vcsa-***.***
Virtual Machine Type:                VMware Virtual Center Server
SubType:                             (1)
User Id:                             ***\usr_netbackup
Required Port:                       443
==============================================================================
EMM Server:                     srv-***-nbkp.***

D:\Program Files\Veritas\Volmgr\bin>

Hi I'm getting this error while backking up one of my client..Need a solution for this.will some one help me in it....

7/14/2015 3:39:51 AM - Info nbjm(pid=6864) starting backup job (jobid=1470955) for client ETW-DBS000261.testeis.tweis.net, policy PROD_Win_Physical, schedule Full  
7/14/2015 3:39:51 AM - Info nbjm(pid=6864) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1470955, request id:{0D0F81F0-D79F-4322-8782-C54293937F2A})  
7/14/2015 3:39:51 AM - requesting resource OSTBackup
7/14/2015 3:39:51 AM - requesting resource epw-inf000048.tw.tweis.net.NBU_CLIENT.MAXJOBS.ETW-DBS000261.testeis.tweis.net
7/14/2015 3:39:51 AM - requesting resource epw-inf000048.tw.tweis.net.NBU_POLICY.MAXJOBS.PROD_Win_Physical
7/14/2015 3:39:51 AM - granted resource epw-inf000048.tw.tweis.net.NBU_CLIENT.MAXJOBS.ETW-DBS000261.testeis.tweis.net
7/14/2015 3:39:51 AM - granted resource epw-inf000048.tw.tweis.net.NBU_POLICY.MAXJOBS.PROD_Win_Physical
7/14/2015 3:39:51 AM - granted resource MediaID=@aaaab;DiskVolume=ost_emcdd01_stu;DiskPool=OSTBackupPool;Path=ost_emcdd01_stu;StorageServer=usw_eib_emcdd01_9021.tweis.net;MediaServer=epw-inf000048.tw.tweis.net
7/14/2015 3:39:51 AM - granted resource OSTBackup
7/14/2015 3:39:51 AM - estimated 0 Kbytes needed
7/14/2015 3:39:51 AM - begin Parent Job
7/14/2015 3:39:51 AM - begin Snapshot, Start Notify Script
7/14/2015 3:39:51 AM - Info RUNCMD(pid=33876) started            
7/14/2015 3:39:51 AM - Info RUNCMD(pid=33876) exiting with status: 0         
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Start Notify Script; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Step By Condition
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Step By Condition; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Stream Discovery
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Stream Discovery; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Read File List
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Read File List; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Create Snapshot
7/14/2015 3:39:51 AM - started process bpbrm (26140)
7/14/2015 4:09:52 AM - Error bpbrm(pid=26140) bpcd on ETW-DBS000261.testeis.tweis.net exited with status 23: socket read failed   
7/14/2015 4:09:52 AM - Info bpbkar32(pid=0) done. status: 23: socket read failed       
7/14/2015 4:09:52 AM - end writing
Status 23
7/14/2015 4:09:52 AM - end Snapshot, Create Snapshot; elapsed time: 0:30:01
7/14/2015 4:09:52 AM - begin Snapshot, Stop On Error
Status 0
7/14/2015 4:09:52 AM - end Snapshot, Stop On Error; elapsed time: 0:00:00
7/14/2015 4:09:52 AM - begin Snapshot, End Notify Script
7/14/2015 4:09:53 AM - Info RUNCMD(pid=17276) started            
7/14/2015 4:09:53 AM - Info RUNCMD(pid=17276) exiting with status: 0         
Status 0
7/14/2015 4:09:53 AM - end Snapshot, End Notify Script; elapsed time: 0:00:01
Status 23
7/14/2015 4:09:53 AM - end Parent Job; elapsed time: 0:30:02
socket read failed(23)

Hi, 

I'm trying to automate  SqlServer Backups by executing from control-m, which is a 3rd party schedule software. 

To do this, I have created a .bat file that call the Netbackup exec file (dbbackex.exe).  

I use this code to do this: 

echo "Starting SqlServer Backup on  %COMPUTERNAME% "> C:\backuplog.log
"C:\Program Files\Veritas\NetBackup\bin\dbbackex" -f C:\bcktest.bch -p nopr_bdd_msql_all -s back -np >> C:\backuplog.log

echo %date% %time% >> C:\backuplog.log
echo "Backup Finished ">> C:\backuplog.log

IF %ERRORLEVEL% GTR 0 echo "Backup Finished with ERROR [%ERRORLEVEL%]">> C:\backuplog.log
IF %ERRORLEVEL% EQU 0 echo "Backup Finished SUCCESSFULLY">> C:\backuplog.log

echo "Review log file:  C:\Program Files\Veritas\NetBackup\logs\user_ops\MsSql\Logs">> C:\backuplog.log

I would like to get the ERROR message, not only the code, using this script and if not possible, get dbclient log name to complete the last line and show something like:

Review log file:  C:\Program Files\Veritas\NetBackup\logs\user_ops\MsSql\Logs\0714115143814-55584-20776-000-000-prg

Does anyone know if this is possible and how could I do this? Or is it possible to configure de path and logfile name?

Other posibility I'm thinking of is manage error codes on my own, but I would need Error code list and cannot find it. Does anyone know if this exist?

I would accept any other suggestion to get error information. I cannot use any other code but cmd/bat. 

Thanks in Advance, 

Elena 

i'm looking to back up a single 40TB drive using netbackup 7.7, utilizing multistreaming.

This needs to be a single job, backing up to multiple tape drives at once.

is there any way to back up the whole data without splitting into seperate folders?

hi, i am running backup jobs with various settings. somehow, i couldn't able to submit the job with more than 2GB of shared memory buffers size.

I am using disk based storage unit (basic). number of concurrent jobs set to 24

I have set SIZE_DATA_BFFER to 256 KB (i.e 256*1024)

I couldn't set NUMBER_DATA_BUFFERS to more than 8200 (just a rought estimate). working fine with 8150 setting.

My netbackup server RAM is 256 GB

I've set shared memory at 128 GB at OS level

 /usr/openv/netbackup/bin/bpbackup -p Gen_Test -s Gen_Test -w GEN_DATA GEN_KBSIZE=2000 GEN_MAXFILES=500 GEN_PERCENT_RANDOM=100
EXIT STATUS 89: problems encountered during setup of shared memory

That means, it is not allowing me use more than 2GB (approx) of shared memory per job. here is the bptm log

16:22:22.913 [7969] <2> io_set_recvbuf: setting receive network buffer to 262144 bytes
16:22:22.913 [7969] <2> read_legacy_touch_file: Found /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS; requested from (tmcommon.c.3525).
16:22:22.913 [7969] <2> read_legacy_touch_file: 8200 read ; requested from (tmcommon.c.3525).
16:22:22.913 [7969] <2> io_init: using 8200 data buffers
16:22:22.913 [7969] <2> io_init: child delay = 10, parent delay = 15 (milliseconds)
16:22:22.914 [7969] <16> create_shared_memory: could not allocate enough shared memory for backup buffers, Invalid argument

so, is there any maximum cap on amount of shared memory that can be used per netbackup job

Hello Everyone,

We have a windwos 2008 -  file server with 8 A,B,C,E..etc.,drives,

Netbackup client version is 7.1 / Netbackup master/media version - Solaris 10 - 7.6.0.1 / Storage Target  - DataDomain

We have multistreaming enabled.

Incrmental backup completes successfully for this file server.

However whenever full backup runs, 2 drives always fail with code 13, 24. 

These 2 drives size is around 2TB.

 I have selected file read timeout to 3600, still no use.

Kindly advise if  i need to disable "windows open file backup"

Hello all,

Because of an internal project to develop backup solutions for AWS I am very interested in upgrading from NBU 7.6.0.1 to 7.7. The project has become a priority to my company, so I'm motivated to upgrade ASAP, but I'm hesitant be one of the first to upgrade. I'm interested in feedback anyone has regarding their upgrade experience, not just about the new AWS integration, but about 7.7 in general.

Hi,

Customer is running NBU 7.6.0.1 on Windows Server.

They recently added a stand-alone tape drive and have it configured. Configuration was successful, including storage unit configuration.

But upon testing backup, they experienced an error. Pleas esee error below.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

7/14/2015 5:05:05 PM - Info nbjm(pid=6132) starting backup job (jobid=293501) for client bdowins01, policy test, schedule test  
7/14/2015 5:05:05 PM - Info nbjm(pid=6132) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=293501, request id:{E9187F42-2E30-4F98-975F-3440D8B8763C})  
7/14/2015 5:05:05 PM - requesting resource bdowins01-hcart2
7/14/2015 5:05:05 PM - requesting resource bdowcbs07.NBU_CLIENT.MAXJOBS.bdowins01
7/14/2015 5:05:05 PM - requesting resource bdowcbs07.NBU_POLICY.MAXJOBS.test
7/14/2015 5:05:05 PM - granted resource bdowcbs07.NBU_CLIENT.MAXJOBS.bdowins01
7/14/2015 5:05:05 PM - granted resource bdowcbs07.NBU_POLICY.MAXJOBS.test
7/14/2015 5:05:05 PM - granted resource A00008
7/14/2015 5:05:05 PM - granted resource HP.ULTRIUM4-SCSI.000
7/14/2015 5:05:05 PM - granted resource bdowins01-hcart2
7/14/2015 5:05:05 PM - estimated 0 Kbytes needed
7/14/2015 5:05:05 PM - Info nbjm(pid=6132) started backup (backupid=bdowins01_1436864705) job for client bdowins01, policy test, schedule test on storage unit bdowins01-hcart2
7/14/2015 5:05:27 PM - started process bpbrm (4316)
7/14/2015 5:05:28 PM - Info bpbrm(pid=4316) bdowins01 is the host to backup data from    
7/14/2015 5:05:28 PM - Info bpbrm(pid=4316) reading file list for client        
7/14/2015 5:05:28 PM - Info bpbrm(pid=4316) starting bpbkar32 on client        
7/14/2015 5:05:28 PM - connecting
7/14/2015 5:05:28 PM - connected; connect time: 0:00:00
7/14/2015 5:05:29 PM - Info bpbkar32(pid=4188) Backup started          
7/14/2015 5:05:29 PM - Info bpbkar32(pid=4188) change time comparison:<disabled>          
7/14/2015 5:05:29 PM - Info bpbkar32(pid=4188) archive bit processing:<enabled>          
7/14/2015 5:05:29 PM - Info bpbkar32(pid=4188) not using change journal data for <E:\test>: not enabled    
7/14/2015 5:05:29 PM - Info bptm(pid=1664) start            
7/14/2015 5:10:43 PM - Error bpbrm(pid=4316) could not send server status message      
7/14/2015 5:10:43 PM - Info bpbkar32(pid=4188) done. status: 10: allocation failed        
7/14/2015 5:10:43 PM - end writing
allocation failed(10)

Thank you!

Hello,

I'm looking for feedback about replicating data from MSDP master server on remote sites back to data center site.

They are not in the same domain. I referred some symantec documents (such as "https://support.symantec.com/en_US/article.TECH163110.html") that pre-seeding could be used for deduplication but I don't know if I could use seeding to speed up the initial full backup replication. If it could be used, what's the configuration step ? 

We have SVN configured on windows server 2k8 R2.The backup directory is D:\csvn.

We have configured one windows server 2k8 R2 running netbackup server 6.5.6 as a backup server.

All policies are running fine except the policy which is taking backup of the SVN server above.

The backup keeps on running without any increase in "Percentage Compleate".

Activity logs.

7/14/2015 6:42:29 PM - mounted
7/14/2015 6:42:29 PM - connecting
7/14/2015 6:42:29 PM - positioning 0023L6 to file 281
7/14/2015 6:42:29 PM - positioned 0023L6; position time: 00:00:00
7/14/2015 6:42:30 PM - connected; connect time: 00:00:01
7/14/2015 6:42:30 PM - begin writing

Current time is 10:47 AM 15/7/2015 and it is still running.It is always struck in /D/csvn/data/repositories/carnival/db/revs/0/117 or some other files.

We are facing this issue as this backup server was recently configured.In previous backup server this policy was running fine.

Also please note we have created a new backup server and created new policies.We havent importany any catalog from previous server.

Also we have 2-3 other SVN servers configured for backup with same SVN repo and they are working fine.

We have tried bpcd logs,tried connecting from backup server,all this is working fine.Also we have created a new policy of the problematic SVN server with different backup folder and it is working fine.

Kindly suggest what can be done to resolve the issue.

Hi Experts,

The Netbackup master server ( version 7.6.1.2 ) is installed on redhatlinux 6.X.

I installed remote console 7.6.1.2 on my laptop which is windows 7.

I added the hostname and IP address to each other's hosts file.

Added my laptop's hostname as additional server to the master server.

There is one problem that our IT opened the telnet ports 1556, 13782 and 13724, but I couldn't telnet my laptop on 1556 from master server.

Is this the key point that I couldn't login to Netbackup Administration Console??

Could any one help me on this problem? Great thanks to you!

Regards,

Lacey

Looks like I had two bpfis processes eat up all my memory and then proceed to crash my VMware backup host. The server is Windows 2012 and has 32GB of RAM.

Custom size on the pagefile is 28415 for both initial and max.

Any help with this one would be greatly appreciated.

10:20PM 7-14

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: nbostpxy.exe (15304) consumed 1333911552 bytes, bpbkar32.exe (20748) consumed 1317830656 bytes, and bpfis.exe (20260) consumed 791089152 bytes.

- System

  - Provider

   [ Name]  Microsoft-Windows-Resource-Exhaustion-Detector
   [ Guid]  {9988748E-C2E8-4054-85F6-0C3E1CAD2470}
 
   EventID 2004
 
   Version 0
 
   Level 3
 
   Task 3
 
   Opcode 33
 
   Keywords 0x8000000020000000
 
  - TimeCreated

   [ SystemTime]  2015-07-15T03:20:11.792020500Z
 
   EventRecordID 573615
 
  - Correlation

   [ ActivityID]  {E534EEEA-AF8A-4B43-9777-90FA662A7A46}
 
  - Execution

   [ ProcessID]  2488
   [ ThreadID]  31484
 
   Channel System
 
   Computer 53tape001.botw.ad.bankofthewest.com
 
  - Security

   [ UserID]  S-1-5-18
 

- UserData

  - MemoryExhaustionInfo

  - SystemInfo

   SystemCommitLimit 64118718464
 
   SystemCommitCharge 64119025664
 
   ProcessCommitCharge 62406537216
 
   PagedPoolUsage 275853312
 
   PhysicalMemorySize 34323431424
 
   PhysicalMemoryUsage 34322612224
 
   NonPagedPoolUsage 343117824
 
   Processes 510
 
 
  - ProcessInfo

  - Process_1

   Name nbostpxy.exe
 
   ID 15304
 
   CreationTime 2015-07-15T00:02:05.322876800Z
 
   CommitCharge 1333911552
 
   HandleCount 426
 
   Version 7.600.214.424
 
   TypeInfo 65
 
 
  - Process_2

   Name bpbkar32.exe
 
   ID 20748
 
   CreationTime 2015-07-15T00:02:15.791556500Z
 
   CommitCharge 1317830656
 
   HandleCount 667
 
   Version 7.600.214.424
 
   TypeInfo 66
 
 
  - Process_3

   Name bpfis.exe
 
   ID 20260
 
   CreationTime 2015-07-14T23:45:55.291613200Z
 
   CommitCharge 791089152
 
   HandleCount 253
 
   Version 7.600.214.424
 
   TypeInfo 67
 
 
  - Process_4

   Name
 
   ID 0
 
   CreationTime 1601-01-01T00:00:00.000000000Z
 
   CommitCharge 0
 
   HandleCount 0
 
   Version 0.0.0.0
 
   TypeInfo 0
 
 
  - Process_5

   Name
 
   ID 0
 
   CreationTime 1601-01-01T00:00:00.000000000Z
 
   CommitCharge 0
 
   HandleCount 0
 
   Version 0.0.0.0
 
   TypeInfo 0
 
 
  - Process_6

   Name
 
   ID 0
 
   CreationTime 1601-01-01T00:00:00.000000000Z
 
   CommitCharge 0
 
   HandleCount 0
 
   Version 0.0.0.0
 
   TypeInfo 0
 
 
 
  - PagedPoolInfo

  - Tag_1

   Name CM31
 
   PoolUsed 65265664
 
 
  - Tag_2

   Name CM16
 
   PoolUsed 49459200
 
 
  - Tag_3

   Name DMTX
 
   PoolUsed 21037680
 
 
 
  - NonPagedPoolInfo

  - Tag_1

   Name Cont
 
   PoolUsed 26666688
 
 
  - Tag_2

   Name Thre
 
   PoolUsed 12405056
 
 
  - Tag_3

   Name IXGB
 
   PoolUsed 11065760
 
 
 
  - ExhaustionEventInfo

   Time 2015-07-15T03:19:30.532670800Z

---------------------------------------------
Faulting application name: bpcd.exe, version: 7.600.214.424, time stamp: 0x53597c4d
Faulting module name: ntdll.dll, version: 6.2.9200.17313, time stamp: 0x5507a832
Exception code: 0xc000012d
Fault offset: 0x00000000000e2100
Faulting process id: 0x7c54
Faulting application start time: 0x01d0bead442a4825
Faulting application path: E:\Program Files\Veritas\NetBackup\bin\bpcd.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9351ba16-2aa0-11e5-9408-a0369f1a3542
Faulting package full name:
Faulting package-relative application ID:
---------------------------------------------
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: bpfis.exe
P2: 7.600.214.424
P3: 53597c74
P4: MSVCR100.dll
P5: 10.0.40219.455
P6: 5253cced
P7: 40000015
P8: 0000000000076269
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_bpfis.exe_74bc75e04aedd284d645efbfab8da538f33325f1_d8f0e0a1

Analysis symbol:
Rechecking for solution: 0
Report Id: 74897e0a-2aa0-11e5-9408-a0369f1a3542
Report Status: 0
Hashed bucket:
-----------------------------------------------
Faulting application name: bpfis.exe, version: 7.600.214.424, time stamp: 0x53597c74
Faulting module name: nbuVmwareTools.dll, version: 5.5001.13.1210, time stamp: 0x52a7f7c5
Exception code: 0xc0000005
Fault offset: 0x00000000004c8fdc
Faulting process id: 0x75fc
Faulting application start time: 0x01d0be91a13ef373
Faulting application path: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe
Faulting module path: E:\Program Files\Veritas\NetBackup\bin\nbuVmwareTools.dll
Report Id: 987015d9-2aa0-11e5-9408-a0369f1a3542
Faulting package full name:
Faulting package-relative application ID:

Log Name:      Application
Source:        Application Error
Date:          7/14/2015 10:21:35 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      53tape001.botw.ad.bankofthewest.com
Description:
Faulting application name: bpfis.exe, version: 7.600.214.424, time stamp: 0x53597c74
Faulting module name: nbuVmwareTools.dll, version: 5.5001.13.1210, time stamp: 0x52a7f7c5
Exception code: 0xc0000005
Fault offset: 0x00000000004c8fdc
Faulting process id: 0x75fc
Faulting application start time: 0x01d0be91a13ef373
Faulting application path: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe
Faulting module path: E:\Program Files\Veritas\NetBackup\bin\nbuVmwareTools.dll
Report Id: 987015d9-2aa0-11e5-9408-a0369f1a3542
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-15T03:21:35.000000000Z" />
    <EventRecordID>35024</EventRecordID>
    <Channel>Application</Channel>
    <Computer>53tape001.botw.ad.bankofthewest.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>bpfis.exe</Data>
    <Data>7.600.214.424</Data>
    <Data>53597c74</Data>
    <Data>nbuVmwareTools.dll</Data>
    <Data>5.5001.13.1210</Data>
    <Data>52a7f7c5</Data>
    <Data>c0000005</Data>
    <Data>00000000004c8fdc</Data>
    <Data>75fc</Data>
    <Data>01d0be91a13ef373</Data>
    <Data>E:\Program Files\Veritas\NetBackup\bin\bpfis.exe</Data>
    <Data>E:\Program Files\Veritas\NetBackup\bin\nbuVmwareTools.dll</Data>
    <Data>987015d9-2aa0-11e5-9408-a0369f1a3542</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Hello ,

currently i am working with customer having 2 backup solution . one is taking backup on tapes and other one on disk . they are looking for a way to have at certain point all backup taken on the 1st solution on tape being moved to the disk on the 2nd solution . is staging is supporting tape to disk ?

thanks

Mina

The backup intermittently hangs causing the Lotus notes domino to hang. The issue resolves when the NBU client services have been restarted. When restarted Domino will crash and come back within 10-15 mins. Sometimes domino services will start automatically or it needs a manual restart.

Notes has recorded error indicating NetBackup/bin/nblnagent64.exe has terminated abnormally.

This is not new install. The backup did not have this problem and issue appeared suddenly without any changes reported.

Issue noticed only during full backup. All are VM's.

NBU version- 7.6.0.3

Notes- 9.0.1

I have three Netbackup masters connected to 4 silos (one has two silos).  Each silo has tapes with a unique prefix.  They are all LTO4 tapes (we use HCART3 for these [out of necessity]).

Occasionally someone will insert the wrong tape into the wrong silo. If I dont quickly take some action Netbackup sees this as a new scratch tape and might write onto it (even though the tape is not really expired yet).

So I tried writing some Barcode rules to assign 'unexpected tapes' - those with prefixes that should not be inserted into this silo - to a media type we dont use (I chose WORM_OPT). I also specified Volume Pool NONE.

My plan is that the tapes would just sit in the silo and never be used until I had a chance to relocate them to the correct silo.

But whenever I insert a tape it still gets added to the media database as HCART3 and SCRATCH_POOL.

I have attached a screenshot. "AU" and "R" tapes are expected in this silo; "C", "W", and "T" should not be inserted (but occasionally are).

Any help would be appreciated.