-
- Posts: 3
- Joined: Mon Dec 13, 2021 9:59 pm
Run task as soon as possible after a scheduled start is missed
Hi,
I am a "newbie" on this forum, so please forgive me if I am not following certain procedures correctly!
I have tried to search this forum for what I wrote in the subject..... I couldn't find anything.
So, let me try and explain my issue.
I have 7 seperate (daily) backups scheduled from 19:00 hours to 19:30 hours with a 5 minute interval
(see 1st attachment).
Now, when I start-up my PC after the scheduled scans, it will try(!) to run the missed scheduled tasks
almost simultaneously which doesn't work and ends in an [ERROR] (see 2nd attachment).
How can I make this work without risking an [ERROR] and therefore not having a daily backup?
Thank you in advance for your energy, patience and time.
I am a "newbie" on this forum, so please forgive me if I am not following certain procedures correctly!
I have tried to search this forum for what I wrote in the subject..... I couldn't find anything.
So, let me try and explain my issue.
I have 7 seperate (daily) backups scheduled from 19:00 hours to 19:30 hours with a 5 minute interval
(see 1st attachment).
Now, when I start-up my PC after the scheduled scans, it will try(!) to run the missed scheduled tasks
almost simultaneously which doesn't work and ends in an [ERROR] (see 2nd attachment).
How can I make this work without risking an [ERROR] and therefore not having a daily backup?
Thank you in advance for your energy, patience and time.
You do not have the required permissions to view the files attached to this post.
Backup4all v9.4.460 running on Windows 10 Pro 64-bits (x64) v21H2
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
-
- Posts: 1946
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Run task as soon as possible after a scheduled start is missed
Hi,
Please send us the last backup log for such a backup job with problems, to support[at]backup4all[dot]com
Please send us the last backup log for such a backup job with problems, to support[at]backup4all[dot]com
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html
-
- Posts: 3
- Joined: Mon Dec 13, 2021 9:59 pm
Re: Run task as soon as possible after a scheduled start is missed
Hi Adrian (Softland),
I am reluctant, because:
(1) which file(s) would you need exactly;
(2) the logs I have seen are full of VERY personal data (like: names, IP-addresses etc.).
Also, I am curious as to why I am not able to use BBCode (it is switched OFF).
I am reluctant, because:
(1) which file(s) would you need exactly;
(2) the logs I have seen are full of VERY personal data (like: names, IP-addresses etc.).
Also, I am curious as to why I am not able to use BBCode (it is switched OFF).
Backup4all v9.4.460 running on Windows 10 Pro 64-bits (x64) v21H2
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
-
- Posts: 3
- Joined: Mon Dec 13, 2021 9:59 pm
Re: Run task as soon as possible after a scheduled start is missed
Okay.... I discovered where the error was coming from.
I analyzed the logfiles from 13 dec. 2021 and at the end of the logs there was the reason why the backup
was aborted: in short, it said "Cannot create folder....".
I am backing-up to my NAS which, of course, has a servername and a local IP-address.
The destination folder contains the IP-address instead of the servername.
There is nothing wrong with that, only my computer could not access the NAS by using the IP-address....
a so-called "credentials problem".
I fixed it in Windows Credentials Manager (defining both servername and IP-address with username
and password) and after that I shut down my computer before 19:00 hours and started it back up
at 19:45 hours. And that worked, Backup4all ran all the tasks right after the computer was up and running.
So Adrian (Softland), thanks for your valuable input and time, much obliged!
(topic is solved and can be closed)
I analyzed the logfiles from 13 dec. 2021 and at the end of the logs there was the reason why the backup
was aborted: in short, it said "Cannot create folder....".
I am backing-up to my NAS which, of course, has a servername and a local IP-address.
The destination folder contains the IP-address instead of the servername.
There is nothing wrong with that, only my computer could not access the NAS by using the IP-address....
a so-called "credentials problem".
I fixed it in Windows Credentials Manager (defining both servername and IP-address with username
and password) and after that I shut down my computer before 19:00 hours and started it back up
at 19:45 hours. And that worked, Backup4all ran all the tasks right after the computer was up and running.
So Adrian (Softland), thanks for your valuable input and time, much obliged!
(topic is solved and can be closed)
Backup4all v9.4.460 running on Windows 10 Pro 64-bits (x64) v21H2
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
Intel i7-7700 [email protected] | Samsung 970 EVO Plus M.2 500GB | NVIDIA GeForce GTX1060 6GB | RAM 16GB
-
- Posts: 1946
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Run task as soon as possible after a scheduled start is missed
Hi,
I'm glad you found and solved the problem.
I'm glad you found and solved the problem.
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html