cancel
Showing results for 
Search instead for 
Did you mean: 

VMware backup failling with 4239

amit30
Level 4
Certified

VMBackups are failing with 4239 error. Master is 2008 server and netbackup is 7.6

i tried picking a different method (e.g. display name, DNS name, etc.) but still failing with same error .

Also sometimes its takes old client name even after changing to different name. 

 

Please help.

5 REPLIES 5

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

can you confirm that the Vcetner credentials are validated...? does it only for specific VMs are for all VMs accross the Vcenter?

are you using the Manaul selection of the VM or query based?

if Manual selection.. did you browse and select the VM or just typed the VM name?

DG-2005
Level 5

Create a new policy (not copy)

 > goto client listings and manually selected a client to backup. 

 

I have seen issues when swapping methods of detection for VMs (DisplayName vs DNS Name, etc, etc)

 

 

amit30
Level 4
Certified

Hi RamNagalla,

Yes vcenter credentials are valid. Its for specific VMS not for all.

we tried with both manual and query selection.

In manual section tried both way.

its run with both name i.e vm display and dns name with same time. Not sure why its taking old name . 

Pangal
Level 5

Hi,

          Refer the cache list. Kindly refer below note for details

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

 

amit30
Level 4
Certified

Hi Pangal,

Tried the command to clear the cache but result the same .

 

DG-2005

Created new policy (Not copied) but again taking both old and new client name.