User Initiated - Exit Status 239 - Abnormal exit? 1

[Dorga]

Server: ntabcd622
bpbackup command ran from server: ntabcd622

Problem - Policy exists as below, client is listed in policy, and policy has two user backup schedules. yet, I still get this.

D:\NetBackup\bin>bpbackup -p SQL -s SQL -w c:\autoexec.bat
EXIT STATUS 239: the specified client does not exist in the specified policy

If I disable the policy, and then run the job, I get a 247 (Policy not active). If I remove the client from the policy, I get a 236. If I add a normal schedule, and kick a job off from the master, it works fine.

Ideas? Symantic support can not see past the 239 and insist I need to add the client name.


D:\NetBackup\bin>bppllist sql -U
------------------------------------------------------------

Policy Name: sql

Policy Type: Standard
Active: yes
Effective date: 06/17/2008 12:30:00
Client Compress: no
Follow NFS Mounts: yes
Cross Mount Points: yes
Collect TIR info: no
Block Incremental: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: yes
Interval: 15
Policy Priority: 0
Max Jobs/Policy: 100
Disaster Recovery: 0
Collect BMR info: no
Residence: a_sug
Volume Pool: NetBackup
Keyword: (none specified)

HW/OS/Client: PC Windows2000 ntabcd622

Schedule: SQL_Monthly
Type: User Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 8 (1 year)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00

Schedule: SQL
Type: User Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 00:00:00 --> Friday 24:00:00
Saturday 00:00:00 --> Saturday 24:00:00

 

[Dorga]

Resolved -

The problem was the policy, it was somehow mangeled, creating a new policy with a different name allowed the job to run fine.

So annoying! =)

Thanks for reading!

 

[voyagerman]

or you must use correct client name
check client name from gui in client properties.
best regards

 

[Dorga]

Voyagerman,

The solution for this specific issue had nothing to do with the client, or client name - As stated above.