The support forum

After (re)starting Bvckup, all backups start to run

Klaas :

Jun 27, 2019

Against exoectation also the ones that are set to wait for a Go command.

Klaas :

Jun 27, 2019

Using version 80.1, Professional/Legacy.

Alex Pankratov :

Jun 27, 2019

Please elaborate on exact details. There are no known issues around at-launch scheduling. The only jobs that will run after launch are the real-time ones and periodic jobs that missed their run AND have "run asap" enabled.

Klaas :

Jun 27, 2019

I have no further details, it is as simple as I describe it. I could try making a movie.

Alex Pankratov :

Jun 27, 2019

I need to confirm the issue first, reproduce it second. If you can make a screencap, please do.

Klaas :

Jun 27, 2019

Just made a screencap. Sending it via email.

Alex Pankratov :

Jun 30, 2019

This has been resolved. For everyone's reference the cause was having "run on arrival" option [1] enabled for a manual job going onto a _network share_.

Jobs like this will always start their life in "device is missing" state until the share is checked and verified to be accessible. At this point the job will be moved into "idle" state and *this* triggered a run as per the override.

The workaround is to not use this option with jobs that use networks shares, and a proper fix is to observe this option only when a *local* storage device arrives. This will be in the next maintenance release.

[1] https://bvckup2.com/support/forum/topic/1012

New topic

Create
Made by Pipemetrics in Switzerland
Support

Updates
Blog / RSS
Follow Twitter
Reddit
Miscellanea Press kit
Testimonials
Company Imprint

Legal Terms
Privacy