Error E98F001E: Failed to update data in the database
Hello, I have Backup Exec System Recovery 2010 and have set up email notifications for it. Occasionally I'd getting an email saying Description: Info 6C8F1F7E: A scheduled incremental recovery point of drive *:\ was created successfully. Error E98F001E: Failed to update data in the database. Error E98F001E: Failed to update data in the database But along with this email I get also emails saying that the off-site copy was created successfully and that the backup job was also completed successfully. Can I ignore this email? Are my restore points safe? Or am I going to have a problem if I try to restore one the restore points that reterun this error? Thank you in advance.1.8KViews0likes3CommentsSystem Recovery 2010 SRD
Hello, we have an SBS 2011 Standard Server, with Symantec Backup Exec System Recovery 2010 installed. We have setup System Recovery to save restore point on a NAS. We don't have the System Recovery Disk. From the following post https://vox.veritas.com/t5/System-Recovery/SSR-2011-Symantec-System-Recovery-Disk-ISO-download/m-p/868337/highlight/true#M31511 my understanding is that it's a very old version so there isn't a way to get the ISO. If i get the latest version, trial, will I be able to create a recovery disk? And if I do, will I be able to use the recovery points created from our 2010 System Recovery? Thank you very muchSolved2.8KViews0likes4CommentsIncomplete backup
We were running a backup on a sbs2008 server that got to 90%. Shortly after that the hard drives on the server failed. The image file won't mount and gets a ED800012 The internal structure of the recovery point is invalid. Is it possible to recover data from a incomplete backup? Any help would be appreciated.1.1KViews0likes3CommentsSystem crash
Hello, We had the Backup Exec System Recovery software to run the backup job everyday on all of our servers. Due to "unauthorized" access, our HP EVA4400 Storagework configuration got deleted which caused all the data stored on that EVA got loss. (There are 3 physical servers that connected to EVA for data access) Please let me know what would be the best way to get all the data back? Best regards, Key1.2KViews0likes3CommentsBackup Failing with error 0xe7d1001e, 0xbab0012, 0xebab03f1, 0xbab000d
Hi, My daily backup is intermittently failing with the below error message. This happens on different backup drivers, and just on the C drive. Completes fine on all other drivers and servers on and around the time it tries to backup the C drive on this 1 server. Even though it backs up another drive on this server without any issue. I rotate between 4 backup drives and it doesnt follow a pattern, one day itll be successful and another failed. (0xe7d1001e 26 FILEACCESS_ERROR_CANT_READ Args [1] Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 50 The specified network name is no longer available.);));) Error EC8F17B7: Cannot create recovery points for job: C:\ Full Backup. Error E7D1001E: Unable to read from file. Error EBAB03F1: The specified network name is no longer available. Any help is appreciated2.2KViews0likes6CommentsBackups failing with errors 0xe7c3000f, 0xbab000d, 0xbab0009,0x27352268
Hi, I was hoping someone could help, i am getting the below error and can't seem to find much help online regarding this. I have tried a chkdsk however it still fails after this. I am running BESR 2010. Full backup of Drive E:\ FAILED. The exact message is: Result (0xe7c3000f 37 SECTORBUFFER_ERROR_DEVICE_READ_FAILED Args [4] Arg (0xbab000d 21 \\?\SymantecSnapshot2) Arg (0xbab0009 0x27352268) Arg (0xbab0009 0x2018) Arg (0xbab0012 Result (0xebab03f1 14 ERROR_OS_ERROR Args [1] Arg (0xbab000d 19 Incorrect function.);));) Thanks,Solved3.1KViews0likes9CommentsSymantec System Recovery 2010 - email notifications
Hello, Our customer install base uses Symantec Backup Exec System Recovery for backing up key servers and we have been asked the following question... We are currently configuring email notifications and in line with Symantec documentation, Errors / Warnings / Information can be selected along with the priorities of All / Medium / High. The documentation does not say however what type of scenario is regarded as an Error / Warning / Information. Test runs of the set up seem to have provided email notifications which were not quite in line with expectation; some examples include: Execution of an Auto backup is regarded as INFO (Medium) notification, with the associated generation of a recovery point (this is a routine step run during Auto backup) regarded as INFO (High); Manual backup initiation is regarded as INFO (High). (So some of the routine steps executed during Auto backup (in this example the generation of a recovery point) is ranked higher in INFO terms than the overall Auto backup itself; manually starting a backup is regarded as higher in INFO terms than auto backup.) Date: 6/28/2017 8:34:02 AM Notification Type: Info Priority: Medium Description: Info 6C8F0427: Backup Exec System Recovery service started successfully. Date: 7/9/2017 4:08:37 AM Notification Type: Info Priority: High Description: Info 6C8F1F7D: A scheduled base recovery point of drive C:\ was created successfully. Date: 6/27/2017 11:10:25 AM Notification Type: Info Priority: High Description: Info 6C8F1F63: The drive-based backup job, Manual_Sys_Backup, has been started manually. Where a backup is stopped, it is regarded as INFO (Medium): (this doesn’t seem consistent with Auto / Manual levelling mentioned in point one above). Date: 6/28/2017 8:30:24 AM Notification Type: Info Priority: Medium Description: Info 6C8F0428: Backup Exec System Recovery service stopped. Where Symantec appears to fail to back up, it is regarded as WARNING (Medium). (If a failure to execute a backup is ‘only’ a WARNING (Medium)… what then, for example, would rank higher and result in a WARNING (High) or an ERROR (either Medium or High)?) Date: 6/27/2017 10:49:42 AM Notification Type: Warning Priority: Medium Description: Error EC8F17E5: Your recovery point location of xxxx is running out of space. Please run the Cleanup Recovery Points task to free up some space. Error EBAB03F1: Not enough storage is available to complete this operation. Details: Not enough storage is available to complete this operation. The objective here is to try to better understand the levelling so only critical information is emailed out (and therefore avoid unnecessary notifications to users). Can you provide some assistance with this query? I can't find any documentation online that lists all error codes plus priority ratings. Please can someone assist us with this? Many thanks FergusSolved1.9KViews0likes2CommentsBESR 2010 Server No Mouse/KB on restore
I am using BESR 2010 Server to restore an image to a new Dell PE420 server. I boot using the restore media, but when it loads, I never get a mouse pointer and the keyboard does not respond. The mouse and keyboard respond fine in the BIOS and Lifecycle Controller, and are known to be good. I read that in some cases it can take a few hours for the PnP to pick up the USB devices, but I let this sit all night with no success. It seems to me that my BESR recovery disk just does not have the right drivers to make this work. Any ideas on how to get past this? Thanks! -Jim1.2KViews0likes4Comments