NSS6000 will not work with Symantec Backup Exec for Windows Servers

[cubmanky]

Anyone have a clew how I can get Symantec Backup Exec for Windows Servers to talk to my NSS6000 to do a backup?

[TerribleByte]

I've been trying to do the same ; no luck. In theory, you can enable CIFS/SMB on the NSS6000 and use a UNC path to access the data. So far so good, but when Backup Exec tries to connect to this path as a data source for a new backup job it'll warn you that it's not allowed. Likewise, if you set it up as a 'custom' data source. It seems that there's an inbuilt limitation, probably because they want you to buy 'remote agent' licenses. However, because the NSS6000 NAS uses an embedded Linux Kernel, a remote agent can't be installed. It's possible that installing the agent license will 'open up' the restriction for UNC paths. ... Linksys will tell you they can't offer support on this (and I can't really argue with that). I've pursued Symantec, but their support is comical at best. They offer little feedback through the forums, are virtually impossible to contact by phone and when you do get through, they won't have a clue what you're asking. I was promised a call back from someone who could help ; he called and didn't understand the problem, when I explained he said he'd have to research it and would call or email me back. That was over three weeks ago and I've not heard anything. I you do come up with a solution, please share it with us.

[kck54]

Use backup-to-disk-folder, thats what I did but not for NSS6000

[Joe-GadellNet]

I would like to figure this out too.  I just assumed this would work unfortunately.  I get an error stating the agent cannot be found. 

I am trying to run tape backups of the data on the NSS 6100 - not trying to backup to the NSS 6100 as a backup-to-disk.

Thanks,

Joe

[TerribleByte]

Hi Joe.


Good point....
I may have misunderstood the original post (slightly ambiguous).

I'd also like to backup the data on my NAS (as per my original post).
Maybe you'll have more luck than I on the Symantec Forum ; the more customers that raise the issue we stand a better chance of Symantec looking into this issue.

As far as I can see, the problem will occur with ANY UNC path on a different server, not just the NAS.
The problem is that in that scenario they'll tell you to buy a remote agent license, which we can't install. But if I recall correctly, I read that you don't always need to actually install the agent, just having the license is sometimes enough (I think the agent marshalls the data transfer when a UNC path isn't available).

If only I could actually talk to someone at Symantec who knew Backup Exec inside out...

NB - I'll probably get a credit on my NSS6100 and buy a Netgear ReadyNAS instead ; it's just died with a RED LED problem.
Linksys report it's a known issue with no current fix affecting multiple customers. Sounds like a firmware compat issue with the hardware (they suggested leaving it unplugged overnight to let the capacitors discharge !!!!!!).

Dave.

---

Joe-GadellNet wrote:

I would like to figure this out too. I just assumed this would work unfortunately. I get an error stating the agent cannot be found.

I am trying to run tape backups of the data on the NSS 6100 - not trying to backup to the NSS 6100 as a backup-to-disk.

Thanks,

Joe

---

[Joe-GadellNet]

That sounds like a possibility.  If we could verify that this is a licensing issue, I would happily request that my customer buy the lastest version of Backup Exec and one additional license to backup the NSS6100.

If anyone knows anything, please chime in.  We are a Symantec partner - I will call them tomorrow and discuss.

Thanks,

Joe

[cubmanky]

any new news???????

[zolazar]

I have had a NAS6000 working beautifully with BackupExec for about a month now. I first configured the NAS to connect to 2003AD and created a share and gave my backup user full access to. Then went into BackupExec and created a Backup-To-Disk connection using the UNC path \\NAS6000\Backups . Worked perfect... well until the red light of death hit me. I did have a problem with BackupExec keep thinking it was offline but I realized it was me making changes to the NAS. Once I got it set the way I wanted it stopped. Been working great ever since...

[TerribleByte]

Hi Zolazar,

Thanks for the feedback, but we're talking about backing the data on the NAS up to tape, not using the NAS for backup storage instead of a tape.

Nice to have the NAS back online after the RED LED problem, shame I had to find out about the fix myself instead of being told about it by Linksys (I did after all have an active RMA).

TB

---

zolazar wrote:

I have had a NAS6000 working beautifully with BackupExec for about a month now. I first configured the NAS to connect to 2003AD and created a share and gave my backup user full access to. Then went into BackupExec and created a Backup-To-Disk connection using the UNC path \\NAS6000\Backups . Worked perfect... well until the red light of death hit me. I did have a problem with BackupExec keep thinking it was offline but I realized it was me making changes to the NAS. Once I got it set the way I wanted it stopped. Been working great ever since...

---

[JOHNDOE_06]

Hi Guys!
For both the NSS4000 and NSS6000, you may find this Knowledge Base Article appropriate for your inquiry:

CLICK THIS: SETTING UP SYMANTEC BACKUP EXEC FOR NSS4000 and NSS6000

URL: http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=15593

Thanks!