Log Entry : The initial full backup version is not accessible at the moment
This is the 3rd time I have posted this annoying error, but Acronis just ignores it.
I am getting this error on all three of my Licenced computers, 2 x XP SP3, 1 x W7 SP1, all running
build 6131.
Every backup is marked with the Yellow triangle indicating a problem with the backup. On investigation there appears to be nothing wrong with the backup that creates the new backup, validates and goes through to completion.
I believe that this log message is entirely spurious and should be removed by Acronis as a matter of urgency.
My conclusion is that the backup code always looks for an "initial full backup" in the version chain, when performing other than full backups.
My problem is that I always perform full backups, so of course there will never be an "Initial full backup version" to access.
Acronis, please stop ignoring this problem that has also been reported by others, and please get it fixed!!!!
Thanks Ross
I'll chime in here... I have the same problem on just one of my drives that I back up. My internal hard drive task does fine, no warnings, and one of my external USB drives does fine, but the other external hard drive, since I installed Acronis 2012 (had been using 2011), gives me the warning in the log:
the initial full backup version is not accessible at the moment.
and then seems to go on to back up just fine.
Very puzzling and a little worrisome...
Thanks - Mary
Is anyone going to answer this? I get this for every incremental backup done since installing this product.
And the little calendar show ONE green check on the day I took the first full backup; after that, ever day has a warning icon.
I'm willing to accept that I may have done something wrong, but my reading of this is that the message is BOGUS, since I can plainly see the full backup. And the incrementals do finish, but I need to know if they're any good or not!
I get these log entries as well and they occur in the first few seconds of the backup process. The backup goes to completion and validates so there is no problem with the backup so in my case the log entry can be ignored.
In my case the log entry occurs when I run my one backup task (full backup then a series of either differential or incremental backups) onto different USB drives on different days.
- The first day I set up the task and run the backup a full back up is done onto USB 1. No errors in the log.
- On day two I use a different USB drive USB 2 when I run the task. No full backup is found on USB 2 so a full back up is done and the log shows the 'initial full backup version is not accessible at the moment' entry.
- Day three using USB 3 - same result.
- Day four I insert USB 1 and a differential (or incremental if that is my routine) backup is done. The first full backup is on this USB drive so no log entry.
- Day five I insert USB 2. There is a full back up there but not the initial one so the backup task does a differential (or incremental) using the full back up on USB 2 drive as reference. the backup is validates but there is a log entry "initial full backup version is not accessible at the moment". That's because the initial full back up verson is not on the USB 2 drive but on USB1 . No matter. The backup was done and it is valid.
That's how it work in my case but there might be other reasons this log entry appears to worry people. I think if the backup validates then it is valid and you can ignore the yellow triangle and the log entry. I agree with Ross.b1 that it would be better if only important error messages appeared in the log.
I'm also having this problem. I just have a simple Incremental scheme run every night. It was fine for months, but after the latest upgrade (I think) to 6154, I am getting the warnings "The initial full backup version is not accessible at the moment" on every nightly backup, even when I run it by hand. I've also uninstalled and re-installed Acronis 2012, and I've run a single full backup to the Acronis Secure Zone, which is also where the incremental backups go, and that full backup completed with no warnings. I'm hoping Acronis actually checks this forum and will provide a solution, since, otherwise, there's not much point in paying for a backup solution that won't run error/warning free.
Hello Kissel,
Welcome to our Forum, we're glad to greet you here. I understand your concern, and will be glad to share the information I've got from the Development team regarding this issue.
Our team is aware of the problem, and got it fixed in the upcoming Update 2. Unfortunately we do not have any ETA regarding its release date available, but it's already being tested, so it shouldn't take long.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you.
Hello Kissel,
Our team is aware of the problem, and got it fixed in the upcoming Update 2. Unfortunately we do not have any ETA regarding its release date available, but it's already being tested, so it shouldn't take long.
Hi Yana,
Please advise if this error message means that the backups are infact being created correctly but the error message is being displayed in error OR if the backups are NOT being created correctly.
If they are NOT being created correctly, how can I force the job to execute a full backup instead of an incremental?
Thanks,
Andreas
Hi
I am on the most recent version of this (Home 2012 update 2 build 7119) and I am getting this exact issue about 3 times per week. I am always backing up to the same drive at the same (scheduled) time.
Please can someone from the technical team explain why we are getting these warnings and if this means that our backups will not be valid?
MKP
Hi
I am on the most recent version of this (Home 2012 update 2 build 7119) and I am getting this exact issue about 3 times per week. I am always backing up to the same drive at the same (scheduled) time.
Please can someone from the technical team explain why we are getting these warnings and if this means that our backups will not be valid?
MKP
Just wanted to say that 7119 is NOT the latest version, 7133 is...
http://forum.acronis.com/forum/33583
Pete
Gosh wouldn't it have been helpful if when I did "check for updates" in the app it had told me that?
I have now updated to the official latest version and I am getting the same issue every evening. It's also clearly failing to run at anything like the scheduled time - scheduled time is 01;00, log time shows "operation started by schedule" at 21:01 - my suspicion is is that it is not actually waking the computer from hibernation/sleep as it is supposed to (this is set in the advanced options). My other suspicion is that what is happening is that this is starting as soon as the computer is manually woken from sleep and is trying to find the network location for the backup before the network card has actually got the locations sorted.
So - any chance of an answer as to whether I should be worried about this problem?