Create NFS file share on Hyper-V Server 2016
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The NFS share won't be on the MD1000, then. It will be inside of a VHD first, and then on the MD1000. That's the issue.
How is that an issue? They are one and the same. The VHD is on the MD1000, so it's not one then the other. It's on the VHD, the VHD is on the MD1000, just two different aspects of the same statement.
This means that ALL physical linux server backups will be inside of that VHD. So in the case I need to restore a single Linux server from Tape, I'd first have to restore the entire VHD.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The NFS share won't be on the MD1000, then. It will be inside of a VHD first, and then on the MD1000. That's the issue.
How is that an issue? They are one and the same. The VHD is on the MD1000, so it's not one then the other. It's on the VHD, the VHD is on the MD1000, just two different aspects of the same statement.
This means that ALL physical linux server backups will be inside of that VHD. So in the case I need to restore a single Linux server from Tape, I'd first have to restore the entire VHD.
Why do you think that? Do you not know you can backup a single file that lives inside a VHD? You can - you can prove that right now - you can copy any file from a Windows VM to another location via the network right now. Nothing says that you can only copy the whole VHD.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
I don't think the tape software will let me dive into a VHDX to restore a single file from it, if it expands multiple tapes... or even at all.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
TL;DR: Is there any 3rd party software that will allow me to host an NFS share on Hyper-V Server 2016,
Yes, that's literally what we are saying to do. A Linux VM is literally "3rd party software that will allow me to host an NFS share on Hyper-V Server 2016". It is, in every way, exactly what you are asking for.
The NFS share won't be on the MD1000, then. It will be inside of a VHD first, and then on the MD1000. That's the issue. I'm first hoping for NFS share directly on the MD1000, not inside of a VHD, unless there are no other options.
You can expose the storage medium directly to the VM though. . . so it wouldn't be "on" the VM. The VM is literally just creating an NFS share from the available storage.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
I don't think the tape software will let me dive into a VHDX to restore a single file from it, if it expands multiple tapes... or even at all.
This isn't an issue because you don't have to backup the VHDX, you can install an agent INSIDE the VM where the NFS is, and backup the files directly.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
I don't think the tape software will let me dive into a VHDX to restore a single file from it, if it expands multiple tapes... or even at all.
Why is there a VHDX being backed up at all. The issue starts with the fact that you are even talking about the VHDX. Just don't use that, problem solved. There is no reason to be backing up the NFS server's contents in a container like that. You weren't gonig to do that with Hyper-V, so you don't need to do it here.
-
@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:
I don't think the tape software will let me dive into a VHDX to restore a single file from it, if it expands multiple tapes... or even at all.
This isn't an issue because you don't have to backup the VHDX, you can install an agent INSIDE the VM where the NFS is, and backup the files directly.
Except his backup solution may not have agents. . . to be installed.
Which If you need a free agent, use UrBackup
-
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
By backing it up normally rather than by putting it into a VHDX and backing it up from the outside. How were you going to do it if you backed up from Hyper-V? Do it the same way.
The Linux VM only gives you more choices, not fewer.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@dustinb3403 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:
I don't think the tape software will let me dive into a VHDX to restore a single file from it, if it expands multiple tapes... or even at all.
This isn't an issue because you don't have to backup the VHDX, you can install an agent INSIDE the VM where the NFS is, and backup the files directly.
Except his backup solution may not have agents. . . to be installed.
Which If you need a free agent, use UrBackup
Exactly - there are ways around that too, as you said, by using another software solution.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
Right, this has to be done right from the beginning, can't be fixed after the wrong thing was backed up.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
Tape shouldn't be used in the recovery process of "grabbing 1 file". It's a our site burnt down, time to rebuild everything when you get the tapes out.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
It can't be on the tape? How is he running a live VM from tape? Mount the VHD on the hypervisor itself and pull the files out.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
It can't be on the tape? How is he running a live VM from tape? Mount the VHD on the hypervisor itself and pull the files out.
That's the thing he is unwilling to do.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
It can't be on the tape? How is he running a live VM from tape? Mount the VHD on the hypervisor itself and pull the files out.
That's the thing he is unwilling to do.
Oh that's what I kept mentioning but I didn't see a response to any of mine. Doing too many things at once here.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
It can't be on the tape? How is he running a live VM from tape? Mount the VHD on the hypervisor itself and pull the files out.
He isn't, the tape is for secondary backups. The MD1000 is being backed up to the Tape as 1 block device. 1 File.
Which is where this issue is coming in. His backup mechanism is the root cause, in that he is backing up multiple little boxes, and making them a giant warehouse that has to be unpacked to get the critical files.
Change this to back up the critical files individually rather than as 1 massive file. Problem solved.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Possible solutions:
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
- This makes restorations more time consuming or complex, because first the .VHDX would need to be restored in order to restore the NFS share inside of it... and then the backup data in the NFS share could finally then be recovered.
- Because it's on a VM, the NFS share will be inside of a .VHDX file.
This is the part that is consistently incorrect. You do not need to restore the VHDX first.
Okay, so how do I get the data off of the VHDX, which is on a Tape, without restoring the VHDX?
One way is again to mount the VHD on the host and then pull the files out that way. Then it has nothing to do with NFS. Just mounting a drive and reading data.
Well, if the VHDX is on the tape.. I'm not sure how you'd mount it. Though I'm sure some systems probably allow you to do that, then you just wait for the tape to load up - probably have timeout issues though.
It can't be on the tape? How is he running a live VM from tape? Mount the VHD on the hypervisor itself and pull the files out.
That's the thing he is unwilling to do.
Oh that's what I kept mentioning but I didn't see a response to any of mine. Doing too many things at once here.
yeah, you and I are on the same page.. both mentioned agents, etc but no response to that solution.
- Create a simple fileserver VM on HV06, serving an NFS share that is located on the MD1000.
-
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
