I will try to make this short: Brand new installadtion of BESR 8.5.1 on a 64-bit Windows 2008 Server (Standard); I'm using the BESR Manager to manage 13 Windows servers, with Windows 2008, 2000 and 2003 "clients. Here's the deal: I have new backups created once a week (Sunday) and recovery points created four times a day; once a day (I'll explain a little later), one of the jobs, on every Windows 2003 server, fails. The Windows 2000 and 2008 Servers always work, but the 2003 jobs will fail 25% of the time. There doesn't seem to be a pattern, a couple of days ago I was backing up at 8am, 11am, 1pm and 5pm; the 8am job would fail (five days in a row), but all the others would work, no problem. So, I removed the 8am job and guess what? Now the 11am job has failed (again, for all Windows 2003 servers) for two days in a row. I just installed BESR- this is not an upgrade for the management server or the clients. I've called Symantec support, didn't get much help. They've said to run checkdisk, defrag, which I have, but I still get this error. They say to stagger the jobs, which I haven't, because I don't see the point; these work 75% of the time and I've monitored the network traffic (this is all being done over a dedicated backup network, not an issue) and that's not the problem. Please help. Thanks!

I'm curious about a couple things. When you say the backup fails, does it always fail with the error you listed in the subject line? What type of backups are you making, file and folder backups, incremental recovery points, or full recovery points? What media are you backing up to? Would you agree that the pattern that appears to be emerging in your case is this:Server 2003 and first backup job of the day.

I have seen this error when there is corruption or install issue with the symsnapservice driver. Try and run the fixinstall.bat on the individual client servers, reboot the servers and allow backups to run

hello joseph, these are production servers and as i said, they're brand new/clean installs (not upgrades) on 8 different servers; it isn't possible for us to reboot these servers very often. i'm a little concerned that an enterprise dr solution may be suffering from "corruption or install issue" on a clean/new install across 8 servers... also, only the 2003 servers are experiencing this- not windows server 2008 or 2000. is there anything else you can suggest? thanks.

hello, - yes, it's always the same error (please see below).- i am creating recovery points 3x a day and a full once a week- backups are to disk (a windows share; the file and share permissions are fine)- yes, it does appear that it is the first backup of the day. i changed the ms shadow copy provider and volume shadow copy services to "automatic" from "manual" to see if that made a difference, but it didn't. vss admin list writers returns no errors. this is the email/notification i get (from this morning): Notification Type: ErrorPriority: HighDescription: Error EC8F17B7: Cannot create recovery points for job: System Drive (C:\) Backup @ RWC. Error EC8F03ED: Cannot create the recovery point. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Computer::CreateImageFile: .\Computer.cpp(1284): guid != Guid() && sequence != 0xffffffff. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. %1Details: 0xEBAB0013 it's always this same message. thank you in advance.

Are you including any utility partitions within the backup jobs? If so, attempt the backups without these utility partitions.

Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly.

21 Replies

aychekay
Level 5
16 years ago
I'm curious about a couple things.

When you say the backup fails, does it always fail with the error you listed in the subject line?

What type of backups are you making, file and folder backups, incremental recovery points, or full recovery points?

What media are you backing up to?

Would you agree that the pattern that appears to be emerging in your case is this:Server 2003 and first backup job of the day.
Joseph_L_
Level 5
16 years ago
I have seen this error when there is corruption or install issue with the symsnapservice driver. Try and run the fixinstall.bat on the individual client servers, reboot the servers and allow backups to run
vincentm
Level 3
16 years ago
hello joseph,

these are production servers and as i said, they're brand new/clean installs (not upgrades) on 8 different servers; it isn't possible for us to reboot these servers very often. i'm a little concerned that an enterprise dr solution may be suffering from "corruption or install issue" on a clean/new install across 8 servers... also, only the 2003 servers are experiencing this- not windows server 2008 or 2000. is there anything else you can suggest? thanks.
vincentm
Level 3
16 years ago
hello,

- yes, it's always the same error (please see below).
- i am creating recovery points 3x a day and a full once a week
- backups are to disk (a windows share; the file and share permissions are fine)
- yes, it does appear that it is the first backup of the day. i changed the ms shadow copy provider and volume shadow copy services to "automatic" from "manual" to see if that made a difference, but it didn't. vss admin list writers returns no errors.

this is the email/notification i get (from this morning):

Notification Type: Error
Priority: High
Description: Error EC8F17B7: Cannot create recovery points for job: System Drive (C:\) Backup @ RWC. Error EC8F03ED: Cannot create the recovery point. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Computer::CreateImageFile: .\Computer.cpp(1284): guid != Guid() && sequence != 0xffffffff. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. %1
Details: 0xEBAB0013

it's always this same message.

thank you in advance.
Joseph_L_
Level 5
16 years ago
Are you including any utility partitions within the backup jobs? If so, attempt the backups without these utility partitions.
vincentm
Level 3
16 years ago
utility partitions are not included in any of the backups.
vincentm
Level 3
16 years ago
any other suggestions here? i have an open case but we're not getting anywhere... thanks.
Jon_R
Level 6
16 years ago
What is your backup schedule? (eg; Monday 1 full, 3 incrementals, Tuesday 4 incrementals, etc.)
dvdb
Level 2
16 years ago
Same issue on HP Compaq nc6120 with Windows XP SP3. Only 1 disk with 1 C - partition (no utility or hidden partitions)
Symantec Backup Exec System recovery 8.5.1.29666 - First installation
==================================================

- First backup for "Recovery Point Set".
Start with "Creating recovery point" - Initializing
After 20 sec - Drive backup starts 0%
Immediately Error
Cannot create the recovery point.
--Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Computer::CreateImageFile: .\Computer.cpp(1284): guid != Guid() && sequence != 0xffffffff.

Reboots, System Updates, Repair of System Recovery --> same problem

- Backup "Independent recovery point"
Start with "Creating recovery point" - Initializing
Creating new image file
---------------------------
Drive Backup of (C:\) (2)
---------------------------
This operation cannot be performed while Windows is running.
You must complete this operation inside the recovery environment.
Would you like to continue?
---------------------------
Yes No
---------------------------
Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\) (2). Error E0BB001B: Cannot lock volume C:\ because it contains the OS or has an active paging file. Error EBAB03F1: The volume contains system or paging files.
Details:
Source: Backup Exec System Recovery

No idea what can cause this problem, but seems to be similar like the one on the servers in this thread.
Joseph_L_
Level 5
16 years ago
Please see the following technotes:

http://support.veritas.com/docs/301176
http://support.veritas.com/docs/304128