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, Rob13KViews1like15CommentsA 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.12KViews1like8CommentsDifferent Backup Job Per Remote PC
I'm using SSR 2013 and have 2 remote PCs that I want to backup at different intervals. PC_A needs to be backed up every Thursday at 12:00 PC_B needs to be backed up daily at 12:00 I create backup jobs for both of these, but these seems to be shared between the 2 PCs. If I select PC_A and only enable the Thursday backup, then that configuration is applied to PC_B as well. How can I configure the PCs to use different backup jobs?734Views0likes2CommentsBoot von Recovery Disk SSR 2012R2
ich möchte in einem Windows 2012R2 \SQL Server 2012 Failover Cluster den 2. Knoten wiederherstellen. Backup lässt sich erstellen, Recover Disk\ Lightsout auch . Wenn ich das System von der CD booten will oder mit Lightsout starte bekomme ich nur einen schwarzen Bildschirm. Der Cluster (Cluster in a Box)ist virtuell auf VMWare ESXI 5.0 Vielen Dank für eure Hilfe892Views1like8CommentsSSR 2013 SRD Fails Boot on system with PERC H310 Raid Controller
I'm running SSR 2013 on a Dell 64 bit Precision T3600 independent workstation with a Xeon ES-1650.0 CPU, 16 GB of RAM and containing a PERC H310 Raid adapter that controlls two 1 TB HDs currently running as independant C: and D: drives (i.e., in non-RAID configuration). 2013 succdessfully backs up the C: (boot) drive to D: in weekly sets with offsite copy. However, attempting to restore C: from image using the 2013 SRD runs into an immediate probllem. When attempting to boot from the CD/DVD drive (preceded by the H310 boot from bios), even before the Windows logo appears, I get a blue screen stating: "Your PC needs to be repaired. There isn't enough memory available to create a ramdisk device. Error Code 0xC00000017." Attempting to use Lights Out produces the same result.. I attempted to customize the SRD with the H310 driver (percsas2.sys), but the SRD Wizard would not accept the .sys file. So I have two questions: 1. Could the problem be caused by something other than the H310? 2. If the probllem is the H310 controller (none of my other systems without controllers have SRD recovery problems), is there a fix short of removing the H310? -- Jim3.4KViews0likes11Commentschanging 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 a recovery 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.8KViews0likes13CommentsBoot from SSR 2013 R2 Recovery Disk
I assume it goes without saying that the SecureBoot for UEFI-based computers must be disabled to permit booting from the SSR 2013 R2 Recovery Disk via an internal DVD/CD drive. The following information is provided by Microsoft support: "After disabling Secure Boot and installing other software and hardware, it may be difficult to re-activate Secure Boot without restoring your PC to the factory state." "Before disabling Secure Boot, consider whether it is necessary. From time to time, your manufacturer may update the list of trusted hardware, drivers, and operating systems for your PC. To check for updates, go to Windows Update, or check your manufacturer's website." I would like to know if I can somehow boot from my SSR 2013 R2 Recovery Disk via my internal DVD/CD drive without disabling SecureBoot so that i don't risk making a mess of my PC, or, if not, what the experience has been with other users regarding the disabling of SecureBoot to permit booting from the SSR disk.2.3KViews1like14CommentsProblem Symantec Backup Recovery 2013 with HP Proliant DL360p
Hi All, I've HP Proliant DL360p with a single partition (C:\) and also an hidden partition unallocated 100mb. I've installed Symantec Backup Recovery 2013 and when I try to run a backup, I don't find C:\ partition on the software, only the hidden partition. Do you have any suggestion? Below I've attached the part info file. Thanks Daniele "C:\Program Files\Symantec\Symantec System Recovery\Utility\PartInfo.exe" PID (5884) Base Build Number: 46236 Base Build Date: Aug 1 2012 12:46:32 OsVersion: Generation: Microsoft Windows Server 2008 R2 Flavor: Enterprise Server OsArchitecture: 64-bit operating system KernelType: Windows NT ProcessorArchitecture: x64 (EM64T/AMD64) VersionNumber: 6.1.7601 ServicePackVersionNumber: 1.0.0 KernelVersionNumber: 0.0.0 Path: file:///C:/Windows/ ComputerName: ENSVTISS Features: Execute64BitBinaries Execute32BitPrograms Hibernate MultipleMonitors NT4FTVolumes DynamicDisk NtfsLonghorn Fat32 CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (If cpu speed is specified, it is rated speed, which may not be current speed) CPU Vendor: GenuineIntel CPU Signature: 000206d7 CPU Features: bfebfbff Hyperthreads/core: 12 Cores/Package: 1 Logical procs/pkg: 12 Number of packages: 1 NX bit supported: Yes x64 Capable: Yes Supports HW Virtualization: Yes Virtual Addr Bits: 48 Physical Addr Bits: 46 OS CPU Count: 12 Processor Mask: 0000000000000fff Min App Addr: 0000000000010000 Max App Addr: 000007FFFFFEFFFF Page Size: 4096 Memory Usage: 13% Total Physical: 16349 MB Avail Physical: 14193 MB Total Page: 32696 MB Avail Page: 29572 MB Total Virtual: 8388607 MB Avail Virtual: 8388561 MB Avail Extended: 0 MB ========================================================================================================================= Disk Geometry Information for Disk 0 Sector Count: 286,677,120 (35,132 Cylinders, 255 Heads, 32 Sectors/Track) Signature: 88EB3C0 Detected Sector Size: 512 Detected Alignment: Cylinder ......................................................................................................................... System Part Table LBA # Boot BCyl Head Sect FS ECyl Head Sect StartSect NumSects ========================================================================================================================= \\?\Volume{2c4e2ae0-4656-11e2-975d-806e6f6e6963}\ On Disk Values: 0 0 80 0 64 1 07 25 88 32 2,048 204,800 C:\ On Disk Values: 0 1 0 25 89 1 07 1023 254 32 206,848 286,661,812 Calculated: 25 89 1 35155 120 20 WARNING: Partition above extends beyond the end of disk. ==================================================================================================================== Partition Information for Disk 0: 137 GB Volume Path PartitionType Status Size Part Table Lba # Start Sector Total Sectors ==================================================================================================================== Unallocated Pri 1 MB None -- 0 2,048 \\?\Volume{2c4e2ae0-4 NTFS Pri,Boot 100 MB 0 0 2,048 204,800 C:\ NTFS Pri 137 GB 0 1 206,848 286,661,812 - - - - - - - - - - Disk 0: Master Boot Record (Sector 0) - - - - - - - - - - - 0: 33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00 3ÀŽÐ¼.|ŽÀŽØ¾.|¿. 10: 06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00 .¹..üó¤Ph..Ëû¹.. 20: BD BE 07 80 7E 00 00 7C 0B 0F 85 0E 01 83 C5 10 ½¾.€~..|..…..ƒÅ. 30: E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00 âñÍ.ˆV.UÆF..ÆF.. 40: B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09 ´A»ªUÍ.]r.ûUªu. 50: F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74 ÷Á..t.þF.f`€~..t 60: 26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00 &fh....fÿv.h..h. 70: 7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13 |h..h..´BŠV.‹ôÍ. 80: 9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00 ŸƒÄ.žë.¸..».|ŠV. 90: 8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1C FE Šv.ŠN.Šn.Í.fas.þ A0: 4E 11 75 0C 80 7E 00 80 0F 84 8A 00 B2 80 EB 84 N.u.€~.€.„Š.²€ë„ B0: 55 32 E4 8A 56 00 CD 13 5D EB 9E 81 3E FE 7D 55 U2äŠV.Í.]ëž>þ}U C0: AA 75 6E FF 76 00 E8 8D 00 75 17 FA B0 D1 E6 64 ªunÿv.è.u.ú°Ñæd D0: E8 83 00 B0 DF E6 60 E8 7C 00 B0 FF E6 64 E8 75 èƒ.°ßæ`è|.°ÿædèu E0: 00 FB B8 00 BB CD 1A 66 23 C0 75 3B 66 81 FB 54 .û¸.»Í.f#Àu;fûT F0: 43 50 41 75 32 81 F9 02 01 72 2C 66 68 07 BB 00 CPAu2ù..r,fh.». 100: 00 66 68 00 02 00 00 66 68 08 00 00 00 66 53 66 .fh....fh....fSf 110: 53 66 55 66 68 00 00 00 00 66 68 00 7C 00 00 66 SfUfh....fh.|..f 120: 61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00 00 CD ah...Í.Z2öê.|..Í 130: 18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07 32 E4 . ·.ë. ¶.ë. µ.2ä 140: 05 00 07 8B F0 AC 3C 00 74 09 BB 07 00 B4 0E CD ...‹ð¬<.t.»..´.Í 150: 10 EB F2 F4 EB FD 2B C9 E4 64 EB 00 24 02 E0 F8 .ëòôëý+Éädë.$.àø 160: 24 02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69 $.ÃInvalid.parti 170: 74 69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72 tion.table.Error 180: 20 6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69 .loading.operati 190: 6E 67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E ng.system.Missin 1A0: 67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74 g.operating.syst 1B0: 65 6D 00 00 00 63 7B 9A C0 B3 8E 08 00 00 80 40 em...c{šÀ³Ž...€@ 1C0: 01 00 07 58 20 19 00 08 00 00 00 20 03 00 00 59 ...X...........Y 1D0: 01 19 07 FE E0 FF 00 28 03 00 B4 1C 16 11 00 00 ...þàÿ.(..´..... 1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............Uª \\?\Volume{2c4e2ae0-4656-11e2-975d-806e6f6e6963}\ ==================================================================================== Volume Boot Record for Disk 0: at Sector 2,048 (0x800) File System: NTFS (BPB NT Version) ==================================================================================== 1. Jump: EB 52 90 2. OEM Name: NTFS 3. Bytes per Sector: 512 4. Sectors per Cluster: 8 5. Reserved Sectors: 0 6. Number of FATs: 0 7. Root Dir Entries: 0 8. Total Sectors: 0 9. Media Descriptor: F8 10. Sectors per FAT: 0 11. Sectors per Track: 32 (0x0020) 12. Number of Heads: 255 (0x00FF) 13. Hidden Sectors: 2048 (0x00000800) 14. Total Sectors (>32 MB): 0 (0x00000000) 15. Disk Unit Number: 128 (0x80) 16. Reserved For NT: 0x00 17. Extended Boot Sig: 0x80 18. Reserved: 0x00 19. Total NTFS Sectors: 204799 20: MFT Start Cluster: 8533 21: MFT Mirror Start Clust: 2 22: MFT First Cluster: 8533 23: Clusters per FRS: 246 24: Clusters per Index Blk: 1 25: Serical Number: 0xD6F613C9F613A8AF 26: Checksum: 0 (0x00000000) - - - Disk 0: Volume Boot Record Hex Dump at Sector 2,048 (0x800) - - - 0: EB 52 90 4E 54 46 53 20 20 20 20 00 02 08 00 00 ëRNTFS......... 10: 00 00 00 00 00 F8 00 00 20 00 FF 00 00 08 00 00 .....ø....ÿ..... 20: 00 00 00 00 80 00 80 00 FF 1F 03 00 00 00 00 00 ....€.€.ÿ....... 30: 55 21 00 00 00 00 00 00 02 00 00 00 00 00 00 00 U!.............. 40: F6 00 00 00 01 00 00 00 AF A8 13 F6 C9 13 F6 D6 ö.......¯¨.öÉ.öÖ 50: 00 00 00 00 FA 33 C0 8E D0 BC 00 7C FB 68 C0 07 ....ú3ÀŽÐ¼.|ûhÀ. 60: 1F 1E 68 66 00 CB 88 16 0E 00 66 81 3E 03 00 4E ..hf.ˈ...f>..N 70: 54 46 53 75 15 B4 41 BB AA 55 CD 13 72 0C 81 FB TFSu.´A»ªUÍ.r.û 80: 55 AA 75 06 F7 C1 01 00 75 03 E9 DD 00 1E 83 EC Uªu.÷Á..u.éÝ..ƒì 90: 18 68 1A 00 B4 48 8A 16 0E 00 8B F4 16 1F CD 13 .h..´HŠ...‹ô..Í. A0: 9F 83 C4 18 9E 58 1F 72 E1 3B 06 0B 00 75 DB A3 ŸƒÄ.žX.rá;...uÛ£ B0: 0F 00 C1 2E 0F 00 04 1E 5A 33 DB B9 00 20 2B C8 ..Á.....Z3Û¹..+È C0: 66 FF 06 11 00 03 16 0F 00 8E C2 FF 06 16 00 E8 fÿ.......ŽÂÿ...è D0: 4B 00 2B C8 77 EF B8 00 BB CD 1A 66 23 C0 75 2D K.+Èwï¸.»Í.f#Àu- E0: 66 81 FB 54 43 50 41 75 24 81 F9 02 01 72 1E 16 fûTCPAu$ù..r.. F0: 68 07 BB 16 68 70 0E 16 68 09 00 66 53 66 53 66 h.».hp..h..fSfSf 100: 55 16 16 16 68 B8 01 66 61 0E 07 CD 1A 33 C0 BF U...h¸.fa..Í.3À¿ 110: 28 10 B9 D8 0F FC F3 AA E9 5F 01 90 90 66 60 1E (.¹Ø.üóªé_.f`. 120: 06 66 A1 11 00 66 03 06 1C 00 1E 66 68 00 00 00 .f¡..f.....fh... 130: 00 66 50 06 53 68 01 00 68 10 00 B4 42 8A 16 0E .fP.Sh..h..´BŠ.. 140: 00 16 1F 8B F4 CD 13 66 59 5B 5A 66 59 66 59 1F ...‹ôÍ.fY[ZfYfY. 150: 0F 82 16 00 66 FF 06 11 00 03 16 0F 00 8E C2 FF .‚..fÿ.......ŽÂÿ 160: 0E 16 00 75 BC 07 1F 66 61 C3 A0 F8 01 E8 09 00 ...u¼..faà ø.è.. 170: A0 FB 01 E8 03 00 F4 EB FD B4 01 8B F0 AC 3C 00 û.è..ôëý´.‹ð¬<. 180: 74 09 B4 0E BB 07 00 CD 10 EB F2 C3 0D 0A 41 20 t.´.»..Í.ëòÃ..A. 190: 64 69 73 6B 20 72 65 61 64 20 65 72 72 6F 72 20 disk.read.error. 1A0: 6F 63 63 75 72 72 65 64 00 0D 0A 42 4F 4F 54 4D occurred...BOOTM 1B0: 47 52 20 69 73 20 6D 69 73 73 69 6E 67 00 0D 0A GR.is.missing... 1C0: 42 4F 4F 54 4D 47 52 20 69 73 20 63 6F 6D 70 72 BOOTMGR.is.compr 1D0: 65 73 73 65 64 00 0D 0A 50 72 65 73 73 20 43 74 essed...Press.Ct 1E0: 72 6C 2B 41 6C 74 2B 44 65 6C 20 74 6F 20 72 65 rl+Alt+Del.to.re 1F0: 73 74 61 72 74 0D 0A 00 8C A9 BE D6 00 00 55 AA start...Œ©¾Ö..Uª C:\ ==================================================================================== Volume Boot Record for Disk 0: at Sector 206,848 (0x32800) File System: NTFS (BPB NT Version) ==================================================================================== 1. Jump: EB 52 90 2. OEM Name: NTFS 3. Bytes per Sector: 512 4. Sectors per Cluster: 8 5. Reserved Sectors: 0 6. Number of FATs: 0 7. Root Dir Entries: 0 8. Total Sectors: 0 9. Media Descriptor: F8 10. Sectors per FAT: 0 11. Sectors per Track: 63 (0x003F) 12. Number of Heads: 255 (0x00FF) 13. Hidden Sectors: 206848 (0x00032800) 14. Total Sectors (>32 MB): 0 (0x00000000) 15. Disk Unit Number: 128 (0x80) 16. Reserved For NT: 0x00 17. Extended Boot Sig: 0x80 18. Reserved: 0x00 19. Total NTFS Sectors: 286470271 20: MFT Start Cluster: 4 21: MFT Mirror Start Clust: 17904391 22: MFT First Cluster: 4 23: Clusters per FRS: 246 24: Clusters per Index Blk: 1 25: Serical Number: 0x46C97BA72BD861B8 26: Checksum: 0 (0x00000000) - - - Disk 0: Volume Boot Record Hex Dump at Sector 206,848 (0x32800) - - - 0: EB 52 90 4E 54 46 53 20 20 20 20 00 02 08 00 00 ëRNTFS......... 10: 00 00 00 00 00 F8 00 00 3F 00 FF 00 00 28 03 00 .....ø..?.ÿ..(.. 20: 00 00 00 00 80 00 80 00 7F 30 13 11 00 00 00 00 ....€.€.0...... 30: 04 00 00 00 00 00 00 00 07 33 11 01 00 00 00 00 .........3...... 40: F6 00 00 00 01 00 00 00 B8 61 D8 2B A7 7B C9 46 ö.......¸aØ+§{ÉF 50: 00 00 00 00 FA 33 C0 8E D0 BC 00 7C FB 68 C0 07 ....ú3ÀŽÐ¼.|ûhÀ. 60: 1F 1E 68 66 00 CB 88 16 0E 00 66 81 3E 03 00 4E ..hf.ˈ...f>..N 70: 54 46 53 75 15 B4 41 BB AA 55 CD 13 72 0C 81 FB TFSu.´A»ªUÍ.r.û 80: 55 AA 75 06 F7 C1 01 00 75 03 E9 D2 00 1E 83 EC Uªu.÷Á..u.éÒ..ƒì 90: 18 68 1A 00 B4 48 8A 16 0E 00 8B F4 16 1F CD 13 .h..´HŠ...‹ô..Í. A0: 9F 83 C4 18 9E 58 1F 72 E1 3B 06 0B 00 75 DB A3 ŸƒÄ.žX.rá;...uÛ£ B0: 0F 00 C1 2E 0F 00 04 1E 5A 33 DB B9 00 20 2B C8 ..Á.....Z3Û¹..+È C0: 66 FF 06 11 00 03 16 0F 00 8E C2 FF 06 16 00 E8 fÿ.......ŽÂÿ...è D0: 40 00 2B C8 77 EF B8 00 BB CD 1A 66 23 C0 75 2D @.+Èwï¸.»Í.f#Àu- E0: 66 81 FB 54 43 50 41 75 24 81 F9 02 01 72 1E 16 fûTCPAu$ù..r.. F0: 68 07 BB 16 68 70 0E 16 68 09 00 66 53 66 53 66 h.».hp..h..fSfSf 100: 55 16 16 16 68 B8 01 66 61 0E 07 CD 1A E9 6A 01 U...h¸.fa..Í.éj. 110: 90 90 66 60 1E 06 66 A1 11 00 66 03 06 1C 00 1E f`..f¡..f..... 120: 66 68 00 00 00 00 66 50 06 53 68 01 00 68 10 00 fh....fP.Sh..h.. 130: B4 42 8A 16 0E 00 16 1F 8B F4 CD 13 66 59 5B 5A ´BŠ.....‹ôÍ.fY[Z 140: 66 59 66 59 1F 0F 82 16 00 66 FF 06 11 00 03 16 fYfY..‚..fÿ..... 150: 0F 00 8E C2 FF 0E 16 00 75 BC 07 1F 66 61 C3 A0 ..ŽÂÿ...u¼..faà 160: F8 01 E8 08 00 A0 FB 01 E8 02 00 EB FE B4 01 8B ø.è.. û.è..ëþ´.‹ 170: F0 AC 3C 00 74 09 B4 0E BB 07 00 CD 10 EB F2 C3 ð¬<.t.´.»..Í.ëòà 180: 0D 0A 41 20 64 69 73 6B 20 72 65 61 64 20 65 72 ..A.disk.read.er 190: 72 6F 72 20 6F 63 63 75 72 72 65 64 00 0D 0A 42 ror.occurred...B 1A0: 4F 4F 54 4D 47 52 20 69 73 20 6D 69 73 73 69 6E OOTMGR.is.missin 1B0: 67 00 0D 0A 42 4F 4F 54 4D 47 52 20 69 73 20 63 g...BOOTMGR.is.c 1C0: 6F 6D 70 72 65 73 73 65 64 00 0D 0A 50 72 65 73 ompressed...Pres 1D0: 73 20 43 74 72 6C 2B 41 6C 74 2B 44 65 6C 20 74 s.Ctrl+Alt+Del.t 1E0: 6F 20 72 65 73 74 61 72 74 0D 0A 00 00 00 00 00 o.restart....... 1F0: 00 00 00 00 00 00 00 00 80 9D B2 CA 00 00 55 AA ........€²Ê..Uª Volumes Reported by OS ========================================================================================================================================== Volume Path (Volume GUID) Disk # Offset in Bytes Size in Bytes Starting Sector Ending Sector Size ========================================================================================================================================== No path name found (\\?\Volume{2c4e2ae0-4656-11e2-975d-806e6f6e6963}\) Disk # 0 1,048,576 104,857,600 2,048 206,847 100 MB C:\ (\\?\Volume{2c4e2ae1-4656-11e2-975d-806e6f6e6963}\) Disk # 0 105,906,176 146,770,847,744 206,848 286,868,659 137 GB1.3KViews0likes5CommentsError while launching Symantec System Recovery Disk Wizard
After installing Symantec system recovery 2013 R3 Desktop, I tried to make a System recovery disk by starting the wizard. However I get the error message: Failed to create a 'ImageSource' from the text 'pack://application:,,,,/Symantec.UI.WpfResources;component/images/error_16.gif'. After closing the message the wizard will not startup again untill the computer is restarted. After a restart the message pops up again. I reinstalled alrady but without succes. Does anybody have suggestions how to repair and be able to create a SSRD?Solved1.4KViews0likes9CommentsDrive information in SSR 2013 R2 event log messages
Hi, When SSR 2013 starts a diskbased job, it logs the following message to the Windows event log: Info 6C8F1F65: The drive-based backup job, Drive Backup of (*:\), (C:\), (E:\), has been started automatically. When SSR 2013 R2 starts a diskbased job, it logs the following message to the Windows event log: Info 6C8F1F65: The drive-based backup job, Full Backup, has been started automatically. While i think it is a good thing that the job name is now included I miss which drives are being backed up. Is there anyway to get SSR R2 to also log which drives are backed up? Or can it be added again in an update / servicepack? I use this information in a monitoring application and this causes issues for me. Regards KristofferSolved723Views0likes3Comments