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.12KViews1like8CommentsSystem 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.11KViews2likes14CommentsNorton Ghost users - Welcome to Symantec System Recovery!
As announced today (15 March 2013), Norton Ghost 15 is being discontinued, and will be replaced with Symantec System Recovery (SSR) 2013 Desktop edition. Click here for details. We'd like to welcome those customer who already have made the transition, or are thinking about it! Please use this thread to discuss any non-technical issues, such as functionality, upgrade information, etc. If you encounter a technical issue and require technical epertise, you are in good hands. This board is monitored by several SSR specialists, ready to assist. Simply start your own thread with your question. On the surface, Ghost 15 and SSR 2013 are very similar in the look and feel. The console hasn't changed much, so using the product itself should not be much of a learning curve. However, the engine itself has gone through several improvements. Here are a few of the changes in SSR 2013 from Ghost 15: Support for Windows Server 2012 and Windows 8 UEFI Support:Symantec System Recoverynow enables boot from UEFI (Unified Extensible Firmware Interface) in addition to BIOS. 64 bit Support: 32-bit and 64-bit recovery disks are now included. USB Recovery Disk: Create a custom Symantec SystemRecovery Disk on a USB device.Add 32- or 64-bit drivers. Advanced Monitoring and Reporting:Symantec SystemRecoveryMonitor is a new monitoring solution that's extremely simple to use andis FREE of charge to all Symantec System Recovery 2013 customers. It's a standalone andlightweightsolution for managing up to 100 nodes.It’s simplicity and no extra dependency eliminates the learning curve for users. Intuitive GUI along with essential action controls provide crisp status along with ability to take desired actions seamlessly through the same view. Improved support for virtual environments: Greater support for ESX, VMWare, HyperV, and Citrix. Smart Reconciliation:Now Backups and reconciliation are efficiently done by smartly tracking changed blocks.The reconcile time is drastically reduced to seconds by eliminating the need to do a complete reconcile in cases of crashes or abrupt shutdowns. In addition,incrementalbackups are now up to 750% faster. (Incremental Backup without reconcile at least 35%,Full Backup 15% faster,Incremental Backup with reconcile – At least 750% faster thanNorton Ghost 15) For more information on SSR 2013, visit http://www.symantecsystemrecovery.com. Again, welcome Norton Ghost users! Please let us help make the transition to SSR 2013 as seamless as possible.9.2KViews4likes97CommentsSreEula.exe - System Error when booting 2013 R2 SRD
Hi all. I have had a support ticket open on this now for almost two weeks, with no luck. I have 2 issues. Dell Poweredge T420. Intel Xeon E5-2450 2.1. 16GB RAM. Windows Server 2012 R2 Std. System Recover 2013 R2 w/ current MS ADK installed. All Windows updates installed, and Live update ran. 1. When trying to create a "Typical" SRD, I am only offered "German" as a language selection. 2. More imporant issue: I cannot boot the Advanced 64-bit SRD after seemingly successfully creating it in English. Booting starts out fine. Blue Windows logo...white spinning in process icon. I get the symantec boxes for loading drivers, checking system requirements, network confguration, but then I get an error box titled: "SreEula.exe - System Error" . The message is: "The program can't start because oledlg.dll is missing from your computer. Try reinstalling the program to fix this problem". I have tried repairing, uninstallling and re-installing the software multiple times, but always get the same error. I haven't gotten anywhere with tech support. Anyone with any ideas?? Thanks Mike5.9KViews6likes60CommentsSSR 2013 - support for Windows 8.1/2012 R2 available now!
Service Pack 2 for Symantec System Recovery (SSR) 2013 will be available soon and, amongst other things, will bring support for Windows 8.1 and Windows Server 2012 R2. I cannot provide an exact date for the release of SP2 at this stage but this thread will be updated with details (release notes etc) when SP2 is available. Please let me know if you have any questions.4KViews4likes61CommentsSymantec System Recovery 2013 R2 is now available!
Symantec System Recovery 2013 R2 is now available! For more details, please refer to the following links: https://www-secure.symantec.com/connect/blogs/new-symantec-system-recovery-2013-r2-here http://www.symantec.com/docs/TECH225253 Feel free to ask any questions about this release on this forum thread.3.4KViews2likes21CommentsError 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.3KViews0likes1CommentSymantec System Recovery 2013 R2 - Service Pack 4 now available!
Symantec System Recovery 2013 R2 SP4 is now available and includes support for Windows 10 and the Symantec Management Platform 7.6. For more details and download links, see below: Trialware: https://www.veritas.com/trial/en/us/system-recovery-2013-server-edition.html Full media download: https://my.veritas.com/ SP4 Patch: https://www.veritas.com/support/en_US/article.000099915 Release Notes: https://www.veritas.com/support/en_US/article.000099941 Software Compatibility List: https://www.veritas.com/support/en_US/article.0000042083KViews0likes3Commentschanging backup settings to allow new hard drives
Our current setup: Windows Small Business Server 2011 (which is actually Server 2008 R2) Symantec System Recovery 2013 Logical drives are C:, D: and E:. We back these up on a weeknightly basis (Monday, Tuesday, Wednesday, Thursday, and Friday). It also backs up the System Reserved drive. It is a recovery point set that run a complete backup each night to an external USB drive. Before the backup runs, we delete out the previous recovery backups from the week before. Ex: on a Tuesday night, we plug in the USB drive labeled "Tuesday". In Windows explorer, we delete out the backup files that are there from last Tuesday's backup. This leaves the hard drive blank, allowing that night's backup to run, which completely copies over the C:, D: and E: drives to the Tuesday USB hard drive (in the case of someone accidently leaving the previous week's backup files on the USB drive, the job creates a differential backup of the logical drives to the USB drive). -We are using arecovery point set job description. Every day, the job shows up as scheduled with the destination drive labeled according to the day of the week: [Monday]\, [Tuesday]\, etc. -Each hard drive has a recovery point set limit of 1. -All the USB hard drives are identical. The problem is that one of the hard drives has failed and we are replacing it with a different, higher capacity USB hard drive. Now the scheduled jobs do not run on that drive. When we run the scheduled backup job manually, it backups successfully to the new USB hard drive. I do not have any error messages right now, unfortunately. What changes do I need to make to my scheduled backup job to allow it to backup to different models of hard drive? We are not using offsite backup features.Solved2.8KViews0likes13CommentsUnable 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 Thomas2.7KViews0likes19Comments