Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

New install, jobs hang

Updated: 21 May 2010 | 13 comments
Jamie Starkel's picture
0 0 Votes
Login to vote

I have a fresh new install of 11d. Only doing backup to disk. Any job I create will just hang as queued. The service account has full permissions to both the backup to disk location as well as the file it's backing up.

In the event log I get the following over and over:
An error occurred while processing a B2D command.
Changer: Couldn't ReadFMTables/RecoverBKF (E:\B2D_Full\B2D000017.bkf). Error=87

An error occurred while processing a B2D command.
Drive: ReadFMTable() SetFilePointer failed (E:\B2D_Full\B2D000017.bkf). Error=87

It will create two windows backup files in the backup to disk location, one being 2KB, the other 0KB.

Any ideas?

Comments

maxi maximus's picture
09
Nov
2006
0 Votes 0
Login to vote

Hi

Can you try creating a new backup to disk folder on another partition? Any difference?
What about Windows event logs? Application/System any indication about problems with disk? Also try NT backup just to rule out any software problem.


Hope this helps!!

Jamie Starkel's picture
09
Nov
2006
0 Votes 0
Login to vote

When I cancel a queued job I get the following in the job log:
Drive and media mount requested: 11/8/2006 2:09:35 PM
- Error - Mount failed.
Operation aborted

Update - So I tried creating a Backup-to-disk folder on the D drive of that server which is locall disk, as opposed to the E drive which is a SCSI attached storage. It is a SurfRaid SR-TRITON16SA storage array with 4.5 TB presented to this Windows Server. If I do a backup to the local disk it works fine, if I do one to the storage array it hangs with the previous errors. Is there any special drivers or tricks to getting it to work with our array?

STeve O's picture
09
Nov
2006
0 Votes 0
Login to vote

On the SurfRaid what if you craete a 200gig partition and try to run a backup to disk? I suspect you 4.5 TB is one volume and it may be a limitation. Or seperating into 2 2.2 TB volumes.

Jamie Starkel's picture
09
Nov
2006
0 Votes 0
Login to vote

My volume is currently a 4.1 TB drive in Windows so it very well could be a limitation issue. Windows has no problem writing to it though so I don't know why Backup Exec would have a problem. It can create the folder and it write the changer config files to it as well as creates the backup file as blank media, it just never writes to it. Is there any engineers from Symantec that can verify this?

Dave Riitano's picture
02
Dec
2006
0 Votes 0
Login to vote

Hello

I too am having similar issues.

I have a brand new 11d setup. I have an external Promise SAN of 4.5 terabytes

I also have a 1 terabyte array

I spent 2 hours with symantec tech support on the phone.

When I go to backup to the 4.5tb drive, it goes into que and a ton of :

Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:33808
Date:12/2/2006
Time:12:39:50 PM
User:N/A
Computer:ICH2
Description:
An error occurred while processing a B2D command.
Drive: WriteMasterFMTable() SetFilePointer failed (\\ich6.xxxxxxxx.org\belarge\1\@@@@@@@@.bkf). Error=6

are created on the BE server.

I am now trying to break the 4.5tb drive into 1.7tb drives.


Also when i backup up to the exisiting 1tb drive, I get pre processing and it never changes (waited 12 hours). Changing the advanced setting to clear auto detect made it work (though not always consistently)

I also on another server tried to backup to a 500g drive, and though it started to work, at 25gigs it failed with 'unknown' error'.

Backing up to tape, or a local folder on the BE server does work

Before 11d I had 9.1 and it worked with all the current drives fine.

So what is the deal?

Dave Riitano's picture
02
Dec
2006
0 Votes 0
Login to vote

I just changed the 4.5 terabyte SAN to 3 1.5tb drives. Had BE create the folder for B2D on one of the shares.

Took an exisiting job and tested it on the local drive it worked in 20 seconds.

Took the same job and sent it too the B2D folder and it imeadiatly went into queued status.

I checked the application log and wham... there are so many event '33808' events that i cant count them!

I purchased this product with several options last week, and will have to return it as simply this is not working with many SAN hardware choices.

My SAN is Promise VTrak 300.

Anyone get this too work yet???

Dave Riitano's picture
02
Dec
2006
0 Votes 0
Login to vote

One last thing.

I have used NTBackup and it works fine; what is sad, is now NTBackup seems like a better option.

Symantec; I have placed a request for a full refund to my vender, but if you can some how make this work in the next 48 hours, I will keep it.

People give shit to Microsoft for their products; It seems clear, from the night mare of licensing to getting tech support on the phone, and making this version work... 11d was months from ready to be released.

Dave
MCSE NT4, MCSE, 2000, MCSA 2003, A+

Dave Riitano's picture
02
Dec
2006
0 Votes 0
Login to vote

One last thing (or will it be). I had Symantec 9 Coorp Anti Virus, and because 11d will not work with this version (won't even boot according to the white papers!) I have purchased version 10.X. Was this an accident?! One Symantec product not compatable with another that is not even 2 years old... makes you wonder...

John Currie's picture
13
Dec
2006
0 Votes 0
Login to vote

I got this same issue! I have a 6.8TB drive and I have tried to repartition, recreate, reformat, reinstall and even upgraded to 11d from 10d and to no avail! Has anyone found the REAL answer to this?

Daryl Sensenig's picture
18
Dec
2006
0 Votes 0
Login to vote

I get this error as well. I cannot backup to any of my network drives. This is the error:

An error occurred while processing a B2D command.
Drive: WriteMasterFMTable() SetFilePointer failed (\\xxxxxxxx\Backup2\@@@@@@@@.bkf). Error=6

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLo...

No Thanks's picture
26
Dec
2006
0 Votes 0
Login to vote

Same error here, any help from Symantec?

Jeroen Buren's picture
15
May
2007
0 Votes 0
Login to vote

I have exactly the same problem. We use an Easyraid Q12+ with a capacity of almost 5 TB. However, I've found a workaround.
 
Create a share of the folder and instead of using the absolute path use the unc path. So in my case the B2D path was g:\backup and now \\ddb-data2\backup.
 
Maybe this could help Symantec to solve this once and for all.
 
Jeroen
great white north's picture
10
Oct
2007
0 Votes 0
Login to vote

I ran into this today. In the end, on the b2d properties configuration page I unselected auto detect settings and checked both read and write buffering. Seems this is a settting that should be documented better by Symantec.
I read the manual and knowledge base articles and there really is not any hint that this would be the setting to make the difference.