Seagate NAS Connection Problem
-
@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.
-
This ended up being a name resolution problem. FQN in the storage repository did the trick. Back on track now...
