Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NBU7.5.0.3 backups with a NetBackup Status Code 0 (successful), but the data is not backed up

Created: 10 Oct 2013 • Updated: 16 Oct 2013 | 16 comments
This issue has been solved. See solution.

hi,

i have an odd issue.

1) NBU master info as below, and there is no media server
NBU master: CentOS release 5.5 (Final), NetBackup 7.5.0.3

2) Windows client info as blow, NBU7.5.0.3
 Windows Server 2008 R2 Standard

3)issue:
i create a backup policy for this new client today to backup "E:\Call_Center Shares". and I start the first full backup manually and the Java Admin GUIconsole shows that the backup completed successfully with status code 0.
the full backup finishes within 5 seconds, it is too quick since we have around 47G data!
so I check the backup image only to find the the 3 subfolders are empty!!! 

the following are the 3 subfolders......there are only 3 empty folders but no data.

E:\Call_Center Shares
                  Customer_Service
                  Documentation
                   Profiles

4) all the NBU client services are running with "local system" and I check the permission of "SYSTEM" , it is good.

the following steps are what I did in order to troubleshoot:

1) I backup a new directory C:\NRPE_NT on the client, which ends successfully with all the data.

2) I copied “E:\Call_Center Shares\Customer_Service” to “E:\Call_Center Shares\Customer_Service – Copy”, and then backup “E:\Call_Center Shares\Customer_Service – Copy” which ends up successfully with all the data. 

So I think the issue should be related to the directory itself ( E:\Call_Center Shares).  but don;t know the root cause and how to fix it.

so  please help!!!

thanks!

Operating Systems:
Discussion Filed Under:

Comments 16 CommentsJump to latest comment

CraigV's picture

...this poppoed up in the BE forums...moved to the correct location!

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

RamNagalla's picture

1) does this the local disk or the CIFS share?

2) by any chance does this folder in exclude list E:\Call_Center Shares  ?

Ivy_Yang's picture

1) it is local drive, not CIFS share;

2) I don't think "E:\Call_Center Shares " is in the exclude list, since I can backup one of the copied subfolders: "E:\Call_Center Shares\Customer_Service – Copy”

and i don't set any exclude list on the NBU master.....

thank you Nagalla!!!!

RamNagalla's picture

so lets do this..

enable the Verbose is set to 5 in client 

make sure bpbkar folder is created in Installpath:/veritas/netbackup/logs/bpbkar. in client

then take the backup of the folder E:\Call_Center Shares.

once backup is compleated. attach the bpbkar log to this post.

Ivy_Yang's picture

okay

1) I set the client attribute "global logging level"  as well as the "database logging level" to "5(maximum)

NBU java admin console---->host properties----->client----->properties---->Logging

2) directoy C:\Program Files\Veritas\NetBackup\logs\bpbkar is already there

now I am restarting both the services on client and master....

and then I will try the backup and post the bpbkar log to the post

Marianne's picture

Are these perhaps separate mount points?

If so, select 'cross mount points' in policy attributes.

Another possibility is DFS Replication. 

Drive letters/folders under DFS-R control will be backed up as part of Shadow Copy Components.

bpbkar log should help....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Ivy_Yang's picture

this is the log:

6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: INF - Starting log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\101013.LOG

6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: GENERAL Log Level: 0
6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: TCP Log Level: 0
6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: INF - the log mutex: 352
BPBKAR  NetBackup Backup/Archive  7.5GA  [Jun  5 2012]
Copyright © 1993 - 2012 Symantec Corporation, All Rights Reserved.
All Rights Reserved.

