Windows clients failing with 13 for System_State:\

[Monu_Puri]

CLIENT:  nxtstwsgrc02 (/Windows2008_x64 6.1 build 7600)
VERSION: 6.5

Mater server: SunOS pronbu03 5.10 Generic_142900-06 sun4u sparc SUNW,Sun-Fire-V490

Netbackup version: NetBackup-Solaris10 6.5.4

The backup on the windows client fails with error code 13 just for System_State:\. The backup runs in multiple streams and rest gets completed without any issues.

I tried to exclude System_State:\ however no luck.

Please assist.

[Kiran_Bandi]

Is the client on Win 2k8 R2?

If yes NBU should be of version 6.5.5

SCL: http://entsupport.symantec.com/docs/325328

Regards....

[Andy_Welburn]

i.e. any other details for the specific error in  job details, bpbkar log, problems report......

Is this backed up via ALL_LOCAL_DRIVES or are you specifying what to back up?

[rizwan84tx]

Please check if Volume Shadow copy service. System state backup will fail if this service is not responding.

[Monu_Puri]

Hi,

 Volume Shadow copy service was stopped i tried to start it and tried the backup. Then tried to stop it again and tried the backup it’s still the same.

Yes, its Win 2k8 R2 so I am in process of getting NBU version upgraded to 6.5.6. Till that time just want to know in case we have any other resolution for it.

It backups up the same amount of data every time for System_State:\ and fails. The backup runs for ALL_LOCAL_DRIVES and then gets divided into 3 streams System_State:\ , C:\ and D:\.

The exclude list contains:

System_State:\

Shadow Copy Components:\

[rizwan84tx]

Can you provide the bpbkar client log (verbose 5)

[Monu_Puri]

See the attachments

[rizwan84tx]

bpcd show mismatch in master server comparison

22:28:10.279 [7032.3628] <16> bpcd main: Server access denied
22:28:10.389 [1480.6652] <2> bpcd main: offset to GMT 28800
22:28:10.389 [1480.6652] <2> bpcd main: Got socket for input 276
22:28:10.389 [1480.6652] <2> logconnections: BPCD ACCEPT FROM 10.133.66.62.54722 TO 10.133.66.62.13724
22:28:10.389 [1480.6652] <2> bpcd main: setup_sockopts complete
22:28:10.436 [1480.6652] <2> bpcd peer_hostname: Connection from host NXTSTWSGRC02.gsm1900.org (10.133.66.62) port 54722
22:28:10.436 [1480.6652] <2> bpcd valid_server: comparing pronbu01.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu01 and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu02 and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu03 and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu02.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu03.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu10.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu11.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu12.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu13.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu14.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu21.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu22.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu23.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <2> bpcd valid_server: comparing pronbu24.unix.gsm1900.org and NXTSTWSGRC02.gsm1900.org
22:28:10.483 [1480.6652] <4> bpcd valid_server: NXTSTWSGRC02.gsm1900.org is not a master server
22:28:10.483 [1480.6652] <16> bpcd valid_server: NXTSTWSGRC02.gsm1900.org is not a media server either
22:28:10.483 [1480.6652] <2> bpcd main: output socket port number = 1
22:28:10.498 [1480.6652] <2> bpcd main: Duplicated vnetd socket on stderr
22:28:10.498 [1480.6652] <2> bpcd main: <---- NetBackup 6.5 0 ------------initiated
22:28:10.498 [1480.6652] <2> bpcd main: VERBOSE = 0
22:28:10.498 [1480.6652] <2> bpcd exit_bpcd: exit status 46  ----------->exiting
22:28:10.498 [1480.6652] <4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46
 

Is this the problematic client?

Can you also post the detail status of the job from activity monitor?

[Monu_Puri]

Apr 20, 2011 12:01:05 AM - estimated 0 kbytes needed
Apr 20, 2011 12:01:07 AM - started process bpbrm (pid=8455)
Apr 20, 2011 12:01:08 AM - connecting
Apr 20, 2011 12:01:09 AM - connected; connect time: 0:00:00
Apr 20, 2011 12:01:18 AM - begin writing
Apr 20, 2011 12:01:35 AM - Warning bpbrm (pid=8455) from client nxtstwsgrc02: WRN - can't open directory: System State:\Task Scheduler Writer (WIN32 536935992: Unknown error)
Apr 20, 2011 12:01:35 AM - Error bpbrm (pid=8455) from client nxtstwsgrc02: ERR - Error encountered while attempting to get additional files for System State:\
Apr 20, 2011 12:01:38 AM - Warning bpbrm (pid=8455) from client nxtstwsgrc02: WRN - can't open directory: System State:\VSS Metadata Store Writer (WIN32 536935992: Unknown error)
Apr 20, 2011 12:01:39 AM - Warning bpbrm (pid=8455) from client nxtstwsgrc02: WRN - can't open directory: System State:\Performance Counters Writer (WIN32 536935992: Unknown error)
Apr 20, 2011 12:29:45 AM - Error bpbrm (pid=8455) socket read failed: errno = 131 - Connection reset by peer
Apr 20, 2011 12:29:48 AM - Error bptm (pid=8492) system call failed - Connection reset by peer (at child.c.1296)
Apr 20, 2011 12:29:49 AM - Error bptm (pid=8492) unable to perform read from client socket, connection may have been broken
Apr 20, 2011 12:29:50 AM - Error bptm (pid=8483) media manager terminated by parent process
Apr 20, 2011 12:36:27 AM - Error bpbrm (pid=8455) could not send server status message
Apr 20, 2011 12:36:29 AM - end writing; write time: 0:35:11
file read failed (13)
 

