Error message
In an incremental backup when trying to recover files a mesage "Failed to open item ..." although the item is where it's supposed to be.
How to proceed?
Thanks Steve,
Backup is configured as a FULL and then several INCREMENTALS.
Atempting to recover files from the ATIH 2016. Mounintg looks to work for the full version but not the incrementals (error: cannot assign drive letter...")
When trying to recover files from the ATIH 2016 I get a message "Cannot find version xx" which is the last incremental.
I will run the Log File Viewer app later today and let you know the messages.
Thanks
eneiman
Please see post: https://forum.acronis.com/forum/116874?page=1#comment-374611 and download the TibMounter patch from that post and right-click and Install it from the .MSI file contained in the zip file - this fixes known problems when mounting images.
Hi Steve,
After installing the TibMounter patch, mounting the incrementals works fine in 2 out of 3 backups. There's stil one that refuses to mount both, the Full and the Incrementals.
Going back to the original problem, from the ATIH 2016 GUI I was getting the message "Cannot find version 24" when trying to recover files.
I found that if I keep clicking "Ignore this version" 24 times till the message goes away, the recover files screen in the ATIH 2016 GUI will open fine.
These worked fine on the three backups I'm running.
What could be causing the "Cannot find version xx" error?
Thank you.
Steven, please see post: https://forum.acronis.com/forum/122481 where another user had a similar issue with the 'cannot find version xx' messages.
Once in a while I need to delete a previous set (full+incremental) when disk runs out of space.
What's the right way to do this to avoid doing it from Windows?
Thank you!
The recommended method of deleting unwanted backup versions is to use the auto-cleanup rules to manage your backup versions.
The key point with auto-cleanup is to understand how this works.
Auto-cleanup works with complete version chains, i.e. a full backup plus all associated incremental or differential backups.
Any version chains to be deleted will only be deleted when the next version chain has been successfully created with the first full backup of that new version chain.
If you define auto-cleanup to be actioned after a period of days, then the count of those days does not begin until the next version chain has been successfully started. The same applies if you define the number of backup versions to be retained, old backup versions are not removed until the next version chain has been successfully started.
Thank you Steve, I'm revising the auto-cleanup settings based on your advice.
I have a couple of related questions:
* The backup that refuses to mount, could it be because it's backing-up a folder instead of a hard drive?
* When the backup cannot be started because the PC is off or the backup drive is not availbale or full, the schedule set for following backups gets interrupted. Is there any setting to prevent this?
Steven, difficult to say why you have one backup that refuses to mount, especially if you have installed the TibMounter patch as advised earlier in this thread. Only partition images can be mounted as a drive letter but you should be able to explore a folder backup via Windows Explorer.
There are several options open to you with regards to how you handle scheduled backups that are missed or where the target drive is not available.
One of those options is to Run (missed) backups with a delay of x minutes on the next system start and the other is to run when the target device is next connected.
See the ATIH 2016 User Guide - Advanced Settings
Advanced settings
Clicking Advanced settings allows you to specify the following additional settings for backup and validation:
- To postpone a scheduled operation until the next time the computer is not in use (a screen saver is displayed or computer is locked), select the Run the backup only when the computer is idle check box. If you schedule validation, the check box will change to Run the validation only when the computer is idle.
- If you want to wake up the sleeping/hibernating computer to perform the scheduled operation, select the Wake up the sleeping/hibernating computer check box.
- If the computer is switched off when the scheduled time comes, the operation won't be performed. You can force the missed operation to run at the next system startup. To do so, select the Run at system startup check box.
Additionally, you can set a time delay to start backup after the system startup. For example, to start backup 20 minutes after system startup, type 20 in the appropriate box.
- If you schedule a backup to a USB flash drive or validation of a backup that is located on a USB flash drive, one more check box appears: Run when the current destination device is attached. Selecting the check box will let you perform a missed operation when the USB flash drive is attached if it was disconnected at the scheduled time.
- If you want to regularly back up data located on a removable media (for example USB flash drive) or remote storage (for example network folder or NAS), we recommend that you select the Run when the current source device is attached check box. This is useful because an external storage device may be often unavailable at the scheduled moment of backup. In that case, if the check box is selected, the missed backup operation will start when the device is connected or attached.
* The backup that refuses to mount, could it be because it's backing-up a folder instead of a hard drive?
The mount operation can only work with disk and partitions backups, not with files and folders backups.
Got it!
Thank you
Thank you very much Steve!
I will proceed to change my settings based on you advice.