SSR 2013 - ReFS support, when?
When is SSR 2013 Server Edition going to support volumes formatted as ReFS for full/incremental recovery points? BTW the discussion creation form doesn't include "Windows Server 2012" in the dropdown list of Operating systems, only Server 2003 and 2008 is there.478Views0likes4CommentsOff to a bad start with System Recovery 2013 R2 SP4
I was glad to see the long awaited System Recovery 2013 R2 SP4 version out today so I downloaded it and thought I'd get right to testing it on my first system. Unfortunatly, I cannot even install the product. I'm trying to install on a system with the following characteristics: ------------ Intel Core i7 Processor 32GB RAM Boot Drive is a 500GB SSD OS is Windows 10 with the November 2015 update, 64-Bit ------------ I launch the install by running "browser.exe". I get the initial welcome screen with the various elements such as Getting Started, Installation, etc. At this point I click on "Install Now". At this point a screen opens that says "Loading the install. Please wait..." but within about 2 seconds the screen disappears and nothing more happens. Note that there is no error message, the program just seems to go away completely and the "Setup Launcher" disappears from the task list if I'm monitoring it while I attempt the install. As a test, I tried the install on a Windows 7 system and it worked perfectly. Is this possibly a problem with the November Update to Windows 10? I sure hope that we don't have to wait for another update that supports the November Update :-) Anyone else having any better luck than me?Solved6.3KViews2likes47Commentsmoving data from unused area
Hi, I'm wondering what exactly SSR2013 is doing when it's at 99% done and stalled seemingly forever at "Moving data from unused area?" There's no indication of how long this will take, and I'm just sitting here thinking of things to do. I can't really leave the system for any length of time because it might finish the crive copy at any moment. So I'm just stuck here grumbling. What I can't understand is what data there is in an unused area. If it's unused, then why is the date important to me, and why do I have to wait interminably while it is moved? Why can't there be some kind of progress indicator so I can know where I am in the process? GaryK3.3KViews0likes20CommentsSSR2013 - ERROR: Installation failed with error -532462766.
Hey everybody, For some reason the Symantec website does not let me create a new support case (times out), therefor I'm hoping this forum might be of any help. I'm trying to install SSR2013 R2 for one of my clients (W8.1 Pro 64bit). When I run browser.exe or the SSRx64 setup.exe the installation starts with the message 'Loading the install. Please wait... ‘. After a few seconds this message disappears and the setup ends without reporting a clear error. However I checked the SSRINST.html file within the C:\ProgramData\Symantec\SYMANTEC SYSTEM RECOVERY\LOGS folder. It reports the following error: Symantec System Recovery (TM) 2013 R2 Installation Log 02-09-2015,09:39:31 : EnumProcesses Counts: 79 02-09-2015,09:39:31 : OS is Windows 8 or Windows 2012. 02-09-2015,09:39:31 : The OS product type is Workstation. 02-09-2015,09:39:33 : Executing managed _Setup: 02-09-2015,09:39:33 : C:\Users\Voip\Downloads\SSR\Sym_System_Recovery_2013R2_11.1.0.53728_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe 02-09-2015,09:39:35 : ERROR: Installation failed with error -532462766. GetLastError = :0 As test, I also tried to install SSR2013 (so not the R2 version) but it reports a similar error: Symantec System Recovery (TM) 11.0 Installation Log 02-09-2015,11:27:17 : EnumProcesses Counts: 76 02-09-2015,11:27:17 : OS is Windows 8 or Windows 2012. 02-09-2015,11:27:17 : The OS product type is Workstation. 02-09-2015,11:27:19 : Executing managed _Setup: 02-09-2015,11:27:19 : C:\Users\Voip\Downloads\Sym_System_Recovery_2013_11.0.2.49853_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe 02-09-2015,11:27:21 : ERROR: Installation failed with error -532462766. GetLastError = :0 Support would be appreciated. Thank you.Solved4.2KViews0likes9CommentsSSR Backups constantly fail
I am running SSR2013 on a Windows2012R2 server trying to back up the two local drives to a NAS device with a shadow copy to a USB drive but it costantly fails with the following: --Unable to write to file. ---Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'An unexpected network error occurred.' ---Unable to set file size. ----Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'An unexpected network error occurred.' (UMI:V-281-2001-31) I have checked the following: There is enough hard drive space on the NAS All of the permissions are correct There are no obviously associated event log entries The job starts and creates three ".tmp" files for the bakup of C: and up to 4 ".tmp" file for X: and then it fails. There were about 21 ".tmp" files for the X: drive the one and only time it worked and the system is set to split the files at 9.4GB in size. The server is hosting two Hyper-V guests and the VHDX files are on the X: drive. The annoying thing is that the backup worked once last week (running a base backup) and then we had two differentials as well but this week absolutely nothing will work. I have set it up to create a new base backup each week with Diffs every other day (mon-fri) If anyone has any ideas please let me know.1.9KViews0likes5CommentsError EC8F17B7 along with Error ED800012: (CRC Validation) is invalid & Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service
Hi I am trying to backup a PC using SSR2013 (Desktop ed). I have created a custom backup job to run on schedule but the backup continuously fails. I find the following error in the event log afterwards: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), (D:\). Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: VSS_E_OBJECT_NOT_FOUND (-2147212536). (UMI:V-281-3215-6071) After running the job manually, I find the following in the event log: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\). Error ED800012: The internal structure of the recovery point file (CRC Validation) is invalid, damaged or unsupported. (UMI:V-281-3215-6071) I have been trying a few solutions found on the Symantec website regarding these errors, but have not received any good results. I have also not found a solution that relates to SSR2013... Thanks Zaid3.8KViews0likes16CommentsSymantec System Recovery 2013 - restore to new VM
We're running Symantec System Recovery 2013 on Windows Server 2012. It's scheduled to create recovery point sets with a "full" backup once a week, then "incremental" ones in between. That's all working fine, and we can restore individual files from the backups with no problems. However, we'd also like this to work as a form of disaster recovery, in that if the building were to burn down, we'd like to be able to restore an offsite copy of the latest recovery point to a new virtual machine at a datacentre. I've been testing this process by creating a new VM, and booting with the Symantec Recovery DVD to perform the restore. Although the restore process runs to completion, there seems to be a problem with drivers, and the newly-created VM doesn't boot properly to Windows. The "Restore Anywhere" feature of Symantec System Recovery 2013 is definitely enabled. The newly-created VM gets most of the way through the initial boot process but, before the logon screen is reached, an alert box appears "Windows Setup could not configure Windows to run on this computer's hardware". I'm using the latest version of Oracle Virtualbox for the VM host, with default virtual hardware, which normally Windows Server 2012 supports with no problems. I've also tried using a virtual IDE drive or virtual SCSI drive for my VM, instead of the default SATA virtual hardware. The original physical server has an Fujitsu SAS 6Gb/s RAID 5/6 512MB (D2616) Adapter and a RAID-5 array. I've also tried using the feature built in to Symantec System Recovery which allows the conversion of the latest recovery point to a VHD file. I've tried the file it creates both with Virtualbox and with "proper" Hyper-V running under Windows Server 2012 R2, and in both cases I get the same error message when the VM boots. I'm not clear why this isn't working - any ideas, please? I'm assuming it's something to do with mass storage drivers, but perhaps I'm barking up the wrong tree?Solved4.8KViews1like11CommentsA 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.12KViews1like8CommentsI 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?1.9KViews0likes5CommentsError EBAB03F1: 'Logon failure: unknown user name or bad password.'
Hi. When I attempt to use Manage Backup Destinations, then select an old backup set and select delete, it sits for a while and then produces the following error: Info 6C8F1C25: While the recovery points have been removed, the actual recovery point files could not be deleted. ---Error E7D10041: Unable to establish a network connection to \\server\backups. ----Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ----Error E7D10041: Unable to establish a network connection to \\server\backups. -----Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -----Error E7D10041: Unable to establish a network connection to \\server\backups. ------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ------Error E7D10041: Unable to establish a network connection to \\server\backups. -------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -------Error E7D10041: Unable to establish a network connection to \\server\backups. --------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' --------Error E7D10041: Unable to establish a network connection to \\server\backups. ---------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ---------Error E7D10041: Unable to establish a network connection to \\server\backups. ----------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ----------Error E7D10041: Unable to establish a network connection to \\server\backups. -----------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -----------Error E7D10041: Unable to establish a network connection to \\server\backups. ------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ------------Error E7D10041: Unable to establish a network connection to \\server\backups. -------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -------------Error E7D10041: Unable to establish a network connection to \\server\backups. --------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' --------------Error E7D10041: Unable to establish a network connection to \\server\backups. ---------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ---------------Error E7D10041: Unable to establish a network connection to \\server\backups. ----------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ----------------Error E7D10041: Unable to establish a network connection to \\server\backups. -----------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -----------------Error E7D10041: Unable to establish a network connection to \\server\backups. ------------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ------------------Error E7D10041: Unable to establish a network connection to \\server\backups. -------------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' -------------------Error E7D10041: Unable to establish a network connection to \\server\backups. --------------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' --------------------Error E7D10041: Unable to establish a network connection to \\server\backups. ---------------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' ---------------------Error E7D10041: Unable to establish a network connection to \\server\backups. ----------------------Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Logon failure: unknown user name or bad password.' If I go into the backup job and run it, it runs correctly so I know it can access the share. Just for information I am backing up a domain joined server to a share that is not part of the domain. Any ideas on why this is happening? Should I go and just delete the old backup set? Thanks, Lyle Epstein Kortek Solutions1KViews0likes1Comment