Unable to use any existing backup job after doing a system restore
The last two times after I needed to restore my system from a backup, I was unable to continue using any of my stored backup jobs. I got messages that the partitions do not exist or were changed. I was forced to create a new full system backup. Could someone please explain why this is happening. It never did in the past. I am running the latest version of Windows 10 64 bit and my Laptop is UEFI.
Does this mean that once I do a system restore, all my current backup jobs are obsolete? Does this mean that I can no longer do another restore from any of these backups?
Thank you.
Does this mean that once I do a system restore, all my current backup jobs are obsolete? Does this mean that I can no longer do another restore from any of these backups?
Thank you.
Comments
It seems that any backup job active in AOMEI becomes obsolete once I restore my system from an AOMEI backup on an external hard drive. I am forced to create a new system backup job.
When attempting a backup from an existing job, It says that all partitions are either missing or have changed.
I thought the idea of doing these backup images was a way to restore a computer in case of a drive failure or system crash. Why would you want to restore your computer to a state from a year ago? Again, I'm probably missing something and everyone has their own idea on what they might need. Just curious as to the way others think about how to use and how long they want to keep a backup. Again, if you may need a document, make a file and folder backup of your docs or pics. Why keep a system backup that long????
I have created five different backup jobs to back up the system to different drives at different times.
After a system recovery from version 4.1 these backup jobs do not work anymore and I have to recreate all five.
After a system recovery with version 4.0.6 the backup jobs still work.
Volumes are checked...
Volume 0 was not found or has not been changed.
Volume 1 was not found or has not been changed.
The specified volume 2(C:) could not be found or was changed.
Information Code:4123
None of the partitions to back up have been found.
So my apologies go out to you Reisender1967. I understand your problem.
In my case, and to explain to anyone who still doesn't see why this is such a big problem, I usually do a full system backup. After that point, I will do incremental backups before I do any important changes to my system with comments attached to each incremental backup what is about to change. A normal comment for one of the many incremental backups could be "Before installing software X" for example.
Since I do quite a lot of changes to my system and always want to be able to easily roll them back should I have to for whatever reason, this functionality is imperative to me.
I then keep going like this until I decide my system is stable and I'm 100% happy with it. This could be months after I created my first full backup. At this point, I will delete the old backup job(s) and backups and start all over again with a new and fresh full backup.
I've been using this method without any issues for years and I always stayed with an old version of AOMEI Backupper since I have some very bad and scary experiences upgrading to a newer version in the past where AOMEI Backupper once restored a backup image to another disk than the one selected resulting in a complete disaster!
This time around though, I just finished building a brand new PC system and figured it was time to try out the latest version of AOMEI Backupper as well. I was obviously hoping the latest version should prove to be stable without any major flaws and an improvement over the old version I've been using.
So...when can we expect this bug to be fixed?
I see how this thread was created back in July 2018. That is about 8 months ago and still no fix and I'm now using v4.6.2 which as far as I can tell is the latest version.
Some final words to the developers.
You really need to be a bit more on your toes and address issues such as this one without 8 months passing by with no actions on your part if you want to stay competitive in this business.
Even more important when developing software people need to be able to really rely on. After all, this kind of software is like using the seat belt in your car...it just needs to work with zero issues whenever it's needed.
Allowing 8 months to pass where you even released a number of new versions within this time frame and still the reported issue is the very same and untouched by you, that is not cool.
If the bug in the new versions is not fixed soon, I will probably switch to another software.
So in one way or the other, it seems to be very hard to find a version of AOMEI Backupper at this point that ticks all the boxes with no issues.
Would be awesome with a comment in here from the AOMEI developers what their plans are for this software going forward.
Many thanks, missed that option which sorted the issue.
Brilliant!
...and sorry for the late response. Never received a notification I received a reply. Probably because I didn't bookmark this topic...