[Anton_Panyushki]

I presume the client OS is W2008R2. According to this technote http://www.symantec.com/docs/TECH74870 this OS is has been suppoeted since 6.5.5.

Consider NetBackup upgrade.

[rizwan84tx]

Can you confirm if the backup for files/Directory or drives backup completes sucessfully?

Please post the output of below commands

From master server

/usr/openv/netbackup/bin

bpclntcmd -get_remote_host_version <host name>

From the client

bpclntcmd -pn

[RonCaplinger]

You didn't specify it, but we are assuming you know that the NBU master and media server(s) must be at the same or higher version of NetBackup than the clients, correct?  You can't have a 6.5.4 master server and a 6.5.6 client.  The master server must be the same or higher than the media server(s), which in turn must be the same or higher than the clients.

Also, you may need to go into the Master Server properties and under Client Attributes, change the Windows Open File Backup option to use VSS instead of VSP, as VSP is not supported on 2008.

[Monu_Puri]

The backups are divided into 3 streams as follows:

System_State:\          Failing
C:\                            Successful
D:\                            Successful

Media Server:
CLIENT:  pronbu21 (sun4v/SunOS 5.10 Generic_142900-13)
VERSION: NetBackup-Solaris10 6.5.4

Master Server:
CLIENT:  pronbu01 (sun4u/SunOS 5.10 Generic_142900-06)
VERSION: NetBackup-Solaris10 6.5.4

Client:
CLIENT:  nxtstwsgrc02 (/Windows2008_x64 6.1 build 7600)
VERSION: 6.5

I have checked by logging into the client and its 6.5.4.

The Windows Open File Backup option remains disabled in our environment for all our clients.

bpclntcmd -get_remote_host_version nxtstwsgrc02
6.5

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server pronbu01.unix.gsm1900.org
nxtstwsgrc02.gsm1900.org nxtstwsgrc02 10.133.66.62 51287

.

[Amit_Karia]

Do you have trend micro installed in your client?

[Monu_Puri]

No we have Symantec Endpoint Protection.

[Marianne]

Consider yourself lucky to backup anything successfully on the W2008R2 client while on 6.5.4.

There is normally a very good reason for support introduced with a certain patch level.

[Monu_Puri]

My master and media have got 6.5.4 so I suppose that would not be suggested.

I removed the 6.5.4 patch and installed it again. The backup for System_State:\ got partially successful. So its fine as of now as we don’t get failures. Rest in case we have any other valuable thought please share.

Well Marianne you are right I am the lucky one.

Thanks to all for the help and support. Much appreciated !!!! You guys rock.

[Anton_Panyushki]

The Windows build number of your client is 6.1 build 7600 which literally means that it is Windows 2008 R2. Please check this topic http://en.wikipedia.org/wiki/Windows_NT for Windows build vs Windows version comparison table. As I said before, Windows 2008 R2 is not officially supported in NetBackup 6.5.4. The support of Win2008R2 starts in 6.5.5 - http://www.symantec.com/docs/TECH74870 .

Nevertheless, 6.5.6 client and 6.5.4 server can talk to each over because the communication protocol in 6.5.6 is the same as in 6.5.4.

Thre is the bpgetconfig output taken from one of my 6.5.6 clients. I marked communication protocol version.

 bpgetconfig  -A -s dc1 -L
Client/Master = Client of master
NetBackup Client Platform = PC, Windows2000
NetBackup Client Protocol Level = 6.5.4
Product = NetBackup
Version Name = 6.5
Version Number = 650000
NetBackup Installation Path = C:\Program Files\VERITAS\NetBackup\bin
Client OS/Release = Windows2003 5
Cipher = AES-128-CFB
Cipher = BF-CFB
Cipher = DES-EDE-CFB
Cipher = AES-256-CFB
Patch Level = 6.5.6

Consequently, you can install 6.5.6 on the client in question, configure the client properly and try to backup Windows System State.