How to create a storage location on a nas in BackupExec 12.5?

From the Symantec Newsgroups on the issue of backup of NAS Appliances:

"Backup of mapped network drive is not supported with Backup Exec. Although, you can try adding the NAS server directly under selections through "user defined selections". Create a user defined selection by machine name or IP address of the target server and then try expanding it, provide the logon account credentials with permissions on the share on NAS being backed up. Please note that you will need a license for "Agent for Windows Systems" to backup a remote NAS server. Although, on the NAS box, no software needs to be installed, but a license would be required to backup a remote server."

Try this:

1) Make sure you can see the device in your "Network Neighborhood".  Since it has integraded AD Authentication, it should play well with your DC and be visible on the network under your domain.

2) Verify the Administrative credential required to administer the NAS and touch the data (at least read).  That credentail may be different than your domain admin.  If it is, enter it into your credential set under Backup Exec - Tools, Wizards, Logon Account wizard.

3) Start a new backup job and browse to the network place where the SAN is, and test the credentials under the backup job under the "Resource Credentials"..  You may have to muck with this a little to get it working, such as choosing and unchoosing the credential you want to use.

4) Test a small job using that credential to see if you can grab a few files off the NAS.  It wont be as fast as the remote agent...but it will work.

Thanks for the suggestion but my main problem is getting the storage location within the desktop laptop option from within backup exec 12.5 to recognize the nas as a storage location I dont want to backup the nas I want users to be able to backup to the nas and this is where I am having trouble do you know if this is possible?

Oh...Duh..went down the wrong track, sorry.

Did you try mapping a drive to the NAS from the Media Server and then designating that drive as the DLO storage location?

I tried that and it still doesn't show up as an option.

do you think because the nas device is unix based it may be a compatibility issue? If so do you know how I could change the os?

Here is one workaround:

Attach to the NAS as an ISCSI drive on your windows media server.  Then it will be considered local storage to Windows and the DLO destination picker should recognize it as such.  You may have to get a different NAS...Like an IOMEGA, because ISCSI isnt supported on the Black Armour 220.

Hello clcurri

I am also planning to implement this one using NAS as a storage in desktop and laptop option..let me know if you solve the problem and btw seen your post also on the symantec website

Regards, zeltrust

Hello Zeltrust,

I will definitely let you know, but it is very strange that this very basic type of function is either so complex to figure out or may not be compatible so I hope to get this resolved really soon.

would this help? http://buffalo.nas-central.org/index.php/Joining_Active_Directory

I followed the article and I tried to add this device as a storage location again from symantec and was unsuccessful, I also tried to install a remote agent on this system as well and I tried the iscsi route which I know was a long shot but I had no luck and I am running out of options, now I wish I had just bought an external drive which would have been more useful than this nas.

try this one.  http://seer.entsupport.symantec.com/docs/298956.htm

this looks promising but I have one hurdle to get this to work, the dlo agent asks for my username and password and all combinations of my username and password dont work, do you have any suggestions on what I can try?

If you went the ISCSI route, it would eliminate the problem, since the ISCSI allows you to "see the drive locally".

Hi I tried the ISCSI route but it doesn't look like my nas black armor 220 is compatible.

I also am stuck in limbo at the moment trying the move user route because there is an issue with the test users on the backup exec as they are stuck in a delete pending state and I'm trying to figure out how to get those users out of that state.

Also @chosmer if there is a workaround to getting iscsi to work please advise, thanks.

I was able to get the nas to be used as a storage location using this method but the seagate black armor 220's software is so slow it is almost unusable so I am now looking into ways to turn this nas into an external drive, thanks for helping me figure this out, you've been a really great help.

Renaming the NAS to a shorter name worked here!  Thank you zeltrust! I've been looking for this solution!