Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

trying to address a B2D job issue...

Created: 12 Aug 2013 • Updated: 21 Aug 2013 | 12 comments
This issue has been solved. See solution.

i have a new NAS powervault NX400 (raid 5) that i am trying to configure B2D jobs using BE2010 SP3 off a windows 2003 SBS server.

there is a server upgrade coming (as well as i have the ability to upgrade to BE2012 if needed) and have an existing backup solution in place, but am trying to figure out why my B2D jobs fail shortly after getting started.

I know not to use large B2D files and i have also been able to successfully run B2D jobs to a USB drive when i have had to, but every time i try a b2d job to the NAS device, it fails.

i get "Error Code E00084F4 – an unknown error has occurred…the specified network name is no longer available…For additional information regarding this error refer to link V-79-57344-34036"

In the event logs on the server i get

An error occurred while processing a B2D command.

Drive: InitWrite() CreateFile failed (\\tuttle-nas\nightly backups\test1\B2D000347.bkf). Error=64

I have tried just about everything from un-teaming the network adapters on the NAS device, making speed changes on the switch, changed the write policy on the raid controller...i don't have an A/V program running yet on the NAS device since it's not in production yet. I am using UNC Paths instead of a drive letter...The only thing i haven't done is gone back into the RAID setup and changed the stripe size as i read somewhere...

The odd thing is i have a similar setup (SBS 2011 with BE2010 to an NX200 (only difference is it's raid 1)) set up somewhere else...and i didn't have nearly the types of issues getting B2D jobs going.

I even tried doing a B2D job with a 100GB max file size...but that job died before it could complete.

I am running out of ideas here...i can't imagine someone else hasn't run across this before...

Operating Systems:

Comments 12 CommentsJump to latest comment

Kunal.Mudliyar's picture

B2D do have has some issues with RAID 5

http://www.symantec.com/docs/TECH164267

 

Also try disabling disk write caching

http://support.microsoft.com/kb/259716

Try a backup with a 10 GB Bkf file size instead of 100 GB

Technical Support

Symantec

tothehoop's picture

Thanks Kunal...

been through the TECH164267...already doing most of the best practices.

i have tried with the standard 4GB BKF file size...that doesn't work either...tried it with or without compression...no dice...

as far as the disk write caching...since the drives are on a raid controller, i would presume that's why i can't disable them within the OS

Kunal.Mudliyar's picture

How about testing with RAID 1?

Technical Support

Symantec

CraigV's picture

Hi,

 

That PV NX400 runs Windows Server 2012 which has built-in iSCSI. Have you tried to carve out an iSCSI LUN and present to your BE media server?

If not, try this, and run B2Dtest.exe to ensure that the B2D is supported. The PV NX400 isn't on the BE 2010 or 2012 HCL, but iSCSI might still work. this would get around any authentication issues or unavailable shares for instance as the LUN is presented persistently to the media server.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

tothehoop's picture

HI Craig...

mine is actually running Storage Server 2008 R2...

Not sure what you mean about "carving out an iSCSI LUN and present to my BE media server?"

i've run the b2dtest....i got some errors (would have to go re-run it to get specifics)...but it appeared to be supported from what i remembered.

CraigV's picture

...OK, for Windows Server 2008 R2 you need to check out the links below:

http://www.youtube.com/watch?v=eU_dXr3dmf8

http://blogs.technet.com/b/filecab/archive/2010/09/27/windows-storage-server-2008-r2-and-the-microsoft-iscsi-software-target-3-3-are-available-on-msdn-technet-here-s-how-to-install-them.aspx

Carve out = create a LUN, and then you create an initiator to this LUN from your media server. This will present the LUN from the NX400 to the media server and pop up in Storage Manager. Format the drive, and then run B2Dtest.exe to verify support.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

SOLUTION
tothehoop's picture

Craig...thanks for the help!

i did get it up and running last night...still having some speed issues though..i had my switch set to 100Mb/half (teamed NICs) and it was all running fine but very slowly...

switching it back to GB connectivity (first teamed, then using one as a failover adapter on the NAS) seemed to set me back though...so still trying to troubleshoot.

thanks to everyone for the assistance so far...

CraigV's picture

Cool...have you checked if you can enable jumbo frames on the NAS and on your server NICs? If you have an AV installed, turn it off and see what the speed difference is.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

tothehoop's picture

thanks Craig...

i long removed AV from my NAS device.  Unfortunately my "slow tests" still weren't running fine.  I should probably run the B2Dtest jobs and post the resuts.

CraigV's picture

...sorry, meant the AV on the backup server.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

tothehoop's picture

I want to thank everyone for their help so far...

the ISCSI set up was a great find! i currenlty have an SBS 2003 box which is about to get upgraded, but went ahead and tried it out so i would know what i was up against after the migration.

been having issues still mapping to UNC shares, but the light bulb went on...it's a drive letter :)

Once i did that, things started working...i ran the b2dtest file program against the drive and it came back clean.

Craig...i can't disable AV on the backup server...but i did try with on-access off (worked) and put it back on (worked)

I also have a powerconnect 2824 switch so couldn't do much with jumbo frames there from what i could see, but reset the NICs on the NAS to 8000.

still have a couple of floating questions:

my original plan was the drive to be one giant drive for backups...currently i have most all of it as a VHD file.  is that bad? (or is it ok as long as i take regular snapshots?) i don't know for sure what my new backup strategy will be so i don't know how much i can cut off this drive if like a 1.6TB vhd file is a bad idea.

Teamed NICs on the NAS box? reccomend against?  i currently have the team broken(and one nic disabled)...and i am moving data to the NAS fine...but would it help performance? (i can't see any concrete evidence on way or the other about it)

thanks for all the help everyone

 

CraigV's picture

Hi,

 

I ran teamed NICs on the Iomega NAS arrays and never had bad performance. That said, it was another backup software writing to the device. However, BE would backup from the iSCSI LUN and we got very good speeds.

Team the NICs again and see what performance you get out of it. See if you can configure it for throughput...ie. 2GB instead of 1GB only in a failover configuration.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...