Create NFS file share on Hyper-V Server 2016
-
Bleh, the stuff from the NFS share is going to Tape via network (3 GB/minute). The other stuff goes way faster (14 GB/minute), so I can tell that's going directly from MD1000 to tape through HV06 via SAS cable.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Bleh, the stuff from the NFS share is going to Tape via network (3 GB/minute). The other stuff goes way faster (14 GB/minute), so I can tell that's going directly from MD1000 to tape through HV06 via SAS cable.
So is the other one, it's just likely going through the vSwitch inside Hyper-V.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Bleh, the stuff from the NFS share is going to Tape via network (3 GB/minute). The other stuff goes way faster (14 GB/minute), so I can tell that's going directly from MD1000 to tape through HV06 via SAS cable.
So is the other one, it's just likely going through the vSwitch inside Hyper-V.
No, there's no hyper-v involved between the Windows Server Backup data on the MD1000 and tape. HV06 pushes that data from the MD1000 through SAS all the way to the tape drive. That's going at 233 MB/s (1866 mbps), which is fitting for a 3gbps SAS backplane on the MD1000.
The data on the NFS share is going over the regular network from the VM. I'm just not sure the path it's taking. That it's only getting 50 MB/s over a 1gbps network tells me its making it's way (routing over) onto the regular network, somewhere between the VM and it's host. The fact that the NFS share needs to be accessible over the regular network limits me from being able to keep it internal only to the VM and host.
I'll have to think about it a little bit, I'm sure I can figure somethign out.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Bleh, the stuff from the NFS share is going to Tape via network (3 GB/minute). The other stuff goes way faster (14 GB/minute), so I can tell that's going directly from MD1000 to tape through HV06 via SAS cable.
So is the other one, it's just likely going through the vSwitch inside Hyper-V.
No, there's no hyper-v involved between the Windows Server Backup data on the MD1000 and tape. HV06 pushes that data from the MD1000 through SAS all the way to the tape drive. That's going at 233 MB/s (1866 mbps), which is fitting for a 3gbps SAS backplane on the MD1000.
The data on the NFS share is going over the regular network from the VM. I'm just not sure the path it's taking. That it's only getting 50 MB/s over a 1gbps network tells me its making it's way (routing over) onto the regular network, somewhere between the VM and it's host. The fact that the NFS share needs to be accessible over the regular network limits me from being able to keep it internal only to the VM and host.
I'll have to think about it a little bit, I'm sure I can figure somethign out.
Hold on - The VM with your NFS share is on HV06, right? Assuming so, why would the data for the tape leave HV06, go on the network, then return to the box (not sure where it went to be send back to the box) to the Yosemite agent installed in Hyper-V which has access to the tape drive and written to tape.
Is that what you're saying?
-
Again, assuming the VM with the NFS share is a VM on HV06, why wouldn't that VM just use the internal vSwitch to talk to the Yosemite agent on Hyper-V, which then writes to tape?
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Bleh, the stuff from the NFS share is going to Tape via network (3 GB/minute). The other stuff goes way faster (14 GB/minute), so I can tell that's going directly from MD1000 to tape through HV06 via SAS cable.
So is the other one, it's just likely going through the vSwitch inside Hyper-V.
No, there's no hyper-v involved between the Windows Server Backup data on the MD1000 and tape. HV06 pushes that data from the MD1000 through SAS all the way to the tape drive. That's going at 233 MB/s (1866 mbps), which is fitting for a 3gbps SAS backplane on the MD1000.
The data on the NFS share is going over the regular network from the VM. I'm just not sure the path it's taking. That it's only getting 50 MB/s over a 1gbps network tells me its making it's way (routing over) onto the regular network, somewhere between the VM and it's host. The fact that the NFS share needs to be accessible over the regular network limits me from being able to keep it internal only to the VM and host.
I'll have to think about it a little bit, I'm sure I can figure somethign out.
Hold on - The VM with your NFS share is on HV06, right? Assuming so, why would the data for the tape leave HV06, go on the network, then return to the box (not sure where it went to be send back to the box) to the Yosemite agent installed in Hyper-V which has access to the tape drive and written to tape.
Is that what you're saying?
No idea, but yes, that's what I'm saying. The numbers are telling me that. 50 MB/s means data is definitely leaving HV06 for some reason before going to tape.
-
Actually HV06 is connected to a Microtik... so I may be able to "see" for sure.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:
@tim_g late to party. can this help with your original plan?
Yes, something like that but a little more current would have been perfect!
A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.
Try this google search
-
@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:
@tim_g late to party. can this help with your original plan?
Yes, something like that but a little more current would have been perfect!
A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.
Try this google search
Wow your google-fu is better than mine!
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:
@tim_g late to party. can this help with your original plan?
Yes, something like that but a little more current would have been perfect!
A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.
Try this google search
Wow your google-fu is better than mine!
Not often... This has been a lucky one.
