0xe00846b Error When Going from 2010 to 2012

[zubeb]

I just upgraded to BE 2012.  Now, backup jobs for remote NAS resources that I used to back up to without any problem fail with the 0xe00846b error.  I have looked at several articles but cannot find a valid solution.

[AmolB]

Could you post entire error message from the job lob.

[CraigV]

Hi,

Those B2Ds might be seen as legacy B2Ds...check the TNs below to see if they apply to you:

http://www.symantec.com/business/support/index?page=content&id=HOWTO74274

http://www.symantec.com/business/support/index?page=content&id=HOWTO74137

Thanks!

[zubeb]

I have the ability to simply delete the B2D's and create new ones.  Is that likely the easiest route?  I have the data backed up in other places too, which would allow me to do that.

[VJware]

You mentioned ' 0xe00846b ' , but i guess you were meaning to type 0xe000846b (an extra 0)

this error message can be usually ignored when backing up NAS boxes, as they cannot have a remote agent installed...

verify if the data was actually backed up or not & prolly attempt a test restore..if successful, this msg can be ignored...

[zubeb]

Yes, you are correct.  However, the job actually fails (not just a notation of an error).  Any way to let the system know that it's a NAS and can't have an agent?

[CraigV]

...if you can do so, you're starting with something new...

[VJware]

Is the NAS part of AD ? If yes, when this NAS is added by the to BE 2012, authentication happens via AD as the NAS would appear as a windows share, and then BE looks for the remote agent & since there is no remote agent, you would see this error...(again, check if the data was backed up or not before job failure)...

create & use a root account instead for the this backup job..

[AmolB]

Refer to  http://www.symantec.com/docs/TECH17377