Netbackup 6.5 Backups Fail with Status Code 46

[Jim_Haywood]

Hello!

I've got a Netbackup 6.5 error. This setup has just been installed.

We have a server with a directly connected autoloading SCSi tape drive.  the server needs to be backed up locally to this drive. The data also needs to be encrypted. (But haven't got that far yet)

So I've made this server both the Netbackup Master server and also the Media server. Tape drive seems to have installed fine, and can happily churn out a catalog backup and inventory the libary

To test it backing up an actual file to tape, I've just created a policy backing up one file. When run, it fails with status code 46.

When I run vxlogview, the line that jumps out at me as being the problem is:

"The NBU client version is incompatible with the NBU master server."

But as the server that I am trying to back up is also the master and media server, it won't let me install a client onto the machine. What do I need to do to get local backups working? After this comes the next hurdle of getting encryption working, but I can't approch that issue until I can actually get non-encrypted data backed up!


The whole output of vxlogview -i 121 is:

23/01/2008 12:10:54.328 [stringManipulation.cpp:Split()] Invalid input parameters, exiting, line=49
23/01/2008 12:11:49.093 V-128-754 [regutils.cpp:GetRegistryString2()] Could not get data from the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\HomeDirectory, return code = 2
23/01/2008 12:11:50.765 V-128-754 [regutils.cpp:GetRegistryString2()] Could not get data from the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\ImagePath, return code = 2
23/01/2008 12:11:50.953 [CBmrSaveCfg.cpp:sendDiscovery()] BMROP_IMPORT failed, rc=199
23/01/2008 12:11:50.953 [Error] V-121-27 Failed to import Config file.
23/01/2008 12:11:50.953 [CBmrSaveCfg::discover()] Failed sending the discovery, rc=199, mode=1
23/01/2008 12:11:50.953 [Error] V-121-21 Failed sending the discovery.
23/01/2008 12:11:50.953 [main.cpp:bmrmain()] The NBU client version is incompatible with the NBU master server.
23/01/2008 12:11:50.953 [Error] V-121-71 The NBU client version is incompatible with the master server.
23/01/2008 12:36:53.906 [stringManipulation.cpp:Split()] Invalid input parameters, exiting, line=49
23/01/2008 12:37:48.578 V-128-754 [regutils.cpp:GetRegistryString2()] Could not get data from the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base\HomeDirectory, return code = 2
23/01/2008 12:37:50.015 V-128-754 [regutils.cpp:GetRegistryString2()] Could not get data from the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\ImagePath, return code = 2
23/01/2008 12:37:50.093 [CBmrSaveCfg.cpp:sendDiscovery()] BMROP_IMPORT failed, rc=199
23/01/2008 12:37:50.093 [Error] V-121-27 Failed to import Config file.
23/01/2008 12:37:50.109 [CBmrSaveCfg::discover()] Failed sending the discovery, rc=199, mode=1
23/01/2008 12:37:50.109 [Error] V-121-21 Failed sending the discovery.
23/01/2008 12:37:50.109 [main.cpp:bmrmain()] The NBU client version is incompatible with the NBU master server.
23/01/2008 12:37:50.109 [Error] V-121-71 The NBU client version is incompatible with the master server.




The detailed status of the failed job is below:


+++++++++++++++++++++++++

23/01/2008 12:36:53 - collecting BMR information
23/01/2008 12:36:53 - connecting
23/01/2008 12:36:53 - connected; connect time: 00:00:00
23/01/2008 12:36:53 - transferring BMR infomation to the master server
23/01/2008 12:36:53 - connecting
23/01/2008 12:36:53 - connected; connect time: 00:00:00
23/01/2008 12:36:53 - requesting resource Any
23/01/2008 12:36:53 - requesting resource SERVERNAME.NBU_CLIENT.MAXJOBS.127.0.0.1
23/01/2008 12:36:53 - requesting resource SERVERNAME.NBU_POLICY.MAXJOBS.LocalHostTest
23/01/2008 12:36:53 - granted resource SERVERNAME.NBU_CLIENT.MAXJOBS.127.0.0.1
23/01/2008 12:36:53 - granted resource SERVERNAME.NBU_POLICY.MAXJOBS.LocalHostTest
23/01/2008 12:36:53 - granted resource A00005
23/01/2008 12:36:53 - granted resource HP.ULTRIUM3-SCSI.000
23/01/2008 12:36:53 - granted resource SERVERNAME-hcart3-robot-tld-0
23/01/2008 12:36:53 - estimated 0 kbytes needed
23/01/2008 12:36:53 - begin Parent Job
23/01/2008 12:36:53 - begin Bare Metal Restore , Start Notify Script
Status 26
23/01/2008 12:36:53 - end Bare Metal Restore , Start Notify Script; elapsed time: 00:00:00
23/01/2008 12:36:53 - begin Bare Metal Restore , BMR Save
23/01/2008 12:36:53 - started process bpbrm (4140)
23/01/2008 12:37:49 - Error bpbrm(pid=4140) BMRERR: Received BMR error: The driver for HP NC373i Virtual Bus Device is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore. (1)
23/01/2008 12:37:50 - Error bpbrm(pid=4140) BMRERR: Received BMR error: Failed to import Config file. (1)   
23/01/2008 12:37:50 - Error bpbrm(pid=4140) BMRERR: Received BMR error: Failed sending the discovery. (1)    
23/01/2008 12:37:50 - Error bpbrm(pid=4140) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)
23/01/2008 12:37:50 - end writing
Status 1
23/01/2008 12:37:55 - end Bare Metal Restore , BMR Save; elapsed time: 00:01:02
23/01/2008 12:37:55 - begin Bare Metal Restore , Policy Execution Manager Preprocessed
Status 46
23/01/2008 12:47:59 - end Bare Metal Restore , Policy Execution Manager Preprocessed; elapsed time: 00:10:04
23/01/2008 12:47:59 - begin Bare Metal Restore , Stop On Error
Status 0
23/01/2008 12:47:59 - end Bare Metal Restore , Stop On Error; elapsed time: 00:00:00
23/01/2008 12:47:59 - begin Bare Metal Restore , End Notify Script
Status 26
23/01/2008 12:47:59 - end Bare Metal Restore , End Notify Script; elapsed time: 00:00:00
Status 46
23/01/2008 12:47:59 - end Parent Job; elapsed time: 00:11:06
server not allowed access(46)


Any help would be greatly appriciated!

Jim

[ahlip · Accepted solution]

Hi Jim,

The messages show that the BMR pre-script is failing. Typically, the main backup job should still go on after that, but in your case, BMR triggered more severe errors, causing the backup job to fail without ever going into the main backup task.

Firstly, go to the backup policy and uncheck the box "collect BMR information". Rerun the backup. It should have no issue.

2ndly, patch your machine up to the latest release update 6.5.1 (released 5th Dec).

Your BMR error concerns the windows driver for the hardware "HP NC373i Virtual Bus Device". Do try to install newer driver or to downgrade to a default windows driver. Then retry backup with BMR option enabled.

Again, if you are not going to use BMR (hope you know how this option works and the requirements), you can permanantly uncheck the BMR option.


regards,
Lipz

[Jim_Haywood]

Amazing! Unticking that box seemed to work! My test backups are now sucessful. To be honest, I have no idea what Bare Metal Restore is, so I'm going to have to read up on that before undoing all the hard work so far by playing around with drivers...

Thanks very much for that!

Now I'm trying to implement Encryption. End result: Data that is stored on tape is encrypted, as it will be stored off site. There's no need to encrypt it accross the network, because of course the material that is being backed up is local to the media server!

I will raise this as a seperate thread if requested, but I think here is the best place for the issue for the mo... My main problem here is lack of understanding, I'm sure of it. I've taken that previously working test policy, and done the following:

 - Policy -> Encryption (Ticked)  

 - Client -> Host Properties -> Encryption.
      Tick 'required'.
      Tick 'Enable Encryption'
      Choose 'AES-128-CFB' as the Client Cipher

When I try and run the test backup now, it fails with Status 184.

The detailed summary states:
23/01/2008 15:47:40 - requesting resource Any
23/01/2008 15:47:40 - requesting resource SERVERNAME.NBU_CLIENT.MAXJOBS.127.0.0.1
23/01/2008 15:47:40 - requesting resource SERVERNAME.NBU_POLICY.MAXJOBS.LocalHostTest
23/01/2008 15:47:40 - granted resource SERVERNAME.NBU_CLIENT.MAXJOBS.127.0.0.1
23/01/2008 15:47:40 - granted resource SERVERNAME.NBU_POLICY.MAXJOBS.LocalHostTest
23/01/2008 15:47:40 - granted resource A00007
23/01/2008 15:47:40 - granted resource HP.ULTRIUM3-SCSI.000
23/01/2008 15:47:40 - granted resource SERVERNAME-hcart3-robot-tld-0
23/01/2008 15:47:40 - estimated 7 kbytes needed
23/01/2008 15:47:40 - started process bpbrm (372)
23/01/2008 15:47:40 - connecting
23/01/2008 15:47:40 - connected; connect time: 00:00:00
23/01/2008 15:47:42 - mounting A00007
23/01/2008 15:48:30 - mounted; mount time: 00:00:48
23/01/2008 15:48:33 - positioning A00007 to file 4
23/01/2008 15:48:37 - positioned A00007; position time: 00:00:04
23/01/2008 15:48:37 - begin writing
23/01/2008 15:49:36 - Critical bpbrm(pid=372) from client 127.0.0.1: FTL - tar had an unexpected error  
23/01/2008 15:49:48 - Error bpbrm(pid=372) could not send server status message      
23/01/2008 15:49:48 - end writing; write time: 00:01:11
tar had an unexpected error(184)


If anyone can offer me any guidance on this or point me in the right direction, I'd be very grateful. And I am already to ahlip... Thank you very much!! :)

[ahlip]

Hi Jim,

Do check the 6.5 Security and Encryption guide. If I am not wrong, for Client encryption, you have to create a keyfile in the client based on a password you enter. Encryption always needs a reference or a "seed", a password is usually used as the seed for symmetric (AES, blowfish) encryption.

[Jim_Haywood]

Hmm... Seemed to work well that. Test backups are working so let's hang on for the real deal tonight... For those who are following the thread:

 - Confirm there are licence keys with lots of nice mentions of encryption

On Microsoft Windows clients, you must allow server-directed restores, as follows:
 - Open the Backup, Archive, and Restore utility.
 - Select File > NetBackup Client Properties.
 - On the General tab of the NetBackup Client Properties dialog, select the 'Allow Server Directed Restores' box.

Run the following commandfrom the server to install the encryption option on the client.
   bpinst -ENCRYPTION client_name
(install_path\NetBackup\bin\)

Generate an encryption key for the client. Run the following from the server...
   bpkeyutil -clients client_name
(install_path\NetBackup\bin\)

It'll ask you for an encryption key. You need to store this muckker in a safe place in case it gets corrupted. That coupled with what I've outlined above should see you right. But it really is a good idea to read the guide that ahlip mentioned. It's where I got my info from and will contain extra bits y'all need to understand.

[NBU_13]

Hi,

If Backup job failed with EC46.(The server is trying to access a client but access is blocked)

Possible reason as :

1. Server is not listed on the client as a valid server.

2.Server has been configured to require encrypted backups, but the encryption attribute has not been selected for the Backup Policy.

3.The evaluation license for the NetBackup encryption product has expired.

[S__Sankara_Nara]

23/01/2008 12:37:50.109 [main.cpp:bmrmain()] The NBU client version is incompatible with the NBU master server.
23/01/2008 12:37:50.109 [Error] V-121-71 The NBU client version is incompatible with the master server.


23/01/2008 12:37:50 - Error bpbrm(pid=4140) BMRERR: Received BMR error: Failed sending the discovery. (1)
23/01/2008 12:37:50 - Error bpbrm(pid=4140) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)
23/01/2008 12:37:50 - end writing


Resolving this may help u out!!!