Hi everybody,
for a couple of policies I have checkpoints set to 15 minutes (most of them in conjunction with compression). Some of these polices are not allowed to run at working hours, so they are suspended (mo-fri 7:00 am) and resumed (mo-fri 7:00 pm) with a crontab entry.
Depending on the client involved I sometimes decide to resume a policy manually - usually it works fine but this is not reliable. Sometimes the jobs are not resumeable (error 227 no entity found) and the collected fragments were cleared from the disk.
I suspect, that somewhere the information that the job is not done gets lost - but where and why?
I found some "keywords" which might be connected to this matter, but I am having problems gathering further information, so what about these:
- Pem Job State: PJS_SUSPEND_END (8)
- Task Incomplete, current status PEM_EC_INCOMPLETE (-2)
- Task completion callbacks
- nbpemreq -persisted screen
Both, Server and Client are running on NBU 6.5.4.
Thanks in advance,
Steph
for a couple of policies I have checkpoints set to 15 minutes (most of them in conjunction with compression). Some of these polices are not allowed to run at working hours, so they are suspended (mo-fri 7:00 am) and resumed (mo-fri 7:00 pm) with a crontab entry.
Depending on the client involved I sometimes decide to resume a policy manually - usually it works fine but this is not reliable. Sometimes the jobs are not resumeable (error 227 no entity found) and the collected fragments were cleared from the disk.
I suspect, that somewhere the information that the job is not done gets lost - but where and why?
I found some "keywords" which might be connected to this matter, but I am having problems gathering further information, so what about these:
- Pem Job State: PJS_SUSPEND_END (8)
- Task Incomplete, current status PEM_EC_INCOMPLETE (-2)
- Task completion callbacks
- nbpemreq -persisted screen
Both, Server and Client are running on NBU 6.5.4.
Thanks in advance,
Steph