6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - _pgmptr = 'C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe'
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - lpCmdLine = '-r 8035200 -ru root -dt 0 -to 0 -bpstart_time 1381398917 -clnt wsashdfs01.active.local -class wsashdfs01 -sched Bi_weekly_full -st FULL -bpstart_to 300 -bpend_to 300 -read_to 300 -ckpt_time 900 -blks_per_buffer 512 -use_otm -nfsok -b wsashdfs01.active.local_1381398617 -kl 28 -WOFB_enabled -WOFB_fim 1 -WOFB_usage 0 -WOFB_error 0 -ct 13 -use_ofb '
6:51:59.898 AM: [2120.5732] <2> date_debug: DAT - timezone: Eastern Standard Time, offset=18000, dst: Eastern Daylight Time
6:51:59.898 AM: [2120.5732] <2> date_debug: DAT - current time: 1381402319, 10/10/2013 6:51:59 AM
6:51:59.898 AM: [2120.5732] <2> date_debug: DAT - 01/01/94 UCT:  757382400, 12/31/1993 8:00:00 PM
6:51:59.898 AM: [2120.5732] <2> date_debug: DAT - 07/01/94 UCT:  773020800, 6/30/1994 8:00:00 PM
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard input handle = 368
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard input handle is NOT resilient socket.
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard output handle = 220
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard output handle is NOT resilient socket.
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard error handle = 364
6:51:59.898 AM: [2120.5732] <2> WinMain: DAT - standard error handle is NOT resilient socket.
6:52:01.054 AM: [2120.5732] <4> tar_backup_tfi::create: INF - change time comparison:<disabled>
6:52:01.054 AM: [2120.5732] <4> tar_backup::V_SetupJobData: INF - dwJobData: ffffffff
6:52:01.054 AM: [2120.5732] <4> tar_backup::V_SetupJobData: INF -     dwJob: ffffffff
6:52:01.069 AM: [2120.5732] <4> ncfLogConfiguration: INF - Module: libncf, Release: 7.5.0.3 , Build: 06/05/2012 20:00:00 CDT (20120605)
6:52:01.069 AM: [2120.5732] <4> ncfLogConfiguration: INF - Windows version: 6.1.7601, Platform: 2 (Service Pack 1), Service pack: 1.0, Suite: 272, Product type: 3
6:52:01.085 AM: [2120.5732] <4> ncfLogConfiguration: INF - Process architecture: 9, Page size: 4096, Process type: 1, Process level: 8664, Processor revision: 6
6:52:01.085 AM: [2120.5732] <4> NcfString::logLocale: INF - Current code page: WINDOWS: 1252  (ANSI - Latin I), Max. character width: 1, Substitution character: 0x3F [?], Unicode substitution character: 0x003f [?.]
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - user name: root
6:52:01.085 AM: [2120.5732] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup
6:52:01.085 AM: [2120.5732] <2> ov_log::V_GlobalLog: WRN - ubsDetermineExchangeVersion(): RegOpenKeyEx() failed for HKLM\SOFTWARE\MICROSOFT\ExchangeServer\v14\Setup - 0x2.
6:52:01.085 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: E:
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Symantec SNAC Network Provider
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: VMware Shared Folders
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
6:52:01.366 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
6:52:01.398 AM: [2120.5732] <2> tar_base::V_vTarMsgW: INF - BACKUP START 2120
6:52:01.398 AM: [2120.5732] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
6:52:01.398 AM: [2120.5732] <2> tar_base::V_vTarMsgW: INF - CONTINUE BACKUP message received
6:52:01.398 AM: [2120.5732] <4> tar_backup_cpr::start: INF - checkpoint thread started
6:52:01.398 AM: [2120.5732] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = E:\Call_Center Shares
6:52:01.398 AM: [2120.1592] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - volume guid:<\\?\Volume{18adef46-4c12-11e1-a086-806e6f6e6963}\>
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - mounted at:<C:\>:<\\?\Volume{18adef46-4c12-11e1-a086-806e6f6e6963}\>
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - not adding to collection, volume:<\\?\Volume{18adef46-4c12-11e1-a086-806e6f6e6963}\>:<C:\> is configured to not use the change journal
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - volume guid:<\\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\>
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - mounted at:<E:\>:<\\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\>
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - not adding to collection, volume:<\\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\>:<E:\> is configured to not use the change journal
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - volume guid:<\\?\Volume{18adef45-4c12-11e1-a086-806e6f6e6963}\>
6:52:01.554 AM: [2120.5732] <2> NBJournalDataCollection::NBJournalDataCollection: INF - not adding to collection, volume:<\\?\Volume{18adef45-4c12-11e1-a086-806e6f6e6963}\> is not mounted anywhere
6:52:01.554 AM: [2120.5732] <4> dos_backup::V_Initialize: INF - created change journal collection
6:52:01.554 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_Query: INF - Attempting to query volume snapshots: bpfis query -id wsashdfs01.active.local_1381398617  -copy 1
6:52:02.554 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: wsashdfs01.active.local_1381398617
6:52:02.554 AM: [2120.5732] <2> tar_backup_vxbsa::add: INF - called with 'E:\Call_Center Shares'
6:52:02.554 AM: [2120.5732] <2> _expand_root: INF - checking for root expansion:<E:\Call_Center Shares>
6:52:02.554 AM: [2120.5732] <2> _fix_registry: INF - checking for registry expansion:<E:\Call_Center Shares>
6:52:02.554 AM: [2120.5732] <4> dos_backup::V_VerifyFileSystem: INF - corrected name:<E:\Call_Center Shares>
6:52:02.554 AM: [2120.5732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'E:\Call_Center Shares' --> 10020002
6:52:03.663 AM: [2120.5732] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
6:52:03.663 AM: [2120.5732] <4> tar_backup_tfi::UpdateExcludeListWithVHD: INF - UpdateExludeListWithVHD begin
6:52:03.710 AM: [2120.5732] <4> tar_backup_tfi::backup_arg_state: INF - remember start error count: 0
6:52:03.710 AM: [2120.5732] <4> tar_backup_tfi::backup_arg_state: INF - remember start fatal count: 0
6:52:03.710 AM: [2120.5732] <4> dos_backup::tfs_scanstart: INF - starting scan for file directive:<E:\Call_Center Shares>
6:52:03.710 AM: [2120.5732] <4> dos_backup::tfs_scanstart: INF - starting scan using name:<E:\Call_Center Shares>
6:52:03.710 AM: [2120.5732] <4> dos_backup::tfs_scanstart: INF - in 'backup' mode
6:52:03.710 AM: [2120.5732] <2> tar_base::V_vTarMsgW: INF - Enabling volume snapshots for (E:\Call_Center Shares), please wait...
6:52:03.710 AM: [2120.5732] <4> V_DetermineMountInfo: INF - Checking Volume \\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\ for '\Call_Center Shares'
6:52:03.710 AM: [2120.5732] <4> V_DetermineMountInfo: INF -   Adding NTFS Volume E:\ ==> \\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\
6:52:03.710 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
6:52:03.710 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to create snapshots for 'E:\Call_Center Shares'
6:52:03.710 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request: C:\Program Files\Veritas\NetBackup\bin\bpfis create -owner NBU -WOFB -fim VSS -id wsashdfs01.active.local_1381398617 "E:\Call_Center Shares"
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_AddMappings: INF - input parameters:
 source path:<E:\Call_Center Shares>
   snap path:<\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Call_Center Shares>
  mount path:<(null)>
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_GetSourceVolume: INF - input parameters:
   source:<E:\Call_Center Shares>
 snapshot:<\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Call_Center Shares>
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{7e415054-4d2a-11e1-b2c7-0050569c1b78}\ --> GLOBALROOT\Device\HarddiskVolumeShadowCopy28
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: wsashdfs01.active.local_1381398617
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation was successful
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot provider: VSS
6:52:11.742 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
6:52:11.742 AM: [2120.5732] <2> tar_base::V_vTarMsgW: INF - Volume snapshots enabled
6:52:11.742 AM: [2120.5732] <2> tar_base::V_vTarMsgW: JBD - change journal NOT enabled for <E:\Call_Center Shares>
6:52:13.429 AM: [2120.5732] <4> dos_backup::tfs_scannext: INF - no more path list entries
6:52:13.429 AM: [2120.5732] <4> tar_backup::backup_endarg_state: INF - finish error count: 0
6:52:13.429 AM: [2120.5732] <4> tar_backup::backup_endarg_state: INF - finish fatal count: 0
6:52:13.429 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_Destroy: INF - Attempting to destroy volume snapshots: bpfis delete -id wsashdfs01.active.local_1381398617 -copy 1
6:52:17.461 AM: [2120.5732] <4> V_Snapshot::V_Snapshot_Destroy: INF - Snapshot Destroy EXIT STATUS 0: the requested operation was successfully completed
6:52:17.461 AM: [2120.5732] <2> tar_base::backup_finish: TAR - backup:                     4 files
6:52:17.461 AM: [2120.5732] <2> tar_base::backup_finish: TAR - backup:          file data:          0 bytes
6:52:17.461 AM: [2120.5732] <2> tar_base::backup_finish: TAR - backup:         image data:      16384 bytes
6:52:17.461 AM: [2120.5732] <2> tar_base::backup_finish: TAR - backup:       elapsed time:         14 secs         1170 bps
6:52:17.461 AM: [2120.5732] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
6:52:17.461 AM: [2120.5732] <4> tar_backup::backup_done_state: INF -     number of file directives found: 1
6:52:17.461 AM: [2120.1592] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
6:52:17.461 AM: [2120.5732] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
6:52:17.461 AM: [2120.5732] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 0: the requested operation was successfully completed
6:52:18.461 AM: [2120.5732] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
6:52:18.461 AM: [2120.5732] <4> OVStopCmd: INF - EXIT - status = 0
6:52:18.461 AM: [2120.5732] <2> tar_base::V_Close: closing...
6:52:18.461 AM: [2120.5732] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
6:52:18.461 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000101
6:52:18.461 AM: [2120.5732] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): ubs specifics: 0x001d0000
6:52:18.492 AM: [2120.5732] <4> OVShutdown: INF - Finished process
6:52:18.492 AM: [2120.5732] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
6:52:20.492 AM: [2120.5732] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\101013.LOG

Marianne's picture

bpbkar log does not give enough info.

Please speak to server owner to find out:

1) If the sub-directories are separate volumes

2) If folders are under DFS-R control.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Ivy_Yang's picture

thank you both Marianne ...

I talked with box owner and at least one the the subfolder "E:\Call_Center Shares\Customer_Service" is indeed relate  to DFSR content....

so we can't backup DSFR content? would you please provide me a doc link for reference? 111.jpg

RamNagalla's picture

bpbkar log level is not set to 5, did you set the log level for client?

6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: GENERAL Log Level: 0
6:51:59.882 AM: [2120.5732] <4> ov_log::OVInit: TCP Log Level: 0

yes, i do agree with Marianne,

please speak with server admin

Marianne's picture

Folders under DFS-R control are backed up as part of Shadow Copy Components.

Excellent HOWTO DFS-R TechNote: http://www.symantec.com/docs/HOWTO65638

Please bookmark this link to access all NBU 7.5 manuals: http://www.symantec.com/docs/DOC5138 
(or 'Handy NBU Links' in my signature)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION