Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NBU for VMware : EC39 Client name mismatch

Created: 05 Dec 2012 • Updated: 14 Jan 2013 | 3 comments
This issue has been solved. See solution.

Hi

We have backup proxy host which is also a VM. it has NBU 7.1

Master server 7.1.0.4, sun solaris 10.

Media server 7.1 , sun solaris 10.

Backups of VM's are faling with EC39.

 

Please suggest on this.

Comments 3 CommentsJump to latest comment

Stuart Green's picture

Please give more info about the policy type/mode your using. Hot-Add or NBD.

Can you snapshot the VM within vsphere.

Anything else you tried to resolve the issue. Has this stopped working or ever worked.

Are the LUNs accessible to the backup-proxy host.

Follow practices in the NetBackup Vmware guide for using a VM as a proxy host.

 

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

ChAmp35's picture

Policy type is  Falsh Backup windows, transfer mode is tryall

Yes, it is possible to take snapshots manually.

I just went through bpcd , bpfis logs on VM backup host .. found nothing in them, Bpbkar logs are not generating.

This is new Infrastructure, so it has never worked.

Could u please let me know how to check if LUNs accessible to the backup-proxy host ?

 

 

ChAmp35's picture

This issue got resolved by chanaging value of media multiplexing to 1 from 12 in schedules of policy.

Actually it was bug in 7.1 client version installed on the backup proxy host, which got fixed with this work around and this issue does not appear in NBU 7.1.0.4 version.

SOLUTION