This issue needs a solution.

Failed with snapshot

Created: 19 Jun 2012 • Updated: 28 Aug 2012
Login to vote
0 0 Votes

Master server: NetBackup-Solaris10 7.1.0.2

Client :

Filed Under

Comments

19
Jun
2012

BPBKAR LOGS for the same issue

10:04:22.062 PM: [7800.8732] <4> ov_log::OVInit: INF - Starting log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\061912.LOG

10:04:22.062 PM: [7800.8732] <4> ov_log::OVInit: GENERAL Log Level: 0
10:04:22.062 PM: [7800.8732] <4> ov_log::OVInit: TCP Log Level: 0
10:04:22.062 PM: [7800.8732] <4> ov_log::OVInit: INF - the log mutex: 592
BPBKAR  NetBackup Backup/Archive  7.1GA  [Aug 25 2011]
Copyright © 1993 - 2011 Symantec Corporation, All Rights Reserved.
All Rights Reserved.

10:04:22.062 PM: [7800.8732] <2> WinMain: DAT - _pgmptr = 'C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe'
10:04:22.062 PM: [7800.8732] <2> WinMain: DAT - lpCmdLine = '-r 3024000 -ru root -dt 0 -to 0 -clnt tus3monclupib02 -class win_prod_monclu -sched Full -st FULL -bpstart_to 300 -bpend_to 300 -read_to 3600 -ckpt_time 900 -blks_per_buffer 511 -use_otm -use_ofb -b tus3monclupib02_1340168659 -kl 28 -fso -WOFB_enabled -WOFB_fim 0 -WOFB_usage 0 -WOFB_error 1 -ct 13 '
10:04:22.062 PM: [7800.8732] <2> date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time
10:04:22.062 PM: [7800.8732] <2> date_debug: DAT - current time: 1340168662, 6/19/2012 10:04:22 PM
10:04:22.062 PM: [7800.8732] <2> date_debug: DAT - 01/01/94 UCT:  757382400, 12/31/1993 5:00:00 PM
10:04:22.062 PM: [7800.8732] <2> date_debug: DAT - 07/01/94 UCT:  773020800, 6/30/1994 5:00:00 PM
10:04:22.062 PM: [7800.8732] <2> WinMain: DAT - standard input handle = 676
10:04:22.062 PM: [7800.8732] <2> WinMain: DAT - standard output handle = 616
10:04:22.062 PM: [7800.8732] <2> WinMain: DAT - standard error handle = 612
10:04:22.124 PM: [7800.8732] <4> tar_backup::V_SetupJobData: INF - dwJobData: ffffffff
10:04:22.124 PM: [7800.8732] <4> tar_backup::V_SetupJobData: INF -     dwJob: ffffffff
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - user name: root
10:04:22.140 PM: [7800.8732] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup
10:04:22.140 PM: [7800.8732] <2> ov_log::V_GlobalLog: WRN - ubsDetermineExchangeVersion(): RegOpenKeyEx() failed for HKLM\SOFTWARE\MICROSOFT\ExchangeServer\v14\Setup - 0x2.
10:04:22.140 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D:
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: G:
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Symantec SNAC Network Provider
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
10:04:22.296 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
10:04:22.390 PM: [7800.8732] <2> tar_base::V_vTarMsgW: INF - BACKUP START 7800
10:04:22.452 PM: [7800.8732] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
10:04:22.452 PM: [7800.8732] <2> tar_base::V_vTarMsgW: INF - CONTINUE BACKUP message received
10:04:22.452 PM: [7800.8732] <4> tar_backup_cpr::start: INF - checkpoint thread started
10:04:22.452 PM: [7800.8732] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = ALL_LOCAL_DRIVES
10:04:22.452 PM: [7800.8296] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
10:04:22.530 PM: [7800.8732] <4> V_Snapshot::V_Snapshot_Query: INF - Attempting to query volume snapshots: bpfis query -id tus3monclupib02_1340168659
10:04:23.545 PM: [7800.8732] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: tus3monclupib02_1340168659
10:04:23.545 PM: [7800.8732] <2> tar_backup_vxbsa::add: INF - called with '/'
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileSystem: INF - Added: C:\
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileSystem: INF - Added: D:\
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileSystem: INF - Added: Shadow Copy Components:\
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileSystem: INF - Added: System State:\
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'C:\' --> 10020002
10:04:23.545 PM: [7800.8732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'D:\' --> 10020002
10:04:24.982 PM: [7800.8732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'Shadow Copy Components:\' --> 10020027
10:04:26.449 PM: [7800.8732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for 'System State:\' --> 1002002d
10:04:26.449 PM: [7800.8732] <4> dos_backup::V_VerifyFileList: INF - UBS Local Type for '_BACKUP_SPECIAL_OBJECTS AFTER System State:' --> 1002002d
10:04:27.839 PM: [7800.8732] <4> VssSnapshot::V_VssSetMetadata(): INF - Unable to locate DFSR metadata
10:04:28.182 PM: [7800.8732] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
10:04:28.182 PM: [7800.8732] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: Begin
10:04:31.290 PM: [7800.8732] <4> dos_backup::tfs_findfirst: INF - unable to find first file: 'Shadow Copy Components:\System Service\Background Intelligent Transfer Service\'
10:04:31.305 PM: [7800.8732] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - Drive 'C:' added to VSS Volume Set
10:04:34.600 PM: [7800.8732] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - VSS Volume Set snapped
10:04:34.600 PM: [7800.8732] <4> VssSnapshot::V_VssVolumeSnapshot(): INF - About to commence post-snap unbounded association checks
10:04:34.600 PM: [7800.8732] <4> dos_backup::V_InitializeShadowCopy: INF - ShadowCopy PrePost: End
10:04:34.600 PM: [7800.8732] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
10:04:34.615 PM: [7800.8732] <4> VssSnapshot::V_VssSetMetadata(): INF - Unable to locate DFSR metadata
10:04:38.987 PM: [7800.8732] <16> dos_backup::V_InitializeSystemState: ERR - FS_AddToSnapshotSet() Failed! (System State:\System Files\System Files) 0xE0000352:The specified volume does not exist. Recreate the volume, and then try the job again.

10:04:38.987 PM: [7800.8732] <2> tar_base::V_vTarMsgW: ERR - Volume resolution error for (System State:\System Files\System Files)
10:04:38.987 PM: [7800.8732] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encountered
10:04:38.987 PM: [7800.8732] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
10:04:38.987 PM: [7800.8732] <16> tar_backup::SetExcludeFileList: **** DBG **** - alternate client fileter file is null
10:04:38.987 PM: [7800.8732] <4> tar_backup_tfi::UpdateExcludeListWithVHD: INF - UpdateExludeListWithVHD begin
10:04:42.469 PM: [7800.8732] <4> OVStopCmd: INF - EXIT - status = 0
10:04:42.469 PM: [7800.8732] <2> tar_base::V_Close: closing...
10:04:43.531 PM: [7800.8732] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000001
10:04:43.531 PM: [7800.8732] <16> dtcp_read: TCP - failure: recv socket (676) (TCP 10053: Software caused connection abort)
10:04:43.531 PM: [7800.8732] <4> OVShutdown: INF - Finished process
10:04:43.531 PM: [7800.8732] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
10:04:45.561 PM: [7800.8732] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\061912.LOG

Yogesh9881
Partner
Accredited
19
Jun
2012

wannawin

Can you plz post complete error message from activity monitor details status tab ?

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

28
Aug
2012

..

..

28
Aug
2012

snapshot error encountered 

snapshot error encountered  (156)
 

mph999
Symantec Employee
Accredited
20
Jun
2012

Need bpfis log please when a

Need bpfis log please when a job fails with status 156.

Create <install path>\veritas\netbackup\logs\bpfis  and rerun job.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne
Trusted Advisor
Accredited
Certified
20
Jun
2012

Please post policy config? On

Please post policy config? On master:

bppllist <policy-name> -U

Please also let us know XP SP version. If I am not mistaken, only SP3 is supported. (Will verify).

Where is this reference to W2008 coming from?

Client OS/Release = Windows2008 6

 

PS: Martin (wave) the bpfis log is part of opening post.

 

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

mph999
Symantec Employee
Accredited
20
Jun
2012

Hi Marianne .... Opps, sorry

Hi Marianne ....

Opps, sorry guys, bit blind today ...

OK, from another post where the poster had this issue :

19:22:53.559 [6052.5744] <32> fis_rebuild_from_db: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.Client.com_1311903706.0

... which compared to yours ...

18:06:42.368 [6632.8844] <32> fis_rebuild_from_db: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.tus3monclupib02_1340154395.0

... is very similar.

Here was the solution :

"I raised a case with Symantec, took the Vxms logs and found that, they receiving a null on some data index, it could be caused by corruption.

So, adviced to run chkdsk/defrag command in volume D drive.

After doing a chkdsk/defrag on the drive, the backups are happening and no failures till date."

 

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
28
Aug
2012

  ITS SP3  

 

ITS SP3

 

20
Jun
2012

update..........

is there any switch to run this because when i am trying then it will not work.

version 6.1 (Build 7601 p1 ) Windows 2008 r2
 
 
Yogesh9881
Partner
Accredited
20
Jun
2012

Hi,

pls confirm what is OS on client ??

Win XP or Win2k8 ??

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

Marianne
Trusted Advisor
Accredited
Certified
20
Jun
2012

XP or 2008???

I agree with Yogesh - please confirm client OS? According to your opening post it is Windows XP, later on you say XP3, but policy says Windows 2008?

Any kind of advice will be based on correct client OS.
There are lots of TN's and forum posts for W2008.

To isolate problematic backup stream and have successful backups for the rest, enable Multiple Data Streams in policy attributes.

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

Yogesh9881
Partner
Accredited
20
Jun
2012

Hi

As per your server Hostnames i can GUESS these 2 server are in cluster ... AM I CORRECT ??

if YES then you need to put cluster name (Virtual Name) in NetBackup policy & NOT 2 actual host names.

 

IF my guessing correct then your issue will fix soon smiley

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

20
Jun
2012

Window 2008

Version is window 2008 and it is not in cluster.

 

 

20
Jun
2012

SOLVED

Thanks everyone for timely help.

Actually this server is in cluster and one is active and one is passive. Backup of active one completed successfully but shadow copy componenet backup pof passive one is failed with 156 and backup of c and d drive completed successfully

 

Thanks sooo much

Yogesh9881
Partner
Accredited
20
Jun
2012

Hi,

I was correct cool

Thanks for updating us....

Our only motivation is to help you 

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

21
Jun
2012

how?

how do you know that it is in cluster??

Yogesh9881
Partner
Accredited
21
Jun
2012

Wannawin

My 6th sense wink   

Actually your hostname is tus3monclupib01 & tus3monclupib02 ......So your hostname containts "clu" 

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

Andy Welburn
Trusted Advisor
21
Jun
2012

So

the clu(e) was in the name laughcrying

Marianne
Trusted Advisor
Accredited
Certified
21
Jun
2012

If I understand you correctly

If I understand you correctly SCC for passive node is still failing with 156?

.... but shadow copy componenet backup pof passive one is failed with 156

How is this solved then?

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

21
Jun
2012

update..

I think shadow copy component switch to active node and in my case it is completed for active node.

as it switched to active node then it must be failed for passive node??

 

I thought this would be happen. Marianne please clear this doubt

Marianne
Trusted Advisor
Accredited
Certified
22
Jun
2012

No, only shared data fails

No, only shared data fails over, not SCC.

You need to troubleshoot snapshot error on passive node.

The following 2 TNs may help:

http://www.symantec.com/docs/TECH128805

http://www.symantec.com/docs/TECH76141

 

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

22
Jun
2012

Question

Is the D:\ volume a clustered resource and therefore only available on the active node of a standard Windows cluster?

Is so, and if the backup selections contain D:\ for example the jobs should fail for the passive node.  Are you able to confirm that this is the case?

Is so I would agree with Yogesh9881 and use the Virtual Name and let the cluster do the work ;)

25
Jun
2012

dont know why??

but in my case only shadow copy component fails with 156 and rest completed successfully for inactive node and active node completed successfully

Marianne
Trusted Advisor
Accredited
Certified
25
Jun
2012

Have you had a look at TNs

Have you had a look at TNs mentioned in this post: https://www-secure.symantec.com/connect/forums/fai... ?

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

25
Jun
2012

did not get from tech note

Sorry, but i did not get from tech note. Can u plz explain

 

Marianne
Trusted Advisor
Accredited
Certified
25
Jun
2012

Which part of which TN ?

Which part of which TN did you not understand?

http://www.symantec.com/docs/TECH128805
explains the environment/conditions under which problem is seen, it tells you about a new binary that can be downloaded enables you to type a command that '-ignore_unresolved_volumes'. This binary is included in 7.1.0.2 (seems your cluster nodes are on unpatched 7.1).

http://www.symantec.com/docs/TECH76141
gives a registry key that can be modified.

 

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