media open error (83)

[Aurelien59]

Hello,

I have this error when trying to backup with deduplication a client (windows server 2003 r2).

See logs :

31/07/2017 10:58:55 - Error bpbrm(pid=5428) socket read failed, Accès refusé.  (5)      
31/07/2017 10:59:47 - Critical bptm(pid=6952) sts_open_target_server failed: error 2060023 server is shut down     
31/07/2017 10:59:47 - Critical bptm(pid=6952) failure to open proxy target server srv-media.dkm: plug-in reports error 2060023 server is shut down
31/07/2017 10:59:50 - Info bpbkar32(pid=5136) done. status: 83: media open error       
31/07/2017 10:59:50 - end writing
media open error(83)

Can someone helpme with this ?

Client version : 7.5.0.5

Server version : 7.6.0.3

(sorry for my english)

Thx.

[Marianne]

Are the necessary ports open between client and MSDP server?
And all forward and reverse lookup tested and confirmed? 

See https://www.veritas.com/support/en_US/article.000008432

https://www.veritas.com/support/en_US/article.000008447

[Aurelien59]

Hi Marianne,

All necessary ports are open.

This client has no previous backup on this version. I recently updated it from 4.5 to 7.5.

Now client is running 7.6.0.3, but still fails with error 83 :

31/07/2017 16:35:04 - Critical bpbrm Client Direct Plugin not available (2060024)

[quebek]

Hello

Please disable client side deduplication in the policy - I believe this is not available with 2003 OS... and retry

[Marianne]

Client Side dedupe is supported for Windows 2003 as per the NBU 7.0 - 7.6 OS SCL: http://www.veritas.com/docs/000040842

I agree - disable client side dedupe to see if the backup is going through.

The error is normally a sign that not all of these ports are open between the client and MSDP media server for client-side dedupe:

10102
10082
1556

[Aurelien59]

I disabled client side dedup in Policy, and now it seems that it is backuping well (at least it didnt failed after 2 mins...). I will come back soon to tell if the backup succeed.

[Aurelien59]

it worked fine !

Disabling client side dedup in Policy seems to have more impact than choosing Always use media server in Client Attributes in master's host properties.

[Marianne]

If you want to to use Client Side dedupe again, you really need to verify that all ports mentioned above are open.
Test in both directions from client and MSDP media server using telnet. 

[Aurelien59]

Telnet :

from client to MDSP

1556 OK

10102 OK

10082 OK

from MDSP to client

1556 OK

10102 NOK

10082 NOK

I tried on others clients with client side dedup and I got the same results.

[quebek]

Hi

From MSPD to client only 1556 should worked so I would not be worried about the two other in this direction.

Can you share the file contents version.txt kept on client x:\Program Files\Veritas\NetBackup - where X: is the drive letter on which NBU client binaries are installed...

[Aurelien59]

OK so it is not a problem if others ports are not open.

here is what I got in version.txt :

HARDWARE Windows x86

VERSION Netbackup 7.6.0.1

RELEASE DATE Wed Nov 13 13:27:00 2013

BUILDNUMBER 20131113

[quebek]

Hey

So version is supporting the client side dedupe... Why this is failing... 

can you run this and provide output:

bpclient -client client_name -L

I am running out of ideas kinda... maybe more verbose logging on client, media and master... ie VERBOSE=3 maybe this could shed a light...

[Aurelien59]

bpclient is not recognize as internal command.

I have to run it on MDSP ? Master ? Client ?

How can I change verbose ?

thx a lot for your answers.

[Marianne]

Run the command on the master.

If you don't have the NetBackup folders in your PATH variable, then you have to cd to where NBU is installed (....\NetBackup\bin\admincmd)

[Aurelien59]

M:\Veritas\NetBackup\bin\admincmd>bpclient -client srv-n2broy1-1 -L
 Client Name: srv-n2broy1-1
 Current Host:
 Hostname: srv-n2broy1-1
 Dynamic Address:       no
 Free Browse:   Allow
 List Restore:  Not Specified
 Max Jobs This Client:  Not Specified
 WOFB Enabled:  yes
 WOFB FIM:      VSS
 WOFB Usage:    Individual Drive Snapshot
 WOFB Error Control:    Disable and Continue
 Client Direct: Always use client-side deduplication or
 Always move data direct to storage
 Client Direct Restore: Move data via media server
 OST Proxy:     Off
 OST Proxy Server:      Unspecified
 Connect options:        2 2 3
 Offline:       No