Ошибки (Bugs)
Здравствуйте,
Windows 10 1909, 18363.592, User mode
1) Удалять цепочки версий, старше....
Исходные настройки: 1.jpg
Результат: 2.jpg
На 12.02.2020 хранятся цепочки с датой создания 19.12.2019-25.12.2019
Вопрос: что нужно сделать в настройках, чтобы Правило очистки работало?
PS: Это же происходило еще в 2016г (запещено вставлять ссылки)
2) При возникновении ошибки (ошибка чтения сектора ХХХ на диске) данная задача останавливается но и Задачи, запуск которых было запланирован после остановленной Задачи, не запускаются до тех пор, пока Пользователь случайно это увидит-зайдет в интерфейс программы-Нажмет "Отмена" или "Пропустить"!
Вопрос: что нужно сделать в настройках, чтобы выполнения Заданий не зависело друг от друга?
Спасибо


- Log in to post comments

Hello Steve,
Thank you for your attempt to explain at least something in this craziness, called Acronis :(
1) >>> should have been deleted after 30 days from this date
Yes, they should have deleted but not deleted!
My question is, what should I do to this to work?
Of course, I can do "Clean up versions" manually, but I would like to have this process in automated mode.
2)>> set in the Options > Advanced > Error handling page.
There are such functions, but they don't work correctly.
Settings screenshot attached, in which the dialogs windows appear and rest tasks are blocked.
A bit offtopic:
I have been an official User of Acronis Tue Image since 2013. Until 2017, I tried to tolerate numerous bugs and program errors, then stopped buying it.
In 2020 I thought that probably everything has already been fixed, and again I bought a license, but the errors are still the same.
Attachment | Size |
---|---|
529619-179369.JPG | 22.79 KB |
- Log in to post comments

John, I expect that you will need to use the Clean up versions tool to reduce the number of version chains for your backup task(s).
Personally, I have never used the cleanup option to delete old chains older than X days as it has always been the more difficult one to understand and manage.
Instead, I have always kept to using 'store no more than X version chains' which has worked just fine for me. I normally set X = 2, so when my 3rd version chain is started with a new Full backup, the oldest chain then gets deleted.
For error handling and bad sectors, I have to say that I would not use the option to ignore bad sectors as that is a recipe for nasty surprises further down the line when the disk fails! I would rather be told about bad sectors and given opportunity to decide what actions to take.
CHKDSK /R will check for bad sectors and try to reassign any that are found, but if a drive is going down that path, then using diagnostic tools provided by the drive maker is the next step to determine just what else may be failing on the drive. Finally, replacing the drive before it fails!
I have just taken a Seagate drive and put it in the rubbish bin after it started giving such issues, and when I ran the Seagate Seatools diagnostics, it constantly failed their Short tests with pages of bad sectors. The tool said it had repaired the sectors but when it was run again, the same list came up again!
Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:
- Western Digital drives: Data Lifeguard Diagnostic for Windows
- Seagate disks: SeaTools for Windows
- HGST disks: HGST Windows Drive Fitness Test (WinDFT)
- Intel SSDs: Intel Solid State Drive Toolbox
- Samsung drives: Samsung Magician
- ADATA drives: ADATA SSD ToolBox
- Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager
- Transcend SSDs: Transcend SSD Scope
- Silicon Power disks: SP ToolBox
- Toshiba disks: Toshiba PC Diagnostic Tool Utility
- Crucial disks: Crucial Storage Executive
- Log in to post comments