Getting an 'Access Denied' error when trying to create backup job for Backup Exec 10D

I guess the easy answer to my question is 'Something doesn't have the correct permissions'. =P. I read Backup Exec b2d NAS, but that didn't really answer my question.

I have poked around the Admin guide and google trying to nut this out, but I'm not really getting anywhere very fast and I am loath to call Symantec support if I can avoid it.

The basic setup:

Cisco NSS324

Windows Server 2003 - SP2

Symantec Backup Exec 10D

I want to create a B2D job to the NAS, and have used the UNC path \\<NAS DEVICE NAME>\<TOP LEVEL SHARE>\<BACKUP FOLDER>\. However as soon as I hit 'OK' an "Access is Denied" error pops up.

The NAS has properly joined the network domain and I have given the 'veritas' AD user full read/write access to my NAS share via the Cisco Web Interface and added the 'veritas' user to the AD 'Backup Operators' group (though this group does not appear in the Web Interface as a domain group I can give access to, leading me to suspect this step might be moot) and the funny thing is I can actually browse to the folder within BE10D!

I'm obviously missing something pretty basic here,

I'm just not sure what. Can anyone give me a pointer?

Cheers,

Update:

Ah, damn it. I realised after posting yesterday that I had connected to a local drive (Got B:\ somehow confused with Z:\), not the NAS. Therefore I am a giant dumbass and have not solved this yet.

I am still getting an "Access Denied" message when using the UNC path, after adding permissions for the 'veritas' user on the NAS Share, the folder I am backing up and adding the user to the "Backup Operators" group.

I have tried mapping the IT_Admin share on the NAS to Z:\ and used the path Z:\Backup\ which gives an error saying "The system cannot find the path specified". If I add "\\" in front of the drive letter the error changes to "The network path was not found". I’m pretty sure using the mapped path wouldn’t work anyway from I read over at http://www.symantec.com/connect/forums/bacup-network-drive-backup-exec-10d.

The device name is "NSS324", the top level share I created is "IT_Admin", I have created a folder at the root of the share called "Backup". I feel pretty confident the UNC path of \\NSS324\IT_Admin\Backup\ is correct. Could someone higher level possbily be able to confirm?

I don't want sound like I am asking to be spoon fed, but really not sure what else I can give the user permissions to, in order to get this to work. Anyone feel like throwing in their 2c?

Try logging onto a computer as your Veritas user and confirm you are in fact able to browse to the data you're trying to back up, and try copying something from the network share to the computer. Also check you can browse to the NAS share and create files on that.

On your Backup Exec Media Server, try and browse to the root of \\NSS324. I don't know about this particular NAS, but if it's a Linux based NAS, I have seen those sometimes either not register themselves in DNS properly (or at all) or they don't consistently answer to their assigned name. If that doesn't work, you might want to try a fully qualified name (i.e \\NSS324.corp.acme-widgets.com (obviously replace that with your actual FQDN)).

In your B2D media, there is no need to map the share on the NAS to a Windows drive letter - Backup Exec will be perfectly happy with simply \\NSS324\IT_Admin\Backup.

I've experienced some idiocy from the Backup Exec interface before, where it claimed the user I has specified as the backup user didn't have enough permission (when it really did). If I ran the job manually, it backed up everything and the job completed successfully (confirmed with a restore).

I've also found any errors in the Backup Exec job log are more useful than the error messages you get when setting up a job. It might be worth setting up the job and ignoring any permission errors you get and run it anyway so you can interrogate the job log. Any errors or warnings in the job log generally point to a Symantec KB article, which admittedly isn't always helpful, but might prompt you to think about something you maybe overlooked.

GAH! I didn't give the 'veritas' user proper permissions to access the folder I wanted to backup via explorer.exe...

Facepalm.jpg

Sorry for wasting everyone's time!! >.<

EDIT

Intrestingly, I still wasn't able to use the UNC path to get this to work (possible that I have not entered the path correctly). I have mapped the share as B:\ on the WinServer, and after giving the veritas user proper permissions to access this, I created a "Backup" folder at the root level of the share and browsed to it via BE10D, clicked ok and everything was sweet. Still haven't tried actually doing a backup/restore to/from this folder yet, will update if anything goes awry.

EDIT # 2

Finally figured this one out (though I kinda cheated as I had some external help from someone helping us set up a BES yesterday).

I had the NAS Share mapped by is IP on my Win Server (\x.x.x.x\Share Name\Backup) and used my admin AD credentials to login to the share. We disconnected this drive and remapped it using its UNC path. The only way to logon to the share now was to use the admin login for the NAS, so when the windows auth window popped up for my access to the share I used "device name\admin" and its associated password.

I was now logged into the share via its UNC path in Windows. Reopened BE10D and reattempted to create a B2D to the NAS share it worked like a charm! No access denied errors or anything!

I’ve done a backup and restore to the NAS Share, both of which worked and this question is now solved. Yay! :D Thanks again to everyone for your help!