error 239

[manatee]

NBU 7.6.0.3

i have this policy that of late, whenever it starts the parent job would give error 239 and a job schedule of *NULL*. there is nothing in the details page to indicate the reason why. it's all blank. so after a while, the child job would timeout.

this went on for several days while i figure out what's went wrong as the policy have been in used for years.

today, i found this link https://www.veritas.com/community/forums/sql-backup-failing-status-239

and following the steps taken there, i was able to fix the error 239 problem.

funny thing is, since the creation of the policy, i've always used the hostname to refer both to the client and the master server. now, i have to use the FQDN of the client in the backup policy to make it work. *shrugs*

[manatee · Accepted solution]

i replied and fixed to my own post.

[Marianne]

Actually, you were simply sharing information.

[manatee]

ok. but the solution and the problem is strange. taken together.

like in my other policies, i only use hostnames but in the client when i do bpclntcmd -self it resolves to a FQDN yet i have no error 239 with them.