Bug report 2

[dkvello]

Create a backup-job and include a backup-window with "Permitted" & "Denied" times.

Start this backup-job manually within the "Denied" period.

The error is pretty much non-sense. Eksample.

"
18.06.2012 12:55:33 :: Queued for processing at 18.06.2012 12:55:33
18.06.2012 12:55:33 :: Required resources have been assigned
18.06.2012 12:55:47 :: Job has failed. See logs for details.
18.06.2012 12:55:47 :: Processing finished with errors at 18.06.2012 12:55:47
"

Considering this is working as designed (limited by backup-windows) then the job should not fail, but remain "pending"
with an "info-message" like "Job has been deferred until 18.06.2012 18:00:00 due to backup window restricions"

"
18.06.2012 12:55:33 :: Queued for processing at 18.06.2012 12:55:33
18.06.2012 12:55:33 :: Required resources have been assigned
18.06.2012 12:55:47 :: Job has been deferred until 18.06.2012 18:00:00 due to backup window restricions
18.06.2012 12:55:47 :: Processing finished with warnings at 18.06.2012 12:55:47
"

[dellock6]

Well, you manually asked for the job to start "now", so if it's within the denied period to me sounds the fail is correct, is telling you something like "you cannot run it now". Veeam cannot decide by itself to defer the job until the allowed period, maybe is more a feature request of having a flag to override manual execution even within a denied time frame.

Luca.

[Vitaliy S.]

I believe that any backup/replication job that goes beyond the defined backup window should be immediately stopped. Let me try to explain that:

Imagine that you have an Exchange backup job running for the whole night and in the morning when the whole office is ready to work, the backup snapshot starts committing itself to the virtual disk. This will lead to Outlook disconnections and email delivery delays, which I consider to be worse than the failed backup/replication job, don't you thinks so?

[dkvello]

I can agree that it should be immediately stopped (as to deferred), but it should also report why it failed to run manually.
The log files doesn't state that it failed due to time-restrictions.

This problem came up because we needed to start manually an emergency backup, but the job kept failing for no apparent reason.
Someone had activated a time-denied on this job, but it was not apparent anywhere in the logs.

[Vitaliy S.]

Oh, yes, it definitely makes sense to mention backup window restrictions in the logs files. Thanks!