Forum Discussion

Jim_Hellewell's avatar
10 years ago

NBU 7.6 fails to backup using policy-type "Enterprise-Vault"

Hello All,

I am trying to backup my Enterprise Vault 10.0.4 data (Indexes, SQL and Vaul stores) using NetBackup 7.6.0.1. I can get the backup to work if I use MS-Windows as the Policy-type, but it always fails when I try to use Enterprise-Vault as the Policy_type - the error is client/server handshaking failed(26)

I have modified VSS on the Enterprise Vault server to use unlimited space as suggested inn one of the tech articles

Can anyine help me with this ?

The details are:-

Note that this is all running as VMware VMs on my Laptop:
EV Environment
EV ver 10.0.4
EV Site = EVARCHIVE
EV server - EV.link2.com  (windows 2008 R2)
Windows firewall off

DC=DC2.link2.com (Windows 2008 R2) - this is also the SQL server
SQL Server version is 2008 R2

NetBackup Environment
NBU ver = 7.6.0.1
NBU Master = NBU76Master  (windows 2008 R2)
NBU Media = NBU76Media (Windows 2008 R2)

Windows firewall off

Name resolution works OK from all my servers.

Note that Enterprise Vault work OK, and NetNbackup works OK

I can backup up the SQL server OK using ther MS-SQL agent
I can backup flat files on the EV2 server OK when the Policy-type is MS-Windows.

The backup always fails when I try to use Enterprise-Vault as the Policy-Type
I have created a new policy,with the following options:-
Name:- EV_Index
Policy-type - Enterprise-Vault
Client - EV2
backup Selection - Chose Enterprise Vault 10 and selected EV_INDEX_LOCATION= from the available list, and then manually entered the EV Site name, so the backup selection reads
EV_INDEX_LOCATION=EVARCHIVE

When I manually run the backup job, its fails;
the "Job Overview status" is client/server handshaking failed(26)
The detailed Status is:-

04/12/2014 13:39:32 - Info nbjm(pid=3392) starting backup job (jobid=148) for client EV2, policy EV_Indexes, schedule EV_index_Full 
04/12/2014 13:39:32 - Info nbjm(pid=3392) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=148, request id:{D7CAAB9A-81A1-4952-B0A1-E6C48A08B2BB}) 
04/12/2014 13:39:32 - requesting resource Master_DP1_SU1
04/12/2014 13:39:32 - requesting resource nbu76master.link2.com.NBU_CLIENT.MAXJOBS.EV2
04/12/2014 13:39:32 - requesting resource nbu76master.link2.com.NBU_POLICY.MAXJOBS.EV_Indexes
04/12/2014 13:39:32 - granted resource nbu76master.link2.com.NBU_CLIENT.MAXJOBS.EV2
04/12/2014 13:39:32 - granted resource nbu76master.link2.com.NBU_POLICY.MAXJOBS.EV_Indexes
04/12/2014 13:39:42 - estimated 0 Kbytes needed
04/12/2014 13:39:42 - begin Parent Job
04/12/2014 13:39:42 - begin Enterprise Vault Resolver, Start Notify Script
04/12/2014 13:39:52 - Info RUNCMD(pid=4264) started           
04/12/2014 13:39:52 - Info RUNCMD(pid=4264) exiting with status: 0        
Status 0
04/12/2014 13:39:52 - end Enterprise Vault Resolver, Start Notify Script; elapsed time: 0:00:10
04/12/2014 13:39:52 - begin Enterprise Vault Resolver, Step By Condition
Status 0
04/12/2014 13:39:52 - end Enterprise Vault Resolver, Step By Condition; elapsed time: 0:00:00
04/12/2014 13:39:52 - begin Enterprise Vault Resolver, Read File List
Status 0
04/12/2014 13:39:52 - end Enterprise Vault Resolver, Read File List; elapsed time: 0:00:00
04/12/2014 13:39:52 - begin Enterprise Vault Resolver, Resolver Discovery
04/12/2014 13:40:02 - started process bpbrm (5240)
04/12/2014 13:40:08 - Info bpbrm(pid=5240) EV2 is the host to restore to     
04/12/2014 13:40:08 - Info bpbrm(pid=5240) reading file list for client       
04/12/2014 13:40:11 - Info bpbrm(pid=5240) client_pid=2156           
04/12/2014 13:40:11 - Info bpbrm(pid=5240) from client EV2: TRV - BPRESOLVER has executed on server (EV2) 
04/12/2014 13:40:11 - Error bpbrm(pid=5240) socket read failed, connection closed       
04/12/2014 13:40:11 - Info bpresolver(pid=2156) done. status: 13: file read failed      
Status 26
04/12/2014 13:40:11 - end Enterprise Vault Resolver, Resolver Discovery; elapsed time: 0:00:19
04/12/2014 13:40:11 - begin Enterprise Vault Resolver, Stop On Error
Status 0
04/12/2014 13:40:11 - end Enterprise Vault Resolver, Stop On Error; elapsed time: 0:00:00
04/12/2014 13:40:11 - begin Enterprise Vault Resolver, End Notify Script
04/12/2014 13:40:21 - Info RUNCMD(pid=1156) started           
04/12/2014 13:40:21 - Info RUNCMD(pid=1156) exiting with status: 0        
Status 0
04/12/2014 13:40:21 - end Enterprise Vault Resolver, End Notify Script; elapsed time: 0:00:10
Status 26
04/12/2014 13:40:21 - end Parent Job; elapsed time: 0:00:39
client/server handshaking failed(26)

 

 

5 Replies

  • Jim,

     

    Please add a EV Service Account Credentials under Client Properties and give the permission in the enterprise vault directory Access Management.

    Note: Service Account should have a access to put the EV Partition to the Backup Mode.

    It will resolve issue. Cheers !!

     

    Test.jpg

  • thankyou

     

    Riaan, I don't have or can't find a bpresolver.log file ; do I need to enable this somehow ?

    I have looked in c:\program file\veritas\netbackup\logs on my Master Server and media server and don't see it anywhere.

    I will double check the service account properties, but I am sure I added the account.

    regards

     

    Jim

  • Take a look at the bpresolver log. its should tell you what the issue is. Did you add the username/password for service account to the host properties?