I know I'm bringing up an old thread here, but it fits my question perfectly, just does not answer it completely.

When Stumpr says "from when it st arted,"  does Netbackup consider the "Active Start Time" or does in include the time a backup is queued.

My concern is that, say we have a frequency of 1 day, with an 8 hour backup window scheduled to start at 6 PM.  The backup kicks off, but is queued for four hours, thus the "Active Start Time" is 8 PM.  Will the next days backup not look to start until 8 PM?  And then what if it queued up for an hour after that, pushing the next day's backup to 9?  

I'm just wondering if this is a possibility.

Of course Bob Strump is FAR MOR EXPERIENT than me.. I'm just thinking about it .. no documentation.

imagine that some backup have the elapsed time 26 hrs.

Will net backup start another job without the end of the first one?

I think that is start counting at the end of the backup.

Thinking again.

if it stats couting at the start of the backup it will respect the backup window

I checked out the pretty good technotes that Symantec has on the algorithms used to calculate frequency based schedules, but A) It looks like they are specific to 6.5.4, and B) They still do not mention if they use the start time, including time spend queued, or "Active Start Time" to figure out when to run the next backup.

Imagine that a backup have to run everyday 18:00 hrs... and something made it stay queued for 3 hrs, so it started as 21:00,  next day it will start at 21:00?

I don't think so,  I think that when U schedolle the backup, it will keep stating at the begining.

Strump was right

But I could not find anything in the documentation that confirmed it.

http://seer.entsupport.symantec.com/docs/331912.htm

To clarify a little:

The "day" frequency interval works in a special way; i.e. a frequency of 1 day does not necessarily equal 24 hours.

The 1 day frequency tells NetBackup to allow the backup to run from the start of the backup window on the following day (and so forth), even if only 20 hours have elapsed since the backup last ran.

On the other hand, if you set the frequency to 23 hours for example, then 23 hours will have to have elapsed before the backup will become due.

I hope this helps.

Only if your backups is successful will reschedule, if fails it will not affect the scheduling.

I've just done a test:
Start time: 11:17:21  (queued)
Active Start: 11:23:14

# bpimagelist -client mvdberg -U
Backed Up         Expires       Files       KB  C  Sched Type   Policy
----------------  ---------- -------- --------  -  ------------ ------------
10/29/2009 11:23  11/05/2009     1676  6468669  N  User Backup  mvdb

bpsched used to assign the backupid as the backup was queued. Now nbjm assigns it the moment resouces become available and the job goes active.

So the backup time in the image would reflect the "Active start" time.

Luc.