[Veritas-bu] Storage Lifecycle Policies - SLP - manually running a failed job
2008-11-11 14:43:35
I have SLP active and working great on HP-UX master/media servers at 6.5.2A.
The issue I am seeking assistance with is twofold:
Understanding the SLP recycle process and how to manage it.
If I issue this command:
'bpimagelist -L -idonly -stl_incomplete'
It lists jobs not completed yet. (default is last 24 hours) so I really use
'bpimagelist -L -idonly -hoursago 72 -stl_incomplete' to get the last 3 days.
However - when I sort it using ' bpimagelist -L -idonly -hoursago 72
-stl_incomplete | sort -M -kr3 -kr4n -kr5n'
I can see that some of my jobs are awaiting their copy - often for days.
Is there a way to manually run one or more of these jobs?
Does anyone know how NetBackup determines what to run and when?
The only parameters I am familiar with are based on size or time to wait before
first try and retry time.
If my operator inadvertently issues a 'cancel all jobs' from the Admin console,
which ones run next?
Thanks in advance!
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Veritas-bu] Storage Lifecycle Policies - SLP - manually running a failed job,
David McMullin <=
|
Previous by Date: |
Re: [Veritas-bu] Veritas-bu Digest, Vol 31, Issue 24, Stafford, Geoff |
Next by Date: |
Re: [Veritas-bu] Encrypting offsite tapes, Eagle, Kent |
Previous by Thread: |
Re: [Veritas-bu] Veritas-bu Digest, Vol 31, Issue 24, Stafford, Geoff |
Next by Thread: |
Re: [Veritas-bu] Storage Lifecycle Policies - SLP - manually running a failed job, Rusty . Major |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|