12-13-2022 09:29 AM
Following the upgrade between Windows 10 and Windows 11 (and we also recently noticed after some Windows 11 updates) Veritas System Recovery (versions 18,20, 21, we don't know about Symantec System Recovery) is no longer able to take snapshots, neither on USB disks, nor via network on NAS or other (we don't know if the simple backup of files and folders stops). The error UMI:V-281-3215-6071 is highlighted which is in turn linked to the EC8F17B7 error (checking the LOGs). We only temporarily solved it by completely reinstalling the product complete with the removal of the configuration (if this is left as it is the problem is not solved). Do you have any other faster solution? The problem is spreading like wildfire and we don't have the strength to handle all these cases.
12-13-2022 10:59 AM
I would recommend you upgrade to VSR v23 which has just recently been released. Also do check the appropriate SCL (Software Compatibility Lists) for whichever version you have installed, as this shows which versions of Windows are supported.
The various different SCLs can be found here:
https://www.veritas.com/support/en_US/article.100046309 - List of User's Guides and Software Compatibility Lists for System Recovery
Note that Windows 11 (21H2) isn't supported until you get onto VSR 22, For Windows 11 (22H2) you will need to be running VSR 23.
02-20-2023 07:32 AM - edited 02-23-2023 01:31 AM
Hi, we are starting to buy the new licenses and at least on one PC we still have the same error with the same modalities with the new product reinstalled with version 23. The PC has a Windows 11 Pro os.
The errors are still the same:
0xEBAB0005 (Veritas System Recovery)
High Priority Error: Error EC8F17B7: Cannot create recovery points for job: PC
By completely reinstalling and reconfiguring the product, the first backup is performed correctly, but the subsequent ones always fail with the same error
02-21-2023 02:47 AM
A clarification: by completely reinstalling and reconfiguring the product, the first backup is performed correctly, but the subsequent ones always fail with the same error