Video Screencast Help

Make a technote covering proxy errors and clients that don't support client-side dedup.

Created: 20 Sep 2011 • Updated: 21 Sep 2011 | 4 comments
Alexander Kohr's picture
2 Agree
0 Disagree
+2 2 Votes
Login to vote
Status: Implemented

 

Please make a technote solutions similar to the following as I wasted a week worth of working hours trying to debug an issue that appears to be an undocumented unsupported configuration, that was not happening on our other boxes that we had configured into our environment thus far. Our windows XP desktops and our 32Bit windows servers might have run into this issue as well. We have just not gotten there yet.  It would have been super nice to have been able to google this and get an answer and had it fixed in no time.

In reading this items contained between curly brackets {} are comments that I made. I would not expect them in a final document. Not that I expect my wording exactly to end up in a final document anyway. 

If it is not explicitly part of the TOS of this site, I give you rights to reproduce or derive derivative works from any part of this for any purposes you see fit. 

Title: " sts_get_server_prop_byname failed: error 2060057" and "Client Direct plugin not available (2060057)" error possible either succefully backing up or ending with a media open error(83) 

Body:

This error will occurs when Netbackup 7.X {might be 7.1 or even more) is configured with a NetBackup appliance or pure-disk deduplication system such that the master server properties Client Attributes settings for a client are set to either  "Always use Client-side deduplication"  or "prefer to use Client-Side Deduplication", yet the client does not support Client Side Deduplication.  If "prefer to use Client-Side Deduplication" is set the backup will eventually continue to backup. If "Always use Client-side deduplication" is checked the backup will fail with a "media open error(83)"

 

 Clients that don't support client side deduplication. 

