backup active during a freeze period...why?

[Arnaud_NEC]

Hi All,

I have a problem with a backup that runs during its freeze period. It should be running between 2am and 8am only. The start of the police is running at 2am, waiting for its turn. This is ok.

But I don't understand why the active start of the police can start at 4pm ?!? Do you have some sort of explanation to explain this behavior? Is that a known bug?

Maybe I miss something in the configuration. I have just configure the active window, I don't konw if there is something else.

Thank you for your help !

[Stumpr2]

The job could remain queued and go active just long enough to error out with a errorcode 196. It should not go active and start writing to tape.

[Arnaud_NEC]

Hi,

thank for your feedback.

Look at the log. The start began at 01:00 and the active start at 15:59.

This is an incremental backup. The policy start window is 01:00 - 08:00.

What could help you to understand this behavior?

02/11/2009 01:00:00 - requesting resource Any
02/11/2009 01:00:00 - requesting resource bt1sssxb.NBU_CLIENT.MAXJOBS.Pnmsfumgbucl1
02/11/2009 01:00:00 - requesting resource bt1sssxb.NBU_POLICY.MAXJOBS.UMIS_master
02/11/2009 01:00:00 - awaiting resource Any. Will retry physical later.
02/11/2009 04:09:23 - awaiting resource Any. Will retry physical later.
02/11/2009 04:09:29 - awaiting resource Any. Will retry physical later.
02/11/2009 04:09:55 - awaiting resource Any. Will retry physical later.
02/11/2009 04:11:03 - awaiting resource Any. Will retry physical later.
02/11/2009 04:17:00 - awaiting resource Any. Will retry physical later.
02/11/2009 04:17:09 - awaiting resource Any. Will retry physical later.
02/11/2009 04:17:40 - awaiting resource Any. Will retry physical later.
02/11/2009 04:37:14 - awaiting resource Any. Will retry physical later.
02/11/2009 04:37:22 - awaiting resource Any. Will retry physical later.
02/11/2009 04:37:44 - awaiting resource Any. Will retry physical later.
02/11/2009 04:53:21 - awaiting resource Any. Will retry physical later.
02/11/2009 04:53:36 - awaiting resource Any. Will retry physical later.
02/11/2009 04:57:29 - awaiting resource Any. Will retry physical later.
02/11/2009 04:57:48 - awaiting resource Any. Will retry physical later.
02/11/2009 04:59:57 - awaiting resource Any. Will retry physical later.
02/11/2009 05:13:25 - awaiting resource Any. Will retry physical later.
02/11/2009 05:13:40 - awaiting resource Any. Will retry physical later.
02/11/2009 05:17:33 - awaiting resource Any. Will retry physical later.
02/11/2009 05:17:42 - awaiting resource Any. Will retry physical later.
02/11/2009 05:33:33 - awaiting resource Any. Will retry physical later.
02/11/2009 05:33:45 - awaiting resource Any. Will retry physical later.
02/11/2009 05:53:29 - awaiting resource Any. Will retry physical later.
02/11/2009 05:53:39 - awaiting resource Any. Will retry physical later.
02/11/2009 06:13:34 - awaiting resource Any. Will retry physical later.
02/11/2009 06:33:31 - awaiting resource Any. Will retry physical later.
02/11/2009 06:33:42 - awaiting resource Any. Will retry physical later.
02/11/2009 06:53:37 - awaiting resource Any. Will retry physical later.
02/11/2009 07:13:33 - awaiting resource Any. Will retry physical later.
02/11/2009 07:13:42 - awaiting resource Any. Will retry physical later.
02/11/2009 07:17:47 - awaiting resource Any. Will retry physical later.
02/11/2009 07:33:38 - awaiting resource Any. Will retry physical later.
02/11/2009 07:37:43 - awaiting resource Any. Will retry physical later.
02/11/2009 07:37:53 - awaiting resource Any. Will retry physical later.
02/11/2009 07:53:34 - awaiting resource Any. Will retry physical later.
02/11/2009 07:58:00 - awaiting resource Any. Will retry physical later.
02/11/2009 08:13:30 - awaiting resource Any. Will retry physical later.
02/11/2009 08:18:09 - awaiting resource Any. Will retry physical later.
02/11/2009 08:33:38 - awaiting resource Any. Will retry physical later.
02/11/2009 08:38:06 - awaiting resource Any. Will retry physical later.
02/11/2009 08:53:33 - awaiting resource Any. Will retry physical later.
02/11/2009 08:54:47 - awaiting resource Any. Will retry physical later.
02/11/2009 08:58:03 - awaiting resource Any. Will retry physical later.
02/11/2009 09:14:55 - awaiting resource Any. Will retry physical later.
02/11/2009 09:18:09 - awaiting resource Any. Will retry physical later.
02/11/2009 09:34:51 - awaiting resource Any. Will retry physical later.
02/11/2009 09:38:06 - awaiting resource Any. Will retry physical later.
02/11/2009 09:38:50 - awaiting resource Any. Will retry physical later.
02/11/2009 09:54:46 - awaiting resource Any. Will retry physical later.
02/11/2009 09:58:46 - awaiting resource Any. Will retry physical later.
02/11/2009 10:14:42 - awaiting resource Any. Will retry physical later.
02/11/2009 10:15:32 - awaiting resource Any. Will retry physical later.
02/11/2009 10:16:28 - awaiting resource Any. Will retry physical later.
02/11/2009 10:18:43 - awaiting resource Any. Will retry physical later.
02/11/2009 10:20:10 - awaiting resource Any. Will retry physical later.
02/11/2009 11:24:09 - awaiting resource Any. Will retry physical later.
02/11/2009 11:25:00 - awaiting resource Any. Will retry physical later.
02/11/2009 11:25:34 - awaiting resource Any. Will retry physical later.
02/11/2009 11:26:12 - awaiting resource Any. Will retry physical later.
02/11/2009 11:26:41 - awaiting resource Any. Will retry physical later.
02/11/2009 11:44:09 - awaiting resource Any. Will retry physical later.
02/11/2009 13:13:12 - awaiting resource Any. Will retry physical later.
02/11/2009 14:53:50 - awaiting resource Any. Will retry physical later.
02/11/2009 15:57:56 - awaiting resource Any. Will retry physical later.
02/11/2009 15:58:24 - awaiting resource Any. Will retry physical later.
02/11/2009 15:58:53 - awaiting resource Any. Will retry physical later.
02/11/2009 15:59:49 - granted resource bt1sssxb.NBU_CLIENT.MAXJOBS.Pnmsfumgbucl1
02/11/2009 15:59:49 - granted resource bt1sssxb.NBU_POLICY.MAXJOBS.UMIS_master
02/11/2009 15:59:49 - granted resource BKP052
02/11/2009 15:59:49 - granted resource LTO2
02/11/2009 15:59:49 - granted resource BT1SSSXB-lto3-robot-tld-0
02/11/2009 15:59:51 - started process bpbrm (pid=6580)
02/11/2009 15:59:51 - connecting
02/11/2009 15:59:52 - connected; connect time: 0:00:00
02/11/2009 15:59:56 - mounting BKP052
02/11/2009 16:00:43 - mounted BKP052; mount time: 0:00:47
02/11/2009 16:00:44 - positioning BKP052 to file 13
02/11/2009 16:01:37 - positioned BKP052; position time: 0:00:53
02/11/2009 16:01:37 - begin writing
02/11/2009 16:37:51 - end writing; write time: 0:36:14
the requested operation was successfully completed (0)

[Nathan_Kippen]

Policies dont' have start windows, schedules have start windows.  Double check each of your schedules within your policy.

[Omar_Villa]

Do you have available drives during this time? because the logs says is waiting for resources and the only or most common resource a job wait for is a tape drive, check this and confirm if you have many other jobs running at the same time and if this is a critical job you can upgrade the job priority to ensure it get all the resources it needs on time.

regards.

[Arnaud_NEC]

My schedule is well configured for the policy.

The priority is 3 whereas all other policies are 1.

There are a lot of backups running at the same time so a lot in queue.

[sdo]

NetBackup master server - what is your O/S and version, and which version of NetBackup?

I do know that v6.5.2 has lots of job scheduling issues - which v6.5.3 supposedly fixes.

The later MPn packs of v5.0, v5.1 and v6.0 are pretty stable.