07-20-2010 05:02 PM
07-20-2010 07:43 PM
11-16-2010 08:30 AM
Need Some Help:
I have added the registry keys and double checked their accuracy.
I have unselected System State from the job then submitted changes. I then reselected System State and submitted the changes. However, I am still getting the same error message.
VSS Snapshot warning. File %BeBootDrive%\bootmgr is not present on the snapshot.
Backup Exec 2010 fully updated and running on Server 2003.
I have followed these steps
Workaround:
Exclude the ASR writer from the list of approved writers
11-16-2010 08:59 PM
Are you using a domain admin account to do the backup? If not, can you try it?
11-26-2010 07:44 AM
I too have the same issue, tried the solution posted above and still get same warning message.
I am using Backup Exec 12.5 SP4 on Windows server 2008 64BIT Std.
Planning to uninstall backup exec and do a clean install again.
11-30-2010 11:04 AM
I have also been having the same issue. I'm running BE2010 R2. The jobs are all configured to use a Domain Admin account (double checked after reading the post) and i've tried the registry key. Is there any other way besides uninstalling/reinstalling Backup Exec or just excluding the system state?
12-06-2010 07:42 AM
After removing Backup Exec 12.5 and re-installing the problem is still there.
I have done the suggested steps above again bu the end result is the same.
Any update on this issue please?
02-02-2011 06:41 AM
The solution worked for me under Backup Exec 2010 R2 (running on a server that has uEFI), but the registry key has changed in R2 to:
HKLM\SOFTWARE\Symantec\Backup Exec for Windows\Backup Exec\Engine\Shadow Copy Components\
(This is not a remote agent, this exception was occurring on the backup server itself.)
03-11-2011 07:56 AM
We are receiving the same messages.
Tried the registry change but began to have backups fail all together.
Backup begins but hangs at different locations.
Debug shows the following repeated over and over:
BKUPEXEC: [03/07/11 17:10:32] [0033] [Info] VSN received: type = ACTJOBEX_UPDATE
BKUPEXEC: [03/07/11 17:10:32] [0033] [Debug] VSN is a MODIFY
08-01-2011 10:39 AM
11-14-2011 04:40 AM
This article (TECH126412) does not solve the problem. Backup Exec 2010R3, Windows 2008 Server, IBM x3650M3.
When I try to run full backup server, I still get the message:
"VSS Snapshot warning. File %BeBootDrive%\bootmgr is not present on the snapshot."
After that *.dr file is not created.
Regards
JacekD
11-14-2011 06:04 AM
If using Windows 2008 you should have the 100MB utility partition in your disk management which does not have any drive letter assigned.
As concequence it cannot be included in the VSS snapshots and this is why you see this error. Simply assign a drive letter to this partition and try again
12-13-2011 10:55 PM
Hello,
I have the same issue with Backup Exec 2010 R3 under Small Business Server 2011 (Server 2008 R2).
Simon B. can you tell me how i can assign a drive letter to the hidden partition (100MB)? When i run the diskmgmt.msc i see the hidden partition with 100MB, but with the right button of the mouse i can not assign any drive letter to this preserved hidden partition.
I have stpend a lot of time with this issue, but Backup Exec always says File %BeBootDrive%\bootmgr is not present on the snapshot.
Thanks for your answer.
SBK
12-14-2011 12:37 AM
I was under the impression that you simply can assign the drive letter in disk management, at least in server 2008(r2), maybe the behavior was changed in SBS.
You should however be able to assign the drive letter via diskpart:
diskpart list disk select disk # list partition select partition # assign letter=X
12-19-2011 12:28 AM
Hi Simon,
Thank you for the fast answer, with diskpart assign a drive letter was very easy thanks!
But the problem with the bootmgr still persist :(
Thanks SBK
12-29-2011 01:50 PM
Tried the ASR registry fix. Deleting the System State from the backup job and respecifying it. Still get the same error. Backing up a IBM x3650 M3. Running Backup Exec 2010 SP1 on the backup server. I'd say this issue warrants a hotfix.