All clients less than or equal to 6.5.6  {not tested but assumed, might be a hire number like 7.0.x I don't know},   

NetBackup-MacOSX10.5 clients less than or equal to version 7.1(weather installed on Mac os X 10.5, 10.6, 10.7)   {note I put the 7.1 number in there as there is a idea at http://www.symantec.com/connect/idea/mac-os-x-client-side-deduplication-netbackup-70 that requests this feature}

NetBackup Unix Clients that are not standard install packages. (WARNING! not support a supported configuration by NetBackup in general)

... 

 

Solutions any of the 3 will affectively do the same thing. All three are listed, choose that best fits your environment.

 

1. If the client in question is the only client in the policy or if the policy only contains clients that a producing these proxy errors.

A. Select Activity Monitor -> Policies  and double click on the Policy_Name to open it.

B. Select the Attributes tab and Tick the tick-box for  "Disable client-side deduplication"  (Note this overrides the Master server settings for all the clients in the policy. ) 

 {Note I tested this on a 7.1.0.1 Windows server backing up a NetBackup-MacOSX10.5 7.1 client that had on the master server's properties the Client Attributes set t "Always use client-side deduplication}

 

2. Create an Additional policy specific to boxes that don't support client side deduplication. 

A. Select Activity Monitor -> Policies  aright click on the Policy_Name  and copy the policy by right clicking and selecting Copy_ to new policy. 

B. Give it a new name in the dialog box that appears

C. Tick the tick-box for Disable client-side deduplication

D. Click on the Clients Tab Select and Delete the clients that are in the policy that don't give proxy errors.

E. Click okay

F. Go into the original Policy click on the clients tab, Selected & delete any clients from the list that are having proxy errors.

 

3. Change the client settings in the master server's properties the Client Attributes

A. In the Netbackup Admistration Console select NetBackup Managment -> Host Properties -> Master Servers and right click on Your_Master_Servers_Name and select Properties.

B. Under Properties Select Client Attributes.

C. Scroll down & Select the client with the Proxy issues. 

D. Under Dedupication select Always use the media Server. and click okay.

 

here is an example of my NetBackup activity monitor Job Data if this helps you in making up your TechNote:

 
9/18/2011 6:00:37 PM - Info bpbrm(pid=11460) macosx10.organization.com is the host to backup data from     
9/18/2011 6:01:38 PM - Error bpbrm(pid=11460) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/18/2011 6:01:39 PM - Error bpbrm(pid=11460) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/18/2011 6:02:43 PM - Error bpbrm(pid=11460) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/18/2011 6:02:46 PM - Error bpbrm(pid=11460) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/18/2011 6:03:50 PM - Error bpbrm(pid=11460) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/18/2011 6:03:52 PM - Error bpbrm(pid=11460) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/18/2011 6:04:54 PM - Error bpbrm(pid=11460) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/18/2011 6:04:56 PM - Error bpbrm(pid=11460) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/18/2011 6:05:59 PM - Error bpbrm(pid=11460) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/18/2011 6:06:01 PM - Error bpbrm(pid=11460) sts_get_server_prop_byname failed: error 2060057         
9/18/2011 6:06:02 PM - Error bpbrm(pid=11460) Client Direct plugin not available (2060057) - Disabling Client Direct   
9/18/2011 6:06:05 PM - Info bpbrm(pid=11460) reading file list from client        
9/18/2011 6:06:05 PM - connecting
9/18/2011 6:06:07 PM - Info bpbrm(pid=11460) starting bpbkar32 on client         
9/18/2011 6:06:07 PM - Info bpbkar32(pid=73583) Backup started           
9/18/2011 6:06:07 PM - Info bptm(pid=784) start            
 
 
Or when Always use client side is checked.
 
 
9/20/2011 3:03:08 PM - granted resource MediaID=@aaaaj;DiskVolume=PureDiskVolume;DiskPool=nbapp1;Path=PureDiskVolume;StorageServer=net_appliance.organization.com;MediaServer=Mediaserver.organization.com
9/20/2011 3:03:08 PM - granted resource nbapp1
9/20/2011 3:03:09 PM - estimated 7128982 Kbytes needed
9/20/2011 3:03:09 PM - Info nbjm(pid=3964) started backup job for client client.organization.com, policy Clients-Policy-Name, schedule Daily-Incremental on storage unit nbapp1
9/20/2011 3:03:10 PM - started process bpbrm (7680)
9/20/2011 3:03:11 PM - Info bpbrm(pid=7680) client.organization.com is the host to backup data from     
9/20/2011 3:04:12 PM - Error bpbrm(pid=7680) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/20/2011 3:04:12 PM - Error bpbrm(pid=7680) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/20/2011 3:05:14 PM - Error bpbrm(pid=7680) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/20/2011 3:05:14 PM - Error bpbrm(pid=7680) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/20/2011 3:06:16 PM - Error bpbrm(pid=7680) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/20/2011 3:06:16 PM - Error bpbrm(pid=7680) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/20/2011 3:07:19 PM - Error bpbrm(pid=7680) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/20/2011 3:07:19 PM - Error bpbrm(pid=7680) sts_get_server_prop_byname failed: error 2060057 - retrying       
9/20/2011 3:08:21 PM - Error bpbrm(pid=7680) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1  
9/20/2011 3:08:21 PM - Error bpbrm(pid=7680) sts_get_server_prop_byname failed: error 2060057         
9/20/2011 3:08:21 PM - Critical bpbrm(pid=7680) Client Direct plugin not available (2060057)       
9/20/2011 3:08:24 PM - end writing
media open error(83)
 

Comments 4 CommentsJump to latest comment

Todd D. Woodward's picture

A SymWISE document has now been created, and will be published soon:

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

Thank you for suggesting this.

Todd D. Woodward
IT Supervisor, SOC Shift Lead – Appliances SOC
Symantec Corporation
www.symantec.com

Springfield, Oregon

 

 

0
Login to vote
Alexander Kohr's picture

There is a media Open error (83)page       http://www.symantec.com/docs/HOWTO36379      that apears twice when you are searching the NetBackup Enterprise Server Search Results at http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=Media+open+error+%2883%29&product_finder=NetBackup+Enterprise+Server&productselectorkey=15143&myclicker.x=0&myclicker.y=0

 

It looks like is supposed to cover the general error Media Open Error (83) message as it says see the following possible causes with how to troubleshoot.  It is wofully under popluated with all of the potential issues that you find for that error. If this is not the general how to deal with this error then it's title should be changed. If it is a general debug then something to reference article 170005 should go in there as well as references to probably a dozen other articles that show up in a search for "media Open error (83)" so that it is the general page.

 

Thanks again for your help and for so quickly getting a document up about the issue. Hopefully it helps others. 

+1
Login to vote
Todd D. Woodward's picture

HOWTO articles are mostly taken directly from our manuals, so I unfortunately I can't edit HOWTO36379. However, I did place a link to HOWTO36379 from TECH170005 which should help.

Todd D. Woodward
IT Supervisor, SOC Shift Lead – Appliances SOC
Symantec Corporation
www.symantec.com

Springfield, Oregon

 

 

0
Login to vote
SYMAJ's picture

I know this is now an old post, but if anyone is still watching I would like to clarify one point made above:

"NetBackup Unix Clients that are not standard install packages. (WARNING! not support a supported configuration by NetBackup in general)"

For Unix clients I use the client packages available from the landing page of the appliances, as opposed to the Unix Client package downloaded from Symantec.  I am hoping the tar's available on the appliance are not classed as "not standard install packages" ?

Bottom line is should client side de-dup work OK when using the client packages downloaded from the appliance (2.5.1 / 7.5.0.4) ?

AJ 

0
Login to vote