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

vmware VADP backup cannot connect on socket (25)

Created: 21 Feb 2013 • Updated: 11 Mar 2013 | 5 comments
This issue has been solved. See solution.

hi 

we have a windows vadp vmware backup running that runs a query against the properties of the VM guest and backs it up if it matches. One of the hosts was renamed in VMWare and windows and now runs a successfull backup but also logs a failed backup for the old name

error is :cannot connect on socket (25)

we have changed the "reuse vm selection query result" in the client tab of the policy to 1 minute and ran the query again, the old host name does not show up in the included list and the new quest name shows up.

also have storage vmmotioned the guest and day after day the old name still appears as failed

is there a command or somethign i can run to clear out the old name?

 

thanks

 

daryl 

Operating Systems:

Comments 5 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

Storage VMotion... I suffered from same issue yesterday, and was managed it by removing files under install_path¥NetBackup¥online_util¥fi_cntl.

But I'm not sure this is right way.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Yasuhisa Ishikawa's picture

Please try to remove only vcbnames_*_Any files.

Related Article: http://www.symantec.com/docs/TECH162255

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Daryl Gawn's picture

hi Yasuhisa , thanks for the replys, do I remove them from the master server ,or client ?

Yasuhisa Ishikawa's picture

Perhaps on VMware Access Host. Please check on VMware Backup Host.
If vcbnames_*_Any does not exist on VMware backup host, then, please check on master.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

SOLUTION