SSR 2011 Symantec System Recovery Disk ISO download
I have SSR 2011 installed and would like to create a System Recovery disk, but i don't have the ISO. I know there's a download for that and I've seen a location for a 2013 version, but I assume I need a 2011 version. Where can I download one? Thanks, Rob
BIOS is not ACPI compatible
Hello all, I've got a problem with the backup exec system recovery disc 2010. When I try to boot with the CD (on USB CD Drive) or USB Key, I have this message : Status: 0xc0000225 Info : Windows failed to load beacause the firmware (BIOS) is not ACPI compatible. A kb on symantec website tells to change the option in the BIOS but I don't have any option about ACPI. http://www.symantec.com/business/support/index?page=content&id=TECH57513 I found that the CD BESR is a Windows PE 2.5 (Vista). But the hardware which I try to restore isn't compatible with vista. Is there any solution for this problem like a Windows PE XP ? 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.
I need to image a BIOS computer to UEFI
I can't seem to find a guide or any help. How can I image a bios computer and then restore it to a uefi computer. I tried for a week with absolutely no success. System Recovery can put the image on the computer but it will never boot and if I boot from the Windows 7 CD it will not see the operating system so I can not do any repairs. I saw on symantec site for Ghost that " This issue occurs when you deploy an image of Windows 12 BIOS type client computer on a UEFI enabled client computer. You must add the following command in the Command-line options field of the Command -line tab of the Advanced option of the Deploy Image task: -cesp" This does not apply to System Recovery as far as I can tell. I do not see a place to put in any commands. Since Ghost is being discontinued what can I do?
Hot Swap - Lost disk format?
In my desktop PC I have an hot swap adapter. This allow me to have two or more hard drives with the same drive letter say "E:" Most of the time I use the hot swap for different groups of files (Movies on one drive, Books on a different) and the drive letter is "E:" which is the default letter that is assigned by the PC since it is the need letter not use by my internal hard drives. I back up my OS and Data with SSR to my 3 Tb internal hard drive that is assigned the letter "V:". Over the last few days, my V drive has been showing signs of getting "sick". So I purchased a second 3Tb drive. I removed the V drive from inside the computer. I placed my new 3Tb drive in the hot swap adapter and change the label to "Second BackUP- V2" and assigned it the drive letter "V:". It was my intention to rotate the two V drive as one does external USB drives. Since drives in the hot swap adapter are not on the USB port, the USB option is grayed out when I creat a new backup job. The SSR backup appeared to be running OK until at the very end, I receive an error. When I looked at the new V2 drive with Windows Disk Manager it was (1) unlable and (2) looked as if it was un-formated. I then put the original V drive in the hot swap adapter to make a backup before I attempted to find out what was wrong. SSR could not find the original V drive. When I looked at the original V drive it also appears to have "lost its format". Before, I attempt to take any other action, I am asking for your help. It appears that SSR does not like two disk with the same name. I did notice that SSR "identify" each backup location. Could this be the problem? Any quick solution to restore my backup copies without using a file recover software?Restore physical Windows machine in VMware using System recovery 2013
Hi, I'm new to Backup & Restore portfolio and trying to get some hands on System Recovery. I've installed a trial version of Symantec System Recovery 2013 R2 on my Windows 8.1 laptop and created a entire backup of laptop on USB hard drive in a folder named Symantec Backup. Now using this back up I want to create a Virutal machine in Vmware. Can someone guide me on this.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?
Symantec System Recovery 2013 r2 sp4 & Server 2008 r2 BSOD
I am backing up a Server 2008 R2 with Symantec System Recovery 2013 r2 sp4. The image backups fine. When we do a restore we get one of the following errors BSOD stop 7b, No operating system found, etc I have found this article on Microsoft and Veritas which talks about the C:\Boot files being located inside the image file. https://www.veritas.com/support/en_US/article.TECH125582 Within this article it talks about how it is backed up with the image of course, but when it is restored it is written twice: once by ASR Writer and then again by the image file with the end result of the GUID not matching. Here is Microsoft's explanation: https://support.microsoft.com/en-us/kb/2261423 So then if the C:\Boot is located in the image file to exclude it when you do a restore of the image. Unfortunately I have no luck in trying to find out how to exclude this on a restore or even during a disk-based backup. Has anyone been able to resolve this issue? I have and currently working with Veritas but do not have a resolution. Please let me know. Thank you.