Seagate NAS Connection Problem



  • We have a cheap (but functional) Seagate Blackarmor 440 NAS we use for backups. I am in the middle of demoing some backup software and have about settled on VEEAM and our current solution (just for SQL. and a few physical servers needs).

    I decided to rebuild my NAS since it takes days to delete data off of it. And rebuilt it with RAID10. This NAS does allow for some active directory integration on permissions to the shares and those are set as before.

    On the backup server, I go out to the path to the share \backupnas\share and I can create files and folders and delete them.

    In VEEAM, I set up the new NAS volume in the drive repository, set up the permission (login) to the NAS, it detects it and even shows the free space. All is good there. When I run the backup, I get...

    4/17/2014 4:51:34 PM :: Processing 'pinnacle' Error: Client error: The network path was not found. .
    Agent failed to process method {Stg.OpenReadWrite}.

    On our other backup suite, BackupAssist, that I use for SQL, same thing...it knows the NAS is there, heck, it is even mapped as a drive on the backup server...it gets:

    BA1505 Cannot open the specified destination directory from the server - it may not exist or the SQL server may not have the correct authorisation
    Cannot open backup device '\backupNAS\SQLBackup\SQLINSTANCE-Contracts-20140418.072841.445-FULL.bak'. Operating system error 50(The request is not supported.).
    BACKUP DATABASE is terminating abnormally.

    The NAS setup didn't change...still CFIS and NFS...but for some reason, after recreating the volume, I am having these issues...I did go from RAID5 to RAID10 but really doubt that matters...

    Any ideas?



  • RAID levels definitely have no effect there. This is definitely an issue at a higher level.



  • To put double backslashes in a post, use triple. It treats the first as an escape character. \\server\folder



  • @scottalanmiller said:

    RAID levels definitely have no effect there. This is definitely an issue at a higher level.

    Yeah...this is so frustrating...nothing changed but making a new volume, shares and assigning the same permissions back...maybe I am finally seeking the "sucky" side of these NAS units (which up to know, haven't been as bad as some have reported.)



  • No need to share NFS since you are using SMB.



  • Have you tried just opening the SMB share wide open.... "Read/Write to Everyone" ?



  • @scottalanmiller said:

    Have you tried just opening the SMB share wide open.... "Read/Write to Everyone" ?

    Yes...it was FULL access but still had permissions to limit some access...

    I am starting over with the volume...one more time...step by step...will remain at RAID10 though...



  • Open it completely for testing. Once that is working, lock it down.



  • Here's what I've done

    Created the RAID10 Volume (took about 5-6 minutes to format)
    Created a single share with FULL NFS access...tried to view it in windows explorer and got this:

    nfs01.jpg

    So, there was another option for public access, with along with FULL NFS access selected, takes away the AD options...selected that...BAM...I can get to the folder in Windows Explorer...Started the SQL backup from BackupAssist...BAM...it works...so FULL NFS and Public access makes it work...

    Waiting on the SQL to finish before trying VEEAM but it sounds like it will work now...I can slowly add some AD back into it...while it is always good to have security, backups are not one I am too worried about as no one here would have the time or knowledge to poke around in that drive...



  • @garak0410 said:

    Created a single share with FULL NFS access...tried to view it in windows explorer and got this:

    No, NFS is what you should turn off completely. There is no need for it. Use SMB only and open that all the way up. Windows can't natively talk to NFS.



  • OK something is really fishy if he disabled SMB and only has NFS running, yet he's able to backup to the device (assuming he hasn't installed a NFS driver in Windows).



  • @Dashrender said:

    OK something is really fishy if he disabled SMB and only has NFS running, yet he's able to backup to the device (assuming he hasn't installed a NFS driver in Windows).

    Yeah, that is weird. The software must have its own NFS stack that it is using or installed SFU silently and doesn't tell him. Very odd. But hey, NFS is easier to deal with so... good deal.



  • @scottalanmiller said:

    @Dashrender said:

    OK something is really fishy if he disabled SMB and only has NFS running, yet he's able to backup to the device (assuming he hasn't installed a NFS driver in Windows).

    Yeah, that is weird. The software must have its own NFS stack that it is using or installed SFU silently and doesn't tell him. Very odd. But hey, NFS is easier to deal with so... good deal.

    Well, regardless, it is working for the SQL backup....writing fine...I set up a new Backup Repository in VEEAM to the share with Full Access and Public access and it still fails with THE NETWORK PATH WAS NOT FOUND...baffling...



  • @garak0410 said:

    @scottalanmiller said:

    @Dashrender said:

    OK something is really fishy if he disabled SMB and only has NFS running, yet he's able to backup to the device (assuming he hasn't installed a NFS driver in Windows).

    Yeah, that is weird. The software must have its own NFS stack that it is using or installed SFU silently and doesn't tell him. Very odd. But hey, NFS is easier to deal with so... good deal.

    Well, regardless, it is working for the SQL backup....writing fine...I set up a new Backup Repository in VEEAM to the share with Full Access and Public access and it still fails with THE NETWORK PATH WAS NOT FOUND...baffling...

    Well, that kinda gives credibility to Scott's theory that your backup software for SQL is using it's own NFS driver.

    Time to try Scott's earlier suggestion, enable SMB and open it up fully - everyone full control. no other permissions set.



  • @Dashrender said:

    @garak0410 said:

    @scottalanmiller said:

    @Dashrender said:

    OK something is really fishy if he disabled SMB and only has NFS running, yet he's able to backup to the device (assuming he hasn't installed a NFS driver in Windows).

    Yeah, that is weird. The software must have its own NFS stack that it is using or installed SFU silently and doesn't tell him. Very odd. But hey, NFS is easier to deal with so... good deal.

    Well, regardless, it is working for the SQL backup....writing fine...I set up a new Backup Repository in VEEAM to the share with Full Access and Public access and it still fails with THE NETWORK PATH WAS NOT FOUND...baffling...

    Well, that kinda gives credibility to Scott's theory that your backup software for SQL is using it's own NFS driver.

    Time to try Scott's earlier suggestion, enable SMB and open it up fully - everyone full control. no other permissions set.

    Sorry...enable SMB on what device? If the NAS, there is no option for that...



  • The NAS doesn't support SMB? Something is wrong. That's 95% of its use cases.



  • Maybe the NAS uses the old name for SMB.... CIFS?



  • @scottalanmiller said:

    The NAS doesn't support SMB? Something is wrong. That's 95% of its use cases.

    I know...as mentioned, this all worked great before I rebuilt the volume. Seagate support has suggested factory reset...of course they did... 😞



  • @garak0410 said:

    @scottalanmiller said:

    The NAS doesn't support SMB? Something is wrong. That's 95% of its use cases.

    I know...as mentioned, this all worked great before I rebuilt the volume. Seagate support has suggested factory reset...of course they did... 😞

    If you rebuilt the array, what's wrong with a factory reset?



  • @Dashrender said:

    @garak0410 said:

    @scottalanmiller said:

    The NAS doesn't support SMB? Something is wrong. That's 95% of its use cases.

    I know...as mentioned, this all worked great before I rebuilt the volume. Seagate support has suggested factory reset...of course they did... 😞

    If you rebuilt the array, what's wrong with a factory reset?

    Nothing...just more work (I've got a ton on my plate today)...LOL...about to go attempt it...



  • Real Quick...I did see this setting:

    NFS Service ON or OFF...it was set to OFF. If I set to on, it asks for allowed IP's...I've never had to set that before and it is off on my Archive Server (same series NAS) and it is fine.



  • @garak0410 said:

    Real Quick...I did see this setting:

    NFS Service ON or OFF...it was set to OFF. If I set to on, it asks for allowed IP's...I've never had to set that before and it is off on my Archive Server (same series NAS) and it is fine.

    NFS should be OFF. Test with nothing but SMB for now. Unless the software uses its own NFS, then use nothing but NFS.



  • @scottalanmiller said:

    @garak0410 said:

    Real Quick...I did see this setting:

    NFS Service ON or OFF...it was set to OFF. If I set to on, it asks for allowed IP's...I've never had to set that before and it is off on my Archive Server (same series NAS) and it is fine.

    NFS should be OFF. Test with nothing but SMB for now. Unless the software uses its own NFS, then use nothing but NFS.

    I created a new Share with just CIFS, no NFS...same error:

    4/18/2014 9:50:24 AM :: Processing 'Backup Server' Error: Client error: The network path was not found.
    Agent failed to process method {Stg.OpenReadWrite}.

    Guess I'll go for the factory reset now...



  • And it is wide open with read and write for everyone?



  • @scottalanmiller said:

    And it is wide open with read and write for everyone?

    Sorry for the delay...crazy day with other stuff. Yes...wide open for everyone. VEEAM still returns the error...



  • Oh, it is Veeam. Veeam might use native NFS. I thought that this was your old backup software, sorry. Veeam should be NFS I believe.



  • @scottalanmiller said:

    Oh, it is Veeam. Veeam might use native NFS. I thought that this was your old backup software, sorry. Veeam should be NFS I believe.

    Yeah, the old BACKUP ASSIST that I will use just for SQL from our physical server, is fine now when I set the share to PUBLIC in the NAS GUI...just VEEAM now...it is having problem...this worked fine before I rebuild the volume as RAID10 and made a new share...it has to be in the share somewhere but I've set everything up the same...



  • @garak0410 said:

    @scottalanmiller said:

    Oh, it is Veeam. Veeam might use native NFS. I thought that this was your old backup software, sorry. Veeam should be NFS I believe.

    Yeah, the old BACKUP ASSIST that I will use just for SQL from our physical server, is fine now when I set the share to PUBLIC in the NAS GUI...just VEEAM now...it is having problem...this worked fine before I rebuild the volume as RAID10 and made a new share...it has to be in the share somewhere but I've set everything up the same...

    You know.. I said the same thing about a GPO that I've been bashing my head over all day... turns out either there was corruption in my GPO or a very small change I just couldn't see.. I deleted the non working one.. copied a working one and I'm back in business.... I say this to say... just keep digging I'm sure you'll find some odd setting somewhere that's holding you down.



  • Why not just create an iSCSI target and hook that up to your hosts? You could plop a VHD there and hook it directly up to your Veeam VM.



  • @Nara said:

    Why not just create an iSCSI target and hook that up to your hosts? You could plop a VHD there and hook it directly up to your Veeam VM.

    As long as the NAS is stable and reliable, that would work well. I have one client with a cheap, flaky NAS that's been turned into an iSCSI target. It drops on a regular basis.


Log in to reply