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 theCommand-line optionsfield of theCommand -linetab of theAdvancedoption of theDeploy Imagetask: -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 isbeing discontinued what can I do?1.9KViews0likes5CommentsHot 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?2KViews0likes3CommentsSymantec 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.2.9KViews0likes14CommentsDifferent 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?729Views0likes2CommentsHigh Priority Failure Notification (Error) from Symantec System Recovery
I received the following email this morning. This is from a Windows 7 computer that has had the hard drive replaced twice under warranty in the past three years. I am currently running chkdsk /f /r with the hopes of "correcting" whatever seems to be wrong. Please also note that the back-up files go to a NAS device that has more than 330 GB free space. Any additional help in identifying the actual culprit would be much appreciated. Date: 12/9/2015 7:01:40 AM Notification Type: Error Priority: High Description: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of System Reserved (*:\), OS (C:\). Error E0BB0083: Unable to create incremental recovery point. Error E7C3000F: Device \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy54 cannot read 7632 sectors starting at LBA 109539840. Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'The request could not be performed because of an I/O device error.' Details: 0xE0BB0083 Thanks!Solved1.2KViews0likes5CommentsCreate a Recovery USB Stick only for BIOS Systems
Hello, can i only create a Recovery USB Stick for BIOS Systems? The Windows 7 is installed in the BIOS Version. The Image is also a BIOS Version.When i boot with the Recovery USB Stick, it always boots in EFI Mode. I know, i can change in the boot manager to boot in bios mode, but i want this do. when i forget to change the boot option then ssr says, BIOS Images cannot restore on EFI System, because the first boot is the SSR EFI USB Stick. Can i change this? kind regards Blacksun736Views0likes4CommentsSymantic System Recovery 2013 R2 has suddenly stopped working on Small Business Server 2008
Symantic System Recovery 2013 R2 has suddenly stopped working on Small Business Server 2008 I have been using theSymantic System Recovery 2013 R2 for several months on our SBS 2008 and have not had any problems. Suddenly, last week it stopped creating backups. There were no Microsoft updates installed prior to the program failing and no other configuration items on the server have been changed. I am seeing the following error in the event log: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), DATA (D:\), EXCHANGE (F:\). Error E4F3000F: Unexpected VSS writer error. Check the application event log for writer specific error. Failed VSS writers: BITS Writer. (UMI:V-281-3215-6071) Details: Source: Symantec System Recovery The program is working fine on my other server which runs Windows Server 2008 R2 Standard. Can you please advise me as to how I can resolve this issue?2KViews0likes8Comments