12-19-2013 07:02 AM
Need some help on what is causing our snapshot issues on three different clients. Any help is much appreciated.
Environment:
Windows Server 2008R2 Master/Media Server (NetBackup 7.5.0.6)
NetBackup 5220 Appliance (Media Server 7.5.0.6 firmware 2.5.3)
IBM TS3200 Library
Backing up client via MS-Windows policy type with the below Backup Selection
- Shadow Copy Components
-C:\
Detailed Status:
12/19/2013 8:48:31 AM - Info nbjm(pid=2428) starting backup job (jobid=464633) for client USXHQSQLT2PRDC2, policy SQL_Wkend_SRV_HQ, schedule SQL_Server_Weekly_Full
12/19/2013 8:48:31 AM - estimated 101301279 Kbytes needed
12/19/2013 8:48:31 AM - Info nbjm(pid=2428) started backup (backupid=USXHQSQLT2PRDC2_1387460911) job for client USXHQSQLT2PRDC2, policy SQL_Wkend_SRV_HQ, schedule SQL_Server_Weekly_Full on storage unit stu_disk_USXHQBCKSYM
12/19/2013 8:48:32 AM - started process bpbrm (31571)
12/19/2013 8:48:33 AM - Info bpbrm(pid=31571) USXHQSQLT2PRDC2 is the host to backup data from
12/19/2013 8:48:33 AM - Info bpbrm(pid=31571) reading file list from client
12/19/2013 8:48:34 AM - Info bpbrm(pid=31571) the client does not support accelerator, switch to regular backup
12/19/2013 8:48:34 AM - connecting
12/19/2013 8:48:35 AM - Info bpbrm(pid=31571) starting bpbkar on client
12/19/2013 8:48:35 AM - connected; connect time: 00:00:01
12/19/2013 8:49:21 AM - Info bpbkar(pid=19092) Backup started
12/19/2013 8:49:21 AM - Info bpbrm(pid=31571) bptm pid: 31609
12/19/2013 8:49:22 AM - Info bptm(pid=31609) start
12/19/2013 8:49:22 AM - Info bptm(pid=31609) using 1048576 data buffer size
12/19/2013 8:49:22 AM - Info bptm(pid=31609) using 64 data buffers
12/19/2013 8:49:28 AM - Info bptm(pid=31609) start backup
12/19/2013 8:49:31 AM - Info bptm(pid=31609) backup child process is pid 31621
12/19/2013 8:49:31 AM - begin writing
12/19/2013 8:49:52 AM - Error bpbrm(pid=31571) from client USXHQSQLT2PRDC2: ERR - Volume resolution error for (System State:\System Files\System Files)
12/19/2013 8:49:52 AM - Error bptm(pid=31621) system call failed - Connection reset by peer (at child.c.1298)
12/19/2013 8:49:52 AM - Error bptm(pid=31621) unable to perform read from client socket, connection may have been broken
12/19/2013 8:49:53 AM - Error bptm(pid=31609) media manager terminated by parent process
12/19/2013 8:49:56 AM - Info usxhqbcksym(pid=31609) StorageServer=PureDisk:usxhqbcksym; Report=PDDO Stats for (usxhqbcksym): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%
12/19/2013 8:49:56 AM - Error bpbrm(pid=31571) could not send server status message
12/19/2013 8:49:56 AM - Info bpbkar(pid=19092) done. status: 156: snapshot error encountered
12/19/2013 8:49:56 AM - end writing; write time: 00:00:25
snapshot error encountered(156)
Solved! Go to Solution.
12-19-2013 07:19 AM
hi,
I would suggest you to start with the below tech note and follow the steps listed on it
12-19-2013 07:19 AM
hi,
I would suggest you to start with the below tech note and follow the steps listed on it
12-19-2013 01:30 PM
Please tell us more about the client - as this is where the problem is:
OS? Version and patch level.
NBU version and patch level?
Part of a cluster?
12-19-2013 03:12 PM
Client
OS= Windows Server 2008 R2
NBU= 7.1.0.3
SQL Cluster = All 3 clients having issues are part of the Cluster.
12-19-2013 09:24 PM
you may need to use the Ignore un resolved volues in the all the 3 cluster nodes
http://www.symantec.com/business/support/index?page=content&id=TECH128805
tech note says its been resolved in 7.1.0.1 but worth checking and trying..
12-19-2013 09:31 PM
Nagalla is right - use the w2koption command on the cluster nodes.
The patch has 'fixed' the problem in the sense that the w2koption attributes were added in the patch which allows you to run the command with -ignore_unresolved_volumes. This option did not exist before 7.1.0.1.
12-19-2013 09:49 PM
Check if below helps
http://www.symantec.com/docs/TECH176793
12-20-2013 09:41 AM
Nagalla - I tried this http://www.symantec.com/docs/TECH47808, and all worked as expected.
I will give the other solutions a try and report back.