Create NFS file share on Hyper-V Server 2016
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
So, do you really have Hyper-V role enabled on a Windows Server install on bare metal?
This is only role or not role, Hyper-V is always bare metal.
-
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
-
@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:
@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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
Which of these is backing up the HV06 Host?
The HV06 host backup is fine, there are no issues, concerns, or questions regarding that.
All I wanted is a way to get Physical Linux Server backup images to the MD1000 via the physical linux server backup software. The only remote way to do that via ReaR is by NFS share. And because HV06 itself cannot host NFS shares, it means I'll have to create a VM on HV06 to host a NFS share to a VHD located on the MD1000.
Please humor me. We are trying to get you what you want.
Yeah, anyways... the best way so far is to have ReaR on each physical Linux server connect to it's own separate NFS share to back up to.
Each separate NFS share will be located on it's own .VHDX disk on the simple VM hosting the NFS shares.
So, when these .VHDX disks are on tape, and I need to restore one of the physical linux servers from tape, I just need to restore the appropriate .VHDX and nothing more.
To avoid using a VHD, I would have to install the Yosemite Tape Backup software client on the HV06 VM, and back up the NFS share directory to tape... BUT, I cannot back up to tape from a VM. I can only back up to tape from the host.
No, that's not the best way. That's the horrible kludge you are stuck with because you are...
- Convinced that your bad Hyper-V backup is actually good and not to be questioned.
- Ignoring us pointing out that even if you refuse to fix your Hyper-V backup that doesn't do an adequate job and creates this entire thread that we can STILL fix this using the tools that you have listed at your disposal.
What do you think is the best way to do it, given the the tools and constraints I have?
-
@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:
It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
Correct me if I'm wrong - none of these can be installed directly on Hyper-V server?
You can install the Windows Server Backup feature on a Hyper-V Server host, the same way you can on Windows Server.
OK good to know, I had no idea.
Yosemite Server Backup client does install on Hyper-V Server luckily.
Is this what gives you an interface to the tape drive that's directly attached to HV06?
-
@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:
@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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
Which of these is backing up the HV06 Host?
The HV06 host backup is fine, there are no issues, concerns, or questions regarding that.
All I wanted is a way to get Physical Linux Server backup images to the MD1000 via the physical linux server backup software. The only remote way to do that via ReaR is by NFS share. And because HV06 itself cannot host NFS shares, it means I'll have to create a VM on HV06 to host a NFS share to a VHD located on the MD1000.
Please humor me. We are trying to get you what you want.
Yeah, anyways... the best way so far is to have ReaR on each physical Linux server connect to it's own separate NFS share to back up to.
Each separate NFS share will be located on it's own .VHDX disk on the simple VM hosting the NFS shares.
So, when these .VHDX disks are on tape, and I need to restore one of the physical linux servers from tape, I just need to restore the appropriate .VHDX and nothing more.
To avoid using a VHD, I would have to install the Yosemite Tape Backup software client on the HV06 VM, and back up the NFS share directory to tape... BUT, I cannot back up to tape from a VM. I can only back up to tape from the host.
No, that's not the best way. That's the horrible kludge you are stuck with because you are...
- Convinced that your bad Hyper-V backup is actually good and not to be questioned.
- Ignoring us pointing out that even if you refuse to fix your Hyper-V backup that doesn't do an adequate job and creates this entire thread that we can STILL fix this using the tools that you have listed at your disposal.
What do you think is the best way to do it, given the the tools and constraints I have?
Same thing I've been saying in every post - backup from within the VM, not from Hyper-V. Don't grab the VHD in the first place.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
Where would I put which piece?
Linux VM on Hyper-V, storage from the MD1000. Exactly as described all along.
-
Can a tape drive be passed to a VM?
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
Where would I put which piece?
Linux VM on Hyper-V, storage from the MD1000. Exactly as described all along.
Yes, I get that.. so ReaR is used on the physical hosts to write the backup over to that VM on the MD1000. Now that it's on the MD1000, how do you get the files on that VM's VHD onto a tape drive that is attached to the Host box of that VM?
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Sure
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
Where would I put which piece?
Linux VM on Hyper-V, storage from the MD1000. Exactly as described all along.
Yes, I get that.. so ReaR is used on the physical hosts to write the backup over to that VM on the MD1000. Now that it's on the MD1000, how do you get the files on that VM's VHD onto a tape drive that is attached to the Host box of that VM?
ReaR.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Sure
USB apparently can't be, so I don't just assume sure.
-
@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:
@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:
@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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
Which of these is backing up the HV06 Host?
The HV06 host backup is fine, there are no issues, concerns, or questions regarding that.
All I wanted is a way to get Physical Linux Server backup images to the MD1000 via the physical linux server backup software. The only remote way to do that via ReaR is by NFS share. And because HV06 itself cannot host NFS shares, it means I'll have to create a VM on HV06 to host a NFS share to a VHD located on the MD1000.
Please humor me. We are trying to get you what you want.
Yeah, anyways... the best way so far is to have ReaR on each physical Linux server connect to it's own separate NFS share to back up to.
Each separate NFS share will be located on it's own .VHDX disk on the simple VM hosting the NFS shares.
So, when these .VHDX disks are on tape, and I need to restore one of the physical linux servers from tape, I just need to restore the appropriate .VHDX and nothing more.
To avoid using a VHD, I would have to install the Yosemite Tape Backup software client on the HV06 VM, and back up the NFS share directory to tape... BUT, I cannot back up to tape from a VM. I can only back up to tape from the host.
No, that's not the best way. That's the horrible kludge you are stuck with because you are...
- Convinced that your bad Hyper-V backup is actually good and not to be questioned.
- Ignoring us pointing out that even if you refuse to fix your Hyper-V backup that doesn't do an adequate job and creates this entire thread that we can STILL fix this using the tools that you have listed at your disposal.
What do you think is the best way to do it, given the the tools and constraints I have?
Same thing I've been saying in every post - backup from within the VM, not from Hyper-V. Don't grab the VHD in the first place.
Okay, so lets say VM99 is my simple Linux VM running an NFS share for all physical Linux servers to back up to.
That simple Linux VM will be living on HV06, which is Hyper-V... so everything will be inside of a VHD, located on the MD1000 anyways.
-
@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:
@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:
@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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
Which of these is backing up the HV06 Host?
The HV06 host backup is fine, there are no issues, concerns, or questions regarding that.
All I wanted is a way to get Physical Linux Server backup images to the MD1000 via the physical linux server backup software. The only remote way to do that via ReaR is by NFS share. And because HV06 itself cannot host NFS shares, it means I'll have to create a VM on HV06 to host a NFS share to a VHD located on the MD1000.
Please humor me. We are trying to get you what you want.
Yeah, anyways... the best way so far is to have ReaR on each physical Linux server connect to it's own separate NFS share to back up to.
Each separate NFS share will be located on it's own .VHDX disk on the simple VM hosting the NFS shares.
So, when these .VHDX disks are on tape, and I need to restore one of the physical linux servers from tape, I just need to restore the appropriate .VHDX and nothing more.
To avoid using a VHD, I would have to install the Yosemite Tape Backup software client on the HV06 VM, and back up the NFS share directory to tape... BUT, I cannot back up to tape from a VM. I can only back up to tape from the host.
No, that's not the best way. That's the horrible kludge you are stuck with because you are...
- Convinced that your bad Hyper-V backup is actually good and not to be questioned.
- Ignoring us pointing out that even if you refuse to fix your Hyper-V backup that doesn't do an adequate job and creates this entire thread that we can STILL fix this using the tools that you have listed at your disposal.
What do you think is the best way to do it, given the the tools and constraints I have?
Same thing I've been saying in every post - backup from within the VM, not from Hyper-V. Don't grab the VHD in the first place.
Okay, so lets say VM99 is my simple Linux VM running an NFS share for all physical Linux servers to back up to.
That simple Linux VM will be living on HV06, which is Hyper-V... so everything will be inside of a VHD, located on the MD1000 anyways.
Yes. That much we are in agreement on.
-
Now, like any normal backup, you install your backup agent on your OS, that would be Linux named VM99 in this case. Then you backup file by file and can restore, file by file.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Sure
Yeah I tried out StarWind tape redirectory... it works excellent, but it's slow.
ANd if it's being passed to a VM, the VM won't see 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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Sure
Yeah I tried out StarWind tape redirectory... it works excellent, but it's slow.
ANd if it's being passed to a VM, the VM won't see the MD1000.
Since the VM sits on top of the MD1000, when would you want a VM to "see" the MD1000?
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
Where would I put which piece?
Linux VM on Hyper-V, storage from the MD1000. Exactly as described all along.
Yes, I get that.. so ReaR is used on the physical hosts to write the backup over to that VM on the MD1000. Now that it's on the MD1000, how do you get the files on that VM's VHD onto a tape drive that is attached to the Host box of that VM?
ReaR.
OK - so assuming that the tape drive can be passed to the VM99, cool, ReaR solves the problem here just like it solved it on the remote physical Linux boxes.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
So, here is what I propose, and is what I've proposed since the first post, and I've never found out why it isn't perfect...
Why don't you make a Linux VM for NFS. And back that up with ReaR instead of with the useless thing on Hyper-V that is trying to back up the entire VHD at once?
Where would you put it Scott?
Where would I put which piece?
Linux VM on Hyper-V, storage from the MD1000. Exactly as described all along.
Yes, I get that.. so ReaR is used on the physical hosts to write the backup over to that VM on the MD1000. Now that it's on the MD1000, how do you get the files on that VM's VHD onto a tape drive that is attached to the Host box of that VM?
ReaR.
OK - so assuming that the tape drive can be passed to the VM99, cool, ReaR solves the problem here just like it solved it on the remote physical Linux boxes.
Or use something like Veeam Linux agents. Or just copy files. Anything will work at this point.
-
@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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Sure
Yeah I tried out StarWind tape redirectory... it works excellent, but it's slow.
ANd if it's being passed to a VM, the VM won't see the MD1000.
You don't have a single backup job. You have at least two.
One job at the Hyper-V level, and another at the VM99 level.
