Forum Discussion
dale_m1
15 years agoLevel 4
Hello,
I am wondering if any of the posters in this thread ever found a resolution to this problem?
I have exactly the same error as the original poster.
In my case the server is running Win Server 2003 R2 SP2, BESR 2010 SP1. A fresh local install (no management server) was done this past weekend at which time the first baseline backup was done. Incrementals are scheduled for M,T,W,H,F evenings. The Monday incremental happened. The Tuesday incremental failed.
There is no other backup software on this server.
Below are the log file contents that Chris Riley had requested from other posters in this thread. The log file shows the initial install on the 17th, the first incremental on the 19th, and the failed incremental on the 20th. When I logged onto the system this morning, the 21st, it prompted me via the blue pop-up as to whether I wanted to run missed backups. I said yes. It then gave me the missed backup grid which showed the one missed backup. I ran this and the missed backup ran successfully. Still, this kind of manual intervention defeats the purpose of a backup schedule.
Thank You.
4/17/2010 16:03:25 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:10:22 PM Medium Priority Info: Info 6C8F0428: Backup Exec System Recovery service stopped. 0x00 (Backup Exec System Recovery)
4/17/2010 16:16:21 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:16:40 PM Medium Priority Info: Info 6C8F0428: Backup Exec System Recovery service stopped. 0x00 (Backup Exec System Recovery)
4/17/2010 16:20:48 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:36:30 PM High Priority Info: Info 6C8F1F63: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started manually. 0x00 (Backup Exec System Recovery)
4/17/2010 20:25:49 PM High Priority Info: Info 6C8F1F79: A manual base recovery point of drive D:\ was created successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 20:25:49 PM High Priority Info: Info 6C8F1F79: A manual base recovery point of drive C:\ was created successfully. 0x00 (Backup Exec System Recovery)
4/19/2010 21:00:10 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started automatically. 0x00 (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Info: Info 6C8F1F7E: A scheduled incremental recovery point of drive D:\ was created successfully.
Error E4BD0012: Error E4BD0012: 0x00 (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Info: Info 6C8F1F7E: A scheduled incremental recovery point of drive C:\ was created successfully.
0x00 (Backup Exec System Recovery)
4/20/2010 21:00:21 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started automatically. 0x00 (Backup Exec System Recovery)
4/20/2010 21:10:24 PM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), Data Volume (D:\).
Error E0BB0083: Unable to create incremental recovery point.
Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, BitmapInternal::RunListBase<unsigned long>::RunListBase: d:\ComponentReleases\Base_Main\ws\Base/Dev/Bitmap/RunListBase.inl(158): mRunListCount < maxRuns. 0xE0BB0083 (Backup Exec System Recovery)
(UMI:V-281-3215-6071)
I am wondering if any of the posters in this thread ever found a resolution to this problem?
I have exactly the same error as the original poster.
In my case the server is running Win Server 2003 R2 SP2, BESR 2010 SP1. A fresh local install (no management server) was done this past weekend at which time the first baseline backup was done. Incrementals are scheduled for M,T,W,H,F evenings. The Monday incremental happened. The Tuesday incremental failed.
There is no other backup software on this server.
Below are the log file contents that Chris Riley had requested from other posters in this thread. The log file shows the initial install on the 17th, the first incremental on the 19th, and the failed incremental on the 20th. When I logged onto the system this morning, the 21st, it prompted me via the blue pop-up as to whether I wanted to run missed backups. I said yes. It then gave me the missed backup grid which showed the one missed backup. I ran this and the missed backup ran successfully. Still, this kind of manual intervention defeats the purpose of a backup schedule.
Thank You.
4/17/2010 16:03:25 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:10:22 PM Medium Priority Info: Info 6C8F0428: Backup Exec System Recovery service stopped. 0x00 (Backup Exec System Recovery)
4/17/2010 16:16:21 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:16:40 PM Medium Priority Info: Info 6C8F0428: Backup Exec System Recovery service stopped. 0x00 (Backup Exec System Recovery)
4/17/2010 16:20:48 PM Medium Priority Info: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 16:36:30 PM High Priority Info: Info 6C8F1F63: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started manually. 0x00 (Backup Exec System Recovery)
4/17/2010 20:25:49 PM High Priority Info: Info 6C8F1F79: A manual base recovery point of drive D:\ was created successfully. 0x00 (Backup Exec System Recovery)
4/17/2010 20:25:49 PM High Priority Info: Info 6C8F1F79: A manual base recovery point of drive C:\ was created successfully. 0x00 (Backup Exec System Recovery)
4/19/2010 21:00:10 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started automatically. 0x00 (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Info: Info 6C8F1F7E: A scheduled incremental recovery point of drive D:\ was created successfully.
Error E4BD0012: Error E4BD0012: 0x00 (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Warning: 0x800706BA (Backup Exec System Recovery)
4/19/2010 21:17:15 PM High Priority Info: Info 6C8F1F7E: A scheduled incremental recovery point of drive C:\ was created successfully.
0x00 (Backup Exec System Recovery)
4/20/2010 21:00:21 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of (C:\), Data Volume (D:\), has been started automatically. 0x00 (Backup Exec System Recovery)
4/20/2010 21:10:24 PM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), Data Volume (D:\).
Error E0BB0083: Unable to create incremental recovery point.
Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, BitmapInternal::RunListBase<unsigned long>::RunListBase: d:\ComponentReleases\Base_Main\ws\Base/Dev/Bitmap/RunListBase.inl(158): mRunListCount < maxRuns. 0xE0BB0083 (Backup Exec System Recovery)
(UMI:V-281-3215-6071)
Related Content
- 11 years ago
- 12 years ago