Can't Backup windows server 2012 R2 drive C: and D:
Dears; please i need your help with the following issue : i cant backup windows server 2012 R2 server with Symantec System Recovery 2013 R2 all Drives (C: ; D:) i always got the following error : Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (*:\), (C:\). Error E0BB00B5: Snapshot error Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'OS error 2147754767.'. (UMI:V-281-3215-6071) Details: Source: Symantec System RecoverySolved7.3KViews0likes9CommentsSreEula.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 Trial - VSS_E_INSUFFICIENT_STORAGE error
Just downloaded SSR 2013 trial. (I was a Ghost 15 user, but upgraded to Windows 8 so can no longer use Ghost.) On my first attempt to do a backup of my drive, I got a VSS_E_INSUFFICIENT_STORAGE error. A bit of online research made me think I had to go to System Properties|System Protection and increase the amount of disk space available for system protection, which I did. I increased it from about 9GB to about 100GB. That did not help. FWIW, my hard drive is about 923GB, with about 760GB free. Any guidance? Many thanks. Ken5.2KViews1like90CommentsWindows Server 2012 R2 UEFI Restore Impossible?
I'm trying to do something that is dead simple, but frustratingly it's killing me... One little thing, just trying to backup and restore Windows Server 2012 R2 on an Intel i7 PC that's in UEFI mode with GPT partitions on a SATA SSD drive. Symantec System Recovery 2013 SP2 x64 v11.0.2.49853 has no problem going through the paces of restoring the backup, but afterward Windows fails to boot. I even went to the extent of wiping the C drive (and all the partitions), reinstalled WS2012 R2 Data Center GUI (nothing else except a network driver and SSR), backed up freshly installed WS2012 R2 to an external USB drive using SSR installed inside Windows, wiped the C drive (and all the partitions) and restored the backup, but all that effort didn't matter. PC still won't boot Windows. I also tried restoring the 100MB EFI Partition first, followed by the operating system and Recovery partitions, still no help. The only odd thing I see is inside the WinPE SRD, About - Symantec System Recovery Disk shows versions that seem old even though it was just extracted from the latest v11.0.2.49853 download zip file (although the SRD .iso file date of 12/15/13 is older than the SSR SP2 11.0.2 update that supposedly fixed UEFI problems). Symantec System Recovery Disk Symantec Recovery Toolkit 11.0.0 Version 11.0.0.49496 Copyright 1994-2012 Please scroll down to access my troubleshooting documentation "Symantec System Recovery 2013 x64 SP2 v11.0.2.49853 UEFI Restore Problem.pdf" with a detailed collection of photos showing the entire backup and restore process. Do you see anything usual or something that I'm doing wrong?Please help because obviously I am unhealthily obsessed with this problem! ;-) Thanks! FWIW, I have reviewed these articles, comments and tips about SSR and restoring UEFI partitions: http://www.symantec.com/business/support/index?page=content&id=HOWTO84141 http://www.symantec.com/business/support/index?page=content&id=TECH177792 http://www.symantec.com/business/support/index?page=content&id=TECH128386 http://www.symantec.com/business/support/index?page=content&id=TECH207176 http://www.symantec.com/business/support/index?page=content&id=TECH200291 http://www.symantec.com/business/support/index?page=content&id=TECH200293 https://www-secure.symantec.com/connect/forums/ssr-201020112013-and-restore-anyware-uefi And, tried these suggestions too: https://neosmart.net/wiki/0xc0000225/5.1KViews2likes8CommentsDatabase named "RollbackSnapshotTempDB" left after System Recovery 2013 backup
We have a Windows Server 2008 R2 server with SQL Server 2008 R2 x64 installed. We have been using Backup Exec 2010 to perform Full and Transaction log backups of the databases in our SQL server, and System Recovery 2010 to backup the entire server. A couple weeks ago we upgraded System Recovery 2010 to 2013 and we noticed our Backup Exec 2010 jobs started failing. After investigating we discovered several databases named "RollbackSnapshotTempDB" were piling up. We tried to right-click the DB and go to properties but received an error message. The SQL logs showed a lot of errors related to those "RollbackSnapshotTempDB" databases, such as: Date7/2/2013 6:07:37 AM LogSQL Server (Current - 7/16/2013 8:38:00 AM) Sourcespid400 Message The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000053fc2000 in file '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy11\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\XXXXXX.MDF'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. And: Date7/2/2013 6:07:37 AM LogSQL Server (Current - 7/16/2013 8:38:00 AM) Sourcespid400 Message Error: 823, Severity: 24, State: 2. If I go into the SQL Server Management Studio and and try to delete the "RollbackSnapshotTempDB" databse I receive an error that says "Cannot drop the database because it is being used for replication". However if I take the "RollbackSnapshotTempDB" database offline then I can delete it, and the next Backup Exec 2010 SQL backup job will complete successfully. These errors seem to indicate a file system problem, however a CHKDSK shows no problems. We have rebooted the server as well with no change. I have googled this issue until I'm blue in the face and have not found any solutions. Does anyone have any ideas? Here are more details on the server: Virtual Server running on ESXi 5.1 Update 1 Physical host is HP Proliant DL380 G6 Storage provided by HP LeftHand iSCSI SAN Server 2008 R2 with all Windows Updates applied SQL Server 2008 R2 with all Windows Updates applied Server has two vCPU's and 12GB of RAM C: drive has 21GB free D: drive has 88GB free (D: is where all the SQL data files are stored)4.9KViews1like40CommentsError EBAB03F8 still occurs in SSR 2013 R2
Hi! I have installed SSR 2013 (R1) on about 10 current Dell Optiplex PCs with Win 8.1 Pro (Update 1). I have setup two simple daily backups: One full backup to a server on my network and one incremental to a PC's local HDD. On every PC now and then the incremental backups fail with the strange error: EBAB03F8: 'CHECK failed, Computer::CreateImageFile: Computer.cpp(1517): guid != Guid() && sequence != 0xffffffff && sequence > 0.'. (UMI:V-281-3215-6071) This means that the incremental backups cannot be created successfully for some unknown reason and a new base has to be recreated next time the backup runs. This is really annoying and I had reported this error in the past without receiving any solution here in the forums. Now I hoped that SSR 2013 R2 would finally solve the problem but it did not. I upgraded one PC to SSR 2013 R2 (yes you really have to pay for this "updgrade") and the same error occurs again. The main error reference I found is this: http://www.symantec.com/business/support/index?page=content&id=TECH217964 I wonder how long Symantec needs to get this hotfix tested and merged into the release. I am getting this error on each of my PCs and I am seriously considering to switch to a different backup product if the issue is not going to be solved immediately because it makes the program useless. Other knowledge base articles state that the error might be caused by another backup program installed. There is no such program installed. Anti-virus used is from Symantec (Norton Internet Security) so this should have been tested at least to work ok... Anguel4.9KViews1like56CommentsBIOS 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.4.2KViews1like12CommentsError 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.7KViews0likes16CommentsError E4F3000E: Snapshot failure while using Volume Shadow Copy Service
Hi All, I'm having an issue with System Recovery 2013 backing up to an Iomega NAS, Please see the below error: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), System Reserved (C:\LiveVaultData\BootDir_MP\), (E:\). Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: EndCreateSnapshotSet (-2147212303). (UMI:V-281-3215-6071) Details: Source: Symantec System Recovery I do have a seperate cloud backup solution running as well. Its called 'Live Vault'. Not sure if this helps or not. The server is a Windows 2012 SBS server running Symantec System Recovery 2013 sbs edition, Version 11.0.0.56600 Any help would be much appreciated.Solved3.6KViews0likes4CommentsHow do I create a Custom Recovery Disk using the SSR 2013 Trial
I've just downloaded the SSR 2013 trial and want to create a bootable recovery disk. From what I can tell from the unavailable user guide and sparse help file, I need the to have a SSR disk or SSR recovery .iso in hand and neither was provided with the trial. Is there a way to proceed without them?3.3KViews1like31Comments