2.4K Posts
0
626
April 23rd, 2022 06:00
Be careful once you have restarted a workflow in NW 19.6.0
You better control your restarted workflows in NW 19.6.0.x.
I was surprised because these backups ended very fast - they just took some seconds. However, the workflow did not backup anything because it thinks that the second attempt was restarted outside the restart window:
So please do not just rely on the 'successful' icon - always check the logs as well.
BTW - I have verified this for versions 19.6.0.0, 19.6.0.2 & 19.6.0.3
No Events found!
bingo.1
2.4K Posts
0
May 7th, 2022 08:00
FYI - I just want to share the positive message that this issue has (silently) been solved with NW 19.6.1.0.
barry_beckers
393 Posts
0
May 8th, 2022 08:00
What is then now being reported? As an error as it did not execute due to falling outside the restart window?
bingo.1
2.4K Posts
0
May 8th, 2022 08:00
There is nothing to be reported except that a restart is not rejected any longer. It just works as expected.
bingo.1
2.4K Posts
0
May 10th, 2022 14:00
I am sorry but I have to take my statement back - the problem has not been solved yet with NW 19.6.1.
Unfortunately, looking at all my test servers which I often reconfigure I cannot remember, which configuration I upgraded to verify that it is working now.
As the problem re-occured today I did some more tests and I could verify that it popped up with NW 19.6.1.0 running on
- Windows Server 2012R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
- SLES 12SP5
The setup for the verification is easy:
- define the local client (at the server) with two save sets, for example
- one which exists
- one which does not exist
- Of course the first run will result in an error
- Now just restart the workflow and this run will end
- sucessfully
- with a runtime of 00:00:00 sec
- and with the 'restart rejected' message as shown in my first message.
Sorry for the confusion.