Showing results for 
Search instead for 
Did you mean: 

Catalog Archive: Exit with status 239

Level 3
Hi all,
Maybe someone can shed some light on this topic.
Basically we need to archive off some of our catalog. Using the bpcatlist - client all -before <date>, I can view what images are stored online.
However as soon as I add:
| bpcatarc | bpcatrm I get the error message:
Exit Status 239: the specified client does not exist in the specified policy
So of course this points to a problem with policy. I've recreated this policy many times, it's a standard policy named 'catarc', I've made it 'inactive' and I put in the correct backup selection and correct 'client name'. I've checked these multiple times.
Let me know if you need some more info but at the moment I'm somewhat stuck for ideas.


Level 6
Employee Accredited Certified
Everybody needs to include their operating systems and NetBackup version when starting threads here.

Level 6
Employee Accredited Certified
Let's see that policy, too, if that's OK with you.  (I suspect the policy type may be wrong?)

Level 3
version is 5.1 and OS is solaris 8

Level 3
poicy configuration is correct..

Level 6
Partner Accredited
Peraps a Name resolution problem,

NetBackup is very ogrish about it,

a lot of different status when that happens.

I have to force it up, /etc/hosts in every hosts.

see ya

Level 4
The catarc policy should be active and also ensure the time window is set correctly for when you want to do it.


Level 6
  • Make sure you uncheck the Active field. This policy must remain inactive at all times. The bpcatarc command will activate this policy when it performs a catalog backup and then deactivate the policy once it is complete.

Level 6
The following steps can be taken to create a catalog archiving policy. There are several features that are specific to a catalog archiving policy.  

For example:
  • The policy must be named catarc.  
  • The policy must also be inactive.  
  • The catalog archiving commands must be done manually. The administrator must specify a list of files to archive using the bpcatlist command. As a result, there isn't a way to run scheduled catalog archiving backups.

To create the policy in the GUI, do the following:
1. Go to the Policies tab in the GUI and create a new policy
2. For the Policy name: enter catarc
3. For the Policy type: enter Standard
4. Select the storage unit and volume pool you want to use for catalog archiving
5. Clear the Active. Go into effect at: check box. The policy is not run by the scheduler. Rather the bpcatarc command activates this special policy to perform a catalog backup job, then deactivates the policy after the job is done.
6. Accept the defaults for all the other options in the Attributes tab of the policy

Next, create a schedule for the catarc policy.
7. Go to the Schedules tab of the policy
8. Create a new schedule. You can enter any name for the schedule. Only the policy name must be catarc. It is valid to name the schedule catarc as well.
9. Set the Type of backup: to be User Backup
10. Select a retention level for the catalog archive. This must be at least as long as the longest retention period being archived.
Note: Failure to set the retention level of the catalog archive for a time at least as long as the longest retention period of the backups being archived can result in the loss of catalog data.
11. Accept the defaults for all the other options in the Schedule tab of the policy
12. Go to the Start Window tab in the schedule. Enter a backup window for when the catalog archiving commands can be run by the administrator.

Finally, complete the Backup Selections and Clients tab entries.
13. Go to the Files/Backup Selections tab of the policy
14. Select New to add the following path to the backup: /usr/openv/netbackup/db/images
15. Go to the Clients tab of the policy
16. Add the master server to the client list and select the correct hardware/OS type

Save the new policy and exit the GUI. The catarc policy is now available for catalog archiving.