How to specify different names for different child jobs of a policy?

Not that I am aware off - this is pretty much a built-in working method of Netbackup.

+1 for Nicolai..

chaning the name for child jobs is never possible..

you are looking for this option because jobs are not avalaible in activity moniter.. and it could be of 2 reason.

1) deleted the activity montier jobs manually

2) job crossed the KEEP_JOBS_HOURS setting.

if 1 one is the case you can avoid it by not to deleting it or keeping a note before deleting it

if 2 one one is the case.,you can look to chage the time KEEP_JOBS_HOURS  based on the time you need to look for the failure jobs( do remever keeping the jobs in activity montier will increase the load on job database, unlees you have very less number of jobs, avoid keeping it for too many days.)

in case of UNIX  put below line in bp.conf 

KEEP_JOBS_HOURS = 72    ( it will keep jobs for 72 hours, chage it based on your need)

for windows ;

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

1. Open the registry by going to Start | Run and entering regedt32 and clicking OK
2. Proceed to the key: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
3. From the drop-down menu, select Edit | Add Value (for Windows 2003, select Edit | New | DWORD Value)
4. In the Value Name field, enter "KEEP_JOBS_SUCCESSFUL_HOURS." Change the Data Type to REG_DWORD and clickOK.
5. The DWORD Editor window will pop-up. Change the Radix to Decimal and enter the number of hours in the data field.
 

Example: To keep successful jobs for 10 days, enter a decimal value of 240 (10 days multiplied by 24 hours) and click OK.

6. Repeat steps 3 through 5 for the other value "KEEP_JOBS_HOURS."

if Keep jobs hours also does not enough to then you need to go with failure alert notification or Opscenter to get the details.

If you use OpsCenter you'll have a record of ALL jobs that have run for years and years (if you wish).

Hello,

if I concentrate on what you want, you have two choices:

- you can restart individual child jobs which have failed, directly from Activity Monitor (restart Job action)

- open an ad-hoc backup window for the appropriate schedule. If frequency did not pass yet for all streams, scheduled run will process only failed streams

Rgds

Michal

Hi All,

Thanks for your quick responses.

I have KEEP_JOBS_HOURS set to one week. I will not increase that as a recommendation for load increase.

Suppose I fetch a report on daily basis or weekly basis.

I fetch this from the reports section "Status of Backups" in Nebackup Admin console.

I saw that a policy has some child jobs as status 0 and some as status e.g. 96 or 196.

Now since all the child jobs have same name including master job as policy name I am not able to decide which child job failed (though I had specified streams in the policy backup selection and I know how many child jobs will be created). Now if the failed job is present in the activity monitor I will double click it and can check that ok this child job has failed and i will re run it either directly from activity monitor or by creating a partial policy and including only those failed paths.

But if the job is not present in activity monitor then what? How will I be able to identify which stream\child job failed?

So this is the trap that I always get in. And this is becoming critical for me.

So I just want to know how to change that built-in working in netbackup? Where to configure what so that child jobs come with different names atleast one option must be there? 

You can't change it, if you want granularity, you need to configure multiple policies. Or use OpsCenter to review the jobs.

So two things I feel bad for and feel it as limitations of netbackup that should not be there in any backup software -

1. There should be some ways to get\recover the details of activity monitor jobs with the detailed status if these got deleted.

2. As per requirement one should have flexibility to have different names of child jobs because the one who is facing the requirement knows it well and wishes if it would be there for him to configure.  :) 

Thanks to All.

NetBackup does not do that.

The only option I can see - because I've been in the same boat - is to script your own daily backup report which parses the 'selection list' fields of bpdbjobs -all_columns to establish exactly which 'streams/objects/disks/volumes/paths' failed, and which can then also take re-runs in to consideration.

Unfortunately, I'm not aware of any decent canned reports in OpsCenter which can do this for you.