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

Error 0xe000fe3c (V-79-57344-65084) when backing up multiple iSCSI devices

Created: 27 Jan 2011 • Updated: 07 Mar 2011 | 10 comments
This issue has been solved. See solution.

Symantec BackupExec 2010 R2 Rev 4164 (32 bit)

on Windows Server 2003 R2

With Overland LTO-4 tape library.

 

We are getting the error 0xe000fe3c - Access to the device is not authorized with this edition of Backup Exec when backing up multiple (2) iSCSI devices (NTFS formated mapped as a local disk drive). If we backup each iSCSI device in a separate Job everything is fine.

The iSCSI devices are mapped to F: and G: every night and then backed up in 2 separate jobs. Our goal now is to backup both in 1 job.

Any suggestions why this error occurs?

 

Martin

Comments 10 CommentsJump to latest comment

itsmeaffinity's picture

Hi

 

How many LEO license you have got library expansion option

 

Thank You

If this information helps you, please mark it as solution.

Thank You.

RRE's picture

Hello Martin , 

 

 

Could you go open the affected job & go to resource credentials --- click test all & see the results

Also if possible , could you go to resource credentials & paste the screen shot here so that i can check what is selected. Also go to help ---- about ----- license information & paste the screen shot

 

 

Regards

RRE

________________________________________________________

If this answers your question, Please mark it as solution

Martin Baertl's picture

Thanks for the quick answer. Credential test passed without errors.

Screenshots: see attachments.

 

regards

Martin

SymBE-Lic.jpg Ressource-Cred.jpg
RRE's picture

Hi

 

Are you backing up local resources or remote resources. If you are backing up remote resources make sure you go to tools ---- install options & license keys & check remote agent for windows server license is installed.

 

 

If you are backing up local resources , then try to remove all the licenses & complete the installation . Try backups after that

 

Note - Installation media will be required 

________________________________________________________

If this answers your question, Please mark it as solution

Martin Baertl's picture

The 2 disks that are backed up are "local drives"  that are mapped via iSCSI connector on a remote iSCSI Server. Normaly those disks are treated as local and windows disk manager shows them as "local drive".

Those jobs that only back up 1 of those drives work normaly, without agent or anything. We installed this solution about 4 moth ago and everything is working fine until we try to backup both iSCSI disks in one job.

btw, we did not enter any other license but the "BackupExec 2010 Server" License key during setup.

RRE's picture

Just to isolate the issue.

 

Could you pls try to remove the license keys & then try to backup both the drives in 1 job & update the results

________________________________________________________

If this answers your question, Please mark it as solution

Martin Baertl's picture

Called Symantec support. They told me I have to add 1 License for Windows Remote Agent to Backup multiple iSCSI LUNs in 1 Job.

SOLUTION
RRE's picture

OK , then did you tried to backup both the drives in 1 job after adding that specific license key . If not did you tried to remove all the license keys & then tried to backup both the drives in 1 job ?

 

________________________________________________________

If this answers your question, Please mark it as solution

RRE's picture

Any update ?

________________________________________________________

If this answers your question, Please mark it as solution

Martin Baertl's picture

sorry it took so long.

It took over 2 weeks to get the additional licsense.

Jobs that Backup 2 iSCSI devices are running now. BUT i had to create new jobs. Old Jobs that i edited to Backup 2 instead of 1 drive, reported the same error. After deleting the old job and creating a new one that backs up both drives, everything is working fine.

All kind of backup jobs that we have ran once now, without error.