Cannot find version 2 - Keeps happening
Since ATI 2013, things have been running like clockwork. No issues with backup. Ever since I upgraded to ATI 2016, its very problematic. Can't backup system partition (job fails) and now this nagging issue. I have plenty of disk space on my NAS server (8TB available). I've already fixed this in the past by deleting the job and starting fresh. I'm not going to keep doing this every 1-2 months when it happens again. I put a support ticket in almost a week ago and haven't gotten a response. We resell and support Acronis Enterprise products through a company we partner with (eFolder). Altough we get 1st tier support from eFolder in regards to their enterprise products, the lack of support on their consumer projects puts Acronis in jeopardy of losing the business on the enterprise level to companies such as StorageCraft. I can easily fix this again by deleting the job and the images on the NAS and starting over, but I shouldn't have to. So, it's not a connection issue or a authentication issue or a available storage issue. Anybody have any other ideas?
This type message implies that the target storage location either does not exist or not accessible.
A sleep issue is a distinct possibility. You might check your power configuration on sleep or usb sleep settings which might affect the availability of the storage source. If backup is to a nas type storage location. often these devices have their own sleep/awaken settings which must be adjusted separately.
Or, you could set up a test window scheduler test to awaken the storage location just before backup time.
YOu might also check the Acronis scheduler/advanced settings/
and make sure the awaken settings are checked.
You might also check the storage folder via the Backup Task settings using the task settings "open location" option
and see if the "missing files" are indeed inside the storage folder.
There is no issue with "Power Saving" mode on either laptop or NAS device. Like I said in my prior post, ATI can backup fine for 1 or 2 months and then all of a sudden fail with this error message with absolutely no changes on my end. It's obvious that Acronis support doesn't monitor this forum. I don't plan on paying per incident for a app with bugs. I'd rather buy another product that is more stable and where I can get decent support. BTW, these is no issue accessing the NAS share and yes both version 1 and version 2 files are in the backup share folder.
This attachment shows one place to look inside your active Power Configuration.
the NAS device could also have its own wakeup timer settings.
Good luck.
Grover,
It's not a power configuration issue. I did figure out what is going on. Before I use to run a "Custom" backup. One initial full and ongoing incrementals. The last time I had issues, I created a new job with the defaults (i.e. Incremental with rentention policy). Old version cleanup rule was to "Create a full version after every 5 incremental versions" and the "Old version cleanup rule to "Delete version chains older than 7 days. The version cleanup and automatic cleanup clearly do not work. For some reason, I only had a v2 incremental version and the full v2 was missing. That is why I'm getting the message "Cannot find version 2" (can't find the full backup v2). You would think this product would be smart enough that if a v2 Full was not found, create a new one like many other "Business Grade" backup products do. Somehow, I think ATI 2016 has a bug where the wrong full backup (v2) is being deleted rather than the v1 full and v1 chains. I've attached a couple of screen shots. I've decided to leave the setting for the "Backup Method" to "Custom" and "Create only incremental versions after the initial full version" option. So my question to Acronis support would be, why isn't the cleanup rule working properly and why is the version 2 full (TIB) being deleted because I'm clearly not deleting it.
One last general comment is that I have never seen in my 40 years in the IT field, companies releasing products with no "quality control" what-so-ever. They expect the end-user community to be their eyes and ears. Pretty sad if you ask me.
Hi Gio,
First understand that I am a fellow user--not related to Acronis. This is mostly a volunteer forum. Posting your issues here is not same as posting an official service request. If within 30 days of purchase, initiate a support ticket and use Live Chat or email to seek help from Acronis.
Thank you for the captures and explanation. I can see why this is not sleep/awake issue. Your posting shows several V1-2 issues.
I can see and feel your frustration. The cleanup works but is extremely touchy about the settings and only works if correctly set and then left unchanged without further editing. An edited task almost never performs to expectations.
------------------------------------------------
What you can expect (when correctly working) if the setting is
Full +5 incremental; Delete older than 7 days. (Chain length=6 files (full +5 inc))
Expected deletion of oldest chain will occur when entire chain (oldest inc) is older than 7 days
Elapsed day 1 countdown begins when Inc_B1_S6_V1 has been created more than 24 hours.
Elapsed day 7 countdown ends when the same backup (last incremental of oldest chain) has been created MORE than 7 days. Deletion occurs on first backup that occurs after Inc_B1_S6_V1 is older than 7 days.
----------------------------------------------------
I've decided to leave the setting for the "Backup Method" to "Custom" and "Create only incremental versions after the initial full version" option.
I would strongly urge that you do NOT use this open ended task due to the risk of not being able to restore a future incremental. This link will help explain why.
GH25. Understanding differences between Incremental and Differential backups for data recovery.
When you accumulate a large number of incremental's following a prior full, each and every one of those incremental's must be present and readable without read errors in order to restore you most recent incremental. Also, this setting forces manual deletion which in itself causes issues.
A better solution would be to accumulate fewer incremental's and more frequent full backups. In other words, return to using a custom cleanup. My preference for an automated cleanup option is the the option
"Store no more than (n) recent version chains." This gives you the option of how many chains you wish to keep before automatic deletion occurs.
You could still use your full plus 5 incremental, if that is your preference, and much safer than continuous incremental's.
Automatic deletion should occur after the full backup which causes your store number to be exceeded. My GH12 example offers an example whereby the automatic deletion would occur after full B5 is completed.
------------------------------
If the task is configured with the desired settings and then left alone without further edits, I believe you can get the program to complete your backups as I have suggested above. It would be nice if the task settings were changeable, but making changes rarely works as expected.
Create all new tasks with my suggested settings, and I would expect it to work as configured. I would encourage you to set each task name as unique with no repeat of past task name, and that each task be directed into its own folder or sub-folder inside a more general folder. Name assigned to the tib file will be whatever name you assign to each task.
Later Edit:
As you have had prior installations of TrueImage, if you wre to contact support, there is a high degree of probability that they would suggest that you run the 2015 TrueImage Cleanup tool (Item 4 inside my signature below) and then do a fresh install, creating all new tasks. This is something you might want to consider doing. The cleanup utility has text instructions about editing the registry.
Grover,
That was an excellent reply and it really assisted me in deciding how I was going to implement 2016 for the long haul.
I have been using 2016 for about 4 months now... an upgrade from TIH2014- 2010 (never moved to 2015 due to all the negative comments)
I have been testing and testing, trying out different methods, looking at results and I find your suggestion of using your GH13 the most logical, safe and solid method. So far, I have had good results with 2016, however, I always remembered your comments over the years about not messing with an established task as it is always better and safer to create a new one. That logic has worked well for me. I remembered it and thank you for reminding us.
One question: In the task setup options, there is a Performance setting
The default: Compression: Normal and (I think) Priority: Low
To your knowledge, is there an advantage to changing the priority to "Normal" and if so, why do you think they defaulted it to "Low" ?
Thank you for your time and and for being a fantastic resource on this forum !
Steve
No intent to infringe on Grover here, his advise is rock solid and very reliable and as you say he is an invaliable resource here on the Forum.
In my experience changing the Priority level in the application only provides a minimal gain not really worth doing unless you run backups during offline hours such as nightime to backup large data amounts.
The default "Low" priority is set that way to minimize the impact of the application on system resources and CPU usage so that the user does not experience degraded performance of the PC while a TI backup task is running during a normal computing session.
Hi Gio,
First understand that I am a fellow user--not related to Acronis. This is mostly a volunteer forum. Posting your issues here is not same as posting an official service request. If within 30 days of purchase, initiate a support ticket and use Live Chat or email to seek help from Acronis.
Thank you for the captures and explanation. I can see why this is not sleep/awake issue. Your posting shows several V1-2 issues.
I can see and feel your frustration. The cleanup works but is extremely touchy about the settings and only works if correctly set and then left unchanged without further editing. An edited task almost never performs to expectations.
------------------------------------------------
What you can expect (when correctly working) if the setting is
Full +5 incremental; Delete older than 7 days. (Chain length=6 files (full +5 inc))
Expected deletion of oldest chain will occur when entire chain (oldest inc) is older than 7 days
Elapsed day 1 countdown begins when Inc_B1_S6_V1 has been created more than 24 hours.
Elapsed day 7 countdown ends when the same backup (last incremental of oldest chain) has been created MORE than 7 days. Deletion occurs on first backup that occurs after Inc_B1_S6_V1 is older than 7 days.----------------------------------------------------
I've decided to leave the setting for the "Backup Method" to "Custom" and "Create only incremental versions after the initial full version" option.I would strongly urge that you do NOT use this open ended task due to the risk of not being able to restore a future incremental. This link will help explain why.
GH25. Understanding differences between Incremental and Differential backups for data recovery.
When you accumulate a large number of incremental's following a prior full, each and every one of those incremental's must be present and readable without read errors in order to restore you most recent incremental. Also, this setting forces manual deletion which in itself causes issues.
A better solution would be to accumulate fewer incremental's and more frequent full backups. In other words, return to using a custom cleanup. My preference for an automated cleanup option is the the option
"Store no more than (n) recent version chains." This gives you the option of how many chains you wish to keep before automatic deletion occurs.
You could still use your full plus 5 incremental, if that is your preference, and much safer than continuous incremental's.
Automatic deletion should occur after the full backup which causes your store number to be exceeded. My GH12 example offers an example whereby the automatic deletion would occur after full B5 is completed.
------------------------------
If the task is configured with the desired settings and then left alone without further edits, I believe you can get the program to complete your backups as I have suggested above. It would be nice if the task settings were changeable, but making changes rarely works as expected.
Create all new tasks with my suggested settings, and I would expect it to work as configured. I would encourage you to set each task name as unique with no repeat of past task name, and that each task be directed into its own folder or sub-folder inside a more general folder. Name assigned to the tib file will be whatever name you assign to each task.
Later Edit:
As you have had prior installations of TrueImage, if you wre to contact support, there is a high degree of probability that they would suggest that you run the 2015 TrueImage Cleanup tool (Item 4 inside my signature below) and then do a fresh install, creating all new tasks. This is something you might want to consider doing. The cleanup utility has text instructions about editing the registry.
Grover, very well written! Sorry, didn't mean to vent on you. My frustration evolved out of not getting responses after submitting a ticket to them and not getting any responce. I'm very critical when it comes to support these days. Glad this forum exists and people like you support it.
I have used the cleanup tool in the past (seems like there are leftovers, even when you delete a job/task). This weekend, I will uninstall ATI 2016, run the cleanup tool as you suggested, reinstall ATI 2016 (lastest build) and recreate the backup job/task per one of the methods as you suggested in this post. You are correct in regards to modiying a task. ATI causes all sorts of havoc. I've tried to always delete a task first and create a brand new one. I'm still unsure why the "Full" in v2 disappeared. Will have to start over clean and see what happens.
Thanks again for you knowledge and input!
Ciao,
Gio
Enchant and All....
Thank you for the info and advice.
These forums and the dedicated responders are so helpful and apprciated.
Helps us keep things straight and away from disaster.
Steve
Thank you all for the comments.
The problems users have posted has led me to adapt these procedures which have worked for me and which I recommend others follow as well.
TrueImage works best when set fresh (with the correct settings of course) and left alone.
1. For each new version (but not each build) , I use the TI cleanup utility which uninstalls and cleans up most residue and install into a fresh new installation.
2. I create all new tasks for each new version, and do not later modify. If changes needed, I stop using the old task and create a new task.
Each task name has to be different so no duplication or confusion for the program.
Each task is pointed to its own individual sub-folder so there is no mixing of tasks into the same folder.
3. Each of my tasks is set up for automatic cleanup so manual deletion of old backups is not normally needed;
The cleanup option preferred most is the "store no more than (n) recent version chains which allows for whatever number of chains to be retained.
4. If a backup is restored, I create all new tasks after the restore, as tib backup files exist which are unknown to the restored program.
5. An assortment of storage locations used including internal, external and flash drives. No cloud backups. Occasional CD restores made to test disks for assurance purposes. Occasional backups made via the Recovery CD.
Grover,
Hope you and everyone on the this forum had a great holiday (it's not over yet :)). Last week, I changed my backup scheme to one of your recommended "GH12" scheme. It's been running for almost a week now and seems like it created a full on 12/26 (missed 12/25, at in-laws) called "Entire PC (GIO-NB)_full_b2_s1_v1.tib" and one incremental last night called "Entire PC (GIO-NB)_inc_b2_s2_v1.tib". I've attached a couple of screenshots. So, since GH12 creates a full every 6 incrementals, and keeps only the last 4 chains, can I assume the file structire will be as follows:
CHAIN 2:
Entire PC (GIO-NB)_full_b2_s1_v1.tib
Entire PC (GIO-NB)_inc_b2_s2_v1.tib
Entire PC (GIO-NB)_inc_b2_s3_v1.tib
Entire PC (GIO-NB)_inc_b2_s4_v1.tib
Entire PC (GIO-NB)_inc_b2_s5_v1.tib
Entire PC (GIO-NB)_inc_b2_s6_v1.tib
Entire PC (GIO-NB)_inc_b2_s7_v1.tib
CHAIN 3:
Entire PC (GIO-NB)_full_b3_s1_v1.tib
Entire PC (GIO-NB)_inc_b3_s2_v1.tib
Entire PC (GIO-NB)_inc_b3_s3_v1.tib
Entire PC (GIO-NB)_inc_b3_s4_v1.tib
Entire PC (GIO-NB)_inc_b3_s5_v1.tib
Entire PC (GIO-NB)_inc_b3_s6_v1.tib
Entire PC (GIO-NB)_inc_b3_s7_v1.tib
I'm assuming that the number followinging "b" is the chain number. So before I made the backup scheme change, I was doing continual incrementals, so I would interpret the first chain as looking something like this:
Entire PC (GIO-NB)_full_b1_s1_v1.tib, dated 11/11/15
Entire PC (GIO-NB)_inc_b1_s37_v1.tib, dated 12/17/15
Entire PC (GIO-NB)_inc_b1_s38_v1.tib, dated 12/20/15
Entire PC (GIO-NB)_inc_b1_s39_v1.tib, dated 12/21/15
Entire PC (GIO-NB)_inc_b1_s40_v1.tib, dated 12/22/15
Entire PC (GIO-NB)_inc_b1_s41_v1.tib, dated 12/23/15
Entire PC (GIO-NB)_inc_b1_s42_v1.tib, dated 12/24/15
This would be the first FULL of chain 1 and the last 6 incrementals. So to keep all the chains intact, I can safely delete all incrementals prior to 12/17, but not the full on 11/11/15.
Let me know if that sounds logical.
Thanks,
Gio
Responding to your preceding post #11.
In our discussion below, we are talking about one single backup task and all the backups created by that single task. Backups being created either via schedule, or manually via the "Back up now" option.
1. You have indicated your settings is keep 4 chains (store no more than 4 recent version chains) and each chain will comprise 7 files of 1 full plus 6 incrementals.
2. Once you reach your designated keep quota of 4 chains (28 tib backups), you will ALWAYS have no less than the most recent 22 backups and NEVER more than the most recent 29 backups. You need to plan storage needs on maintaining 4 full plus 24 incrementals plus additional temporary storage space for 1 more full which occurs seconds prior to the deletion of the oldest 7 tib files (oldest chain deleted).
Think of it as your backup quota is an escalator with 29 steps- (4 chains) -each step is a backup. When the escalator gets full and the 29th step gets occupied with a new full backup, there is no more room on the escalator(backup keep quota) so the oldest chain (of 7 oldest backups) will be deleted. The cause of the deletion is your "keep quota" was exceeded (more than 4 chains--28 files total). New backups (vacant escalator steps) will cause the escalator to routinely fill up with 6 new incrementals and then a brand new full backup, which will initiate the next deletion of 7 oldest backups (always oldest chain).
General:
3.Once you reach your designated quota of 4Your target folder of tib backups will neve
4 Chain length is the single full plus any incrementals before the next full. None can be missing or deleted. In your setting, chain length is 7 files (1 full plus 6 consecutive incrementals).
5. Yes. In your chain 2 and chain 3 example, All 7 files of B1 is chain 1. All 7 files of B2 is chain 2. All 7 files of B3 will be chain 3. All 7 files of B4 will be chain 4. Four chains comprise your "keep quota". The B# and chain # will increment with each new FULL backup.
Chain 1= Entire PC (GIO-NB)_full_b2_s1_v1.tib correct
Entire PC (GIO-NB)_inc_b2_s2_v1.tib
Entire PC (GIO-NB)_inc_b2_s3_v1.tib
Entire PC (GIO-NB)_inc_b2_s4_v1.tib
Entire PC (GIO-NB)_inc_b2_s5_v1.tib
Entire PC (GIO-NB)_inc_b2_s6_v1.tib
Entire PC (GIO-NB)_inc_b2_s7_v1.tib
Chain 2= Entire PC (GIO-NB)_full_b3_s1_v1.tib correct
Entire PC (GIO-NB)_inc_b3_s2_v1.tib
Entire PC (GIO-NB)_inc_b3_s3_v1.tib
Entire PC (GIO-NB)_inc_b3_s4_v1.tib
Entire PC (GIO-NB)_inc_b3_s5_v1.tib
Entire PC (GIO-NB)_inc_b3_s6_v1.tib
Entire PC (GIO-NB)_inc_b3_s7_v1.tib
6. The task name Entire PC (GIO-NB) will be assigned by the program to the tib file, plus then adding the suffix code of _backup type_B#_[chain #]_S#[chain slice or backup #]_V1 [always V1 unless the tib file is intentionally split is smaller sizes.].
7. You indicate you made some changes. I hope that means that you created a new task. However, if that means that you made changes to an task already in use, then that is doomed for failure. For the changes to work, the task must be new and unchanged before the first backup is created.
8. Two task names cannot be identical or task name used prior, without confusing the progrom as well as the user. Each task name (Entire PC (GIO-NB) needs to have its own individual unique name to avoid mixing and confusion. The name difference can be just adding an additional name or digits to make each task name different. Each task name should also have its own storage folder or sub-folder so there is no mixing of tib files from different tasks into the same storage folder.
9. There are some problems with assumptions as shown next.
Your example (as below) of chain with missing S2-S36 is not a valid backup and would not validate or restore due to the missing incrementals.
Entire PC (GIO-NB)_full_b1_s1_v1.tib, dated 11/11/15
missing S2--S36
Entire PC (GIO-NB)_inc_b1_s37_v1.tib, dated 12/17/15
Entire PC (GIO-NB)_inc_b1_s38_v1.tib, dated 12/20/15
Entire PC (GIO-NB)_inc_b1_s39_v1.tib, dated 12/21/15
Entire PC (GIO-NB)_inc_b1_s40_v1.tib, dated 12/22/15
Entire PC (GIO-NB)_inc_b1_s41_v1.tib, dated 12/23/15
Entire PC (GIO-NB)_inc_b1_s42_v1.tib, dated 12/24/15
Refer to my escalator example with 29 steps. After 4 chains are completed, oldest chain drops off to make room for the newest approaching chain.
Problem: the November 11 backup pseudo example is missing Slice S2-S36. For any of S37-S42 to be restorable, it requires that S2-S36 be present in the same folder. For a chain to be valid or restorable, ALL incremental of that particular chain (all the same B#) must be present. Each incremental backup has its own special data and that data is not included in any other incremental. If an incremental backup is deleted or corrupt, the chain becomes broken and any newer incrementals are worthless and non-restorable.
10. The automatic cleanup (store no more than 4 recent version chains) will initiate automatic deletion of the oldest chain whenever 28 backups present are exceeded so user deletion of any backup is not needed, and if deletion done by user, backup task will fail.
Additional reference:
GH25. Understanding differences between Incremental and Differential backups for data recovery.
Just to say have same problem. An my NAS is availble.
I often got the error, while working, so I check imedialtey local LAN, all good.
I never had such with Norton, Symantec Ghost.
For the price I expect smooth operation and self healing. If not fund, start new verison.