Allow manual start of Backup Job outside Backup Window

[haslund]

Hello,

While it is fantastic we have the option to terminate a backup job if it goes outside of the allowed backup window, there are 2 items I would like to see different:

#1
If you start a job manually outside the Backup Window it will be terminated with reason: Terminated by user
Could we adjust this to something less confusing? Like terminated due to violation of backup window or similar?

#2
In the window where we set the Backup Window, could we please have a checkbox that, if checked, will allow a backup job to be started manually outside a backup window?

Thank you for your kind consideration.

[foggy]

Rasmus, thanks for the feedback. Though, currently you can start the job manually even at the moment that is outside of the backup window. The job will not be terminated, the setting applies to the automatic scheduling only.

[dellock6]

This was one of my painpoint many months ago and I stressed for this a lot, both in terms of a better message and the option to override the backup window for manual runs. But on v8 these features have been implemented, at least I've tested the manual override, so I'm not sure which version are you talking about Rasmus.

[Vitaliy S.]

And based on this post, this error message was supposed to be fixed in v8.

[Poweruser]

If i define a backup window in the night and try to run the job manually, the software is so intelligent to ask me if i want to ignore the backup window.
i select yes, to ignore, the job starts and then the job ends with an error message that the time window is not obeyed..

very useless? ;-)

[PTide]

Hi,

Does the job make it to the end and create a backup? If not then that is an unexpected behaviour. Please open a support ticket so the issue can be investigated and post you case ID.

Thank you

[Poweruser]

It was stopped by the message: "Error: Job was stopped due to backup window setting"
Anyway iam actually not able to reproduce it.
Strange.

[foggy]

Feel free to open a case if you see this behavior again.

[Poweruser]

First i have to reproduce it. Otherwise it is to hard to diagnostic, why it happend once/seldom.

[Gostev]

No need to reproduce, debug logs will tell us exactly what happened at that time.

[Poweruser]

can i check them out myself or do i have to enable debug first?

[Vitaliy S.]

You can export and review the support logs yourself. Here is a UG page describing how to do it: Exporting Logs

[Poweruser]

I cant find a string which says sth. about the time window or an error inside the log. maybe i dont know what the string i have to search for is named, but i scrolled through...

[Vitaliy S.]

Please contact our technical team for assistance with logs review.