VSR 21 backup failure every 4-5 Days
Hi, Several weeks ago, we installed VSR 21 SP2 on a new Win 10 Pro 20H2 PC The PC has one 256 GB SSD NVMe. Last week we upgraded VSR to VSR 21 SP3 which supports Win 10 20H2. We run a VSR job daily on this machine with new recovery points created twice a month. Since the original install weeks ago backups fail approx. every 4-5 days withe following errors: "Error EC8F1780: Cannot successfully reconcile changes since last session. Error EC8F1771: Cannot enumerate the current drives on this system. Error E0050001: (UMI:V-281-3215-6016)" We were hoping the upgrade to VSR 21 SP3 would resolve the issue, but it made no difference. The error continues daily until the machine is rebooted and then backups run successfully again for 4-5 days. We have uninstalled/reinstalled VSR a couple of times with no change in the error pattern. For many months, we have VSR 21 installed on several other Win 10 Pro computers and we have not experienced this error on any of them. Any help is appreciated. CQ
Managing the Offsite Backup
I think this issue applies to the offsite backup copy for SSRS versions 2013 and later. I've been using SSRS since it was a Norton product and have continued using it all the way to VRS 21. I have a NAS share as my off-site location and it works great, but the copies just grow endlessly. I'd like to be able to prune out old offsite copies, but there is no management UI within the app. Sure, I can manage the local backup locations and set expriations on the recovery points, and perform file actions like consolidating and what not. But there is no similar UI to manage the off-site copies! So my offsite destination has grown to 9TB and I'd really like to keep it under control! Yes I can just delete the copies loaded up to the offsite location, but I was wondering if/why/when/how VRS could or would offer options within it to manage the offsite locations. Sure the app will strat to delete when the off-site location gets full, but lets be honest, we don't ever let our NAS get full! That's like letting our temp locatiosn fill with log files and crash the database! LOL! Or maybe, I'm just missing it and the UI has these capabilities that I've overlooked for 10 years or more... So I post the question here. Ideas? Comments? Tips? I welcome them. Thanks...
A guide to booting HP Elitepad to recovery environment using USB flash drive
Hi, Back in October 2013, a support case that I opened with Symantec in relation to failure of the Elitepad 900 G1 to boot into the Symantec recovery environment from a USB or DVD drive etc, was ultimately closed with no resolution due to a compatibility issue or similar. I recently decided to pick this up again and am pleased to report a successful outcome but not without issues. Here's what I did: > Note: I have SP2 installed on my SSR client (Ver. 11.0.2.49853)but this is immaterial to process described below. > Grabbed a copy of the latest 32bit recovery ISO (SSR11.0.2.49853_AllWin_English_SrdOnly.iso)from here:https://www4.symantec.com/Vrt/offer?a_id=88724 > Obtained and formatted thumb drive as FAT32 (I did not have to bother with the diskpart procedure that is referenced as required from several sources) > Used WinZip to extract the contents of the ISO to the USB flash drive. Note: DO NOT use the Customer Recovery Disk wizard in the SSR 2013 client. > That's it, plugged it in to one of 2 x USB sockets available on the Elitepad productivity jacket. (Note: if you don't have a jacket you might be in trouble having access to only 1 x USB port. > A USB keyboard needs to be connected to the 2nd USB port as there is no touch panel functionality in the recovery environment. Note that If you wish to use a USB Ext Drive to store the recovery points, the USB Boot Flash drive can be safely removed once the environment is entered, allowing you to connect your USB Ext Drive. > In Elitepad Advanced Startup options, selected USB EFI Boot Device option. > Elitepad booted into recovery environment with navigation by keyboard thereafter (Some useful keyboard shortcuts are:- TAB to cycle the focus between objects; enter to select; [space] to check/uncheck a checkbox; right arrow key to expand a file folder to show subfolder) > Ripped a Windows 8.1 image from one Elitepad and then restored using this image to a factory state Windows 8.0 device with no issues whatsoever, just had to re-activate Windows after the restore. So anyway, the critical step in the process described above is to use WinZip or a similar archiving utility to get the ISO contents onto the flash drive because for some bizarre reason, if you use the Symantec Custom Recovery Disk wizard to burn the ISO, this causes all of the files on the flash drive to become hidden (even with "Show Hidden Files / Folders" checked in file explorer?) with the exception of autorun.inf. The problem appears to be that the Elitepad 900 GI apparently can't see these files because it does not recognise a flash drive prepared in this manner, as a valid EFI USB boot device. It seems unlikely that the Elitepad 900 is the only tablet that might be affected by this issue. Hopefully this guide might save somebody some time at some stage. Orson.
Error E4F3000F: Unexpected VSS writer error. Check the application event log
Running VSR 2016 on Windows Server 2012R2. Backups ran for a week then started erroring out with the following: Error E4F3000F: Unexpected VSS writer error. Check the application event log for writer specific error. Failed VSS writers: System Writer I see this problem with SSR 2013 listed in articles with a hotfix, but nowhere do I find anything on VSR 2016.System Recovery 2013 R2 - Service Pack 6 now available!
System Recovery 2013 R2 Service Pack 6 is now available. New features in SP6 include support for Symantec Management Platform (SMP) 8.0, SharePoint 2016 and Amazon S3 Cloud Storage support for Offsite Copy. For more details, please refer to the release notes: http://www.veritas.com/docs/000114407 Service Pack download: http://www.veritas.com/docs/000114408 (note that SP6 is not available via LiveUpdate) Updated compatibility list: http://www.veritas.com/docs/000004208 Full builds are available at https://my.veritas.com/ Trialware available at https://www.veritas.com/trial/en/us/system-recovery-2013-server-edition.html Management Solution trialware available at https://www.veritas.com/content/trial/en/us/system-recovery-management-solution.html Please use this thread for any questions about SP6.SR 2013 - Generating Excessive eMail Alerts & Error Code Info Needed
Hello, I am running System Recovery 2013 Virtual Edition (11.0.2.49853) on a number of Windows Server 2013 Hyper-V Guests. I have the client software configured to generate email alerts for medium and high priority failures. In the past two weeks three of the guest VMs have generated errors which have resulted, in the case of two, the generation of 36 email alerts within 37 seconds, and in the case of the third, the generation of 48 email alerts within 57 seconds. This extreme redundancy of email alerts is something I do not recall experiencing in the past. The two systems that generated 36 emailmessages indicated error E4BD0012 with no further explanatory detail either in the email message or the event log. The system that generated 48 email messages indicated error E7D10017 and EC8F1F61 for the high and medium priority messages respectively. This error indicates a failure to delete an offsite backup file. Regarding the above I have three questions: 1.) By what logic is it necessary to generate 30 to 50 repeititive email messages within a one minute span and, more importantly, is there some way to throttle this behavior? 2.) Does Veritas have any further information on error code E4BD0012? 3.) Regarding the E7D10017 and EC8F1F61 errors, nothing has changed with regard to the offsite backup NAS or the authentication used to access it. The error messages points to a specific file, which is present. Is there any reason this error should suddenly pop up? The system has been backing up in this configuration without issue for nearly two years. Thank You, Dale
Unable to set attributes on the .sv2i file
Hi, We are running Windows Server 2011 and backing up to a buffalo NAS drive and have two jobs configured onedoes our "H" drive, the other does the "C, D, E, G and I" drives. The backup backs up via a network share \\nasname\sbs-bkup, we have recently been getting the below errors This error reports twice once for each backup job. Error EC8F17B6: Cannot update the system index (.sv2i) file. Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'. Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.' Success. Details: Source: Symantec System Recovery These errors appear on the backup job success report in the event log and also on our SMTP logs Info 6C8F1F7E: A scheduled incremental recovery point of drive H:\ was created successfully. Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'. Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.' Success. Details: Source: Symantec System Recovery Info 6C8F1F7E: A scheduled incremental recovery point of drive G:\ was created successfully. Error E7D10016: Unable to set attributes on '//nasshare/sbs-bkup/servername.sv2i'. Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Access is denied.' Success. Details: Source: Symantec System Recovery I found this page "http://www.veritas.com/community/forums/error-ec8f17b6-cannot-update-system-index-sv2i-file” which drew me to this site, unfortunately copying the file onto the server desktop and then back again did not fix the error. Any help would be much appreciated. Thanks in advance Thomas
SR 2013 R2 Windows 10 Restore - Windows Validation Fail
Hi. Have SR 2013 R2 SP4 running on SSD running Windows 10 Pro. Windows 10 was an upgrade on Win 7 Pro. Want to migrate to new Harware. Full Backup taken and stored on 2nd hard drive. Installed NEW SSD and transferred 2nd drive to new PC. Ran SRD from USB.... Looked OK. Selected Restore Anywhere with MBR etc. However... when new PC Boots, it will only log on into Administrator User Account and displays message: "System Protection Tool 3.14 Sysprep was not able to validate your windows installation. Review the log file....\ setupact.log for details." Have Veritas/Symantec found a solution for this Microsoft License Issue?