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.
-
@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.
Yosemite Server Backup client does install on Hyper-V Server luckily.
-
@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:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
That's what I'm saying in part 2. but it part 1 I'm pointing out that the problem you are trying to solve never existed in the first place. You are ignoring that the underpinning problem you have... doesn't exist at all.
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 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:
Awesome!
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The tape drive is attached to HV06.
Tapeserv is a physical box running the TapeBackup Server SOftware.
HV06 contains the tabe backup software "client".
So you've installed a tape backup software agent inside Hyper-V?
Yeah, I can't back anything up from HV06 without the backup client being installed on the host.
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
The trick is that I'm trying to get some physical Linux servers to back up to the MD1000 directly, which has to be done via a NFS share.
So create an NFS share on the MD1000, give it 200TB, install agents on your physical Linux servers, and perform bare metal backups directly to the MD1000!
What the hell is so difficult here?
MD1000 is a DAS, can't "make shares" on it.
Partitions then.
How does that help?
His backup software can target individual partitions, which are connected to a Server and shared as NFS.
That still makes no sense. The backup software targets NFS, it can't tell if there are or are not partitions. Nor do the partitions servce any purpose.
-
@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.
Yosemite Server Backup client does install on Hyper-V Server luckily.
OHHHHH K - NOW we're getting somewhere...
YOU HAVE HYPER-V ROLE ENABLED ON A Windows Server install - This changes EVERYTHING.
-
@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:
@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:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
My solution is a horrible hack.
It's not bad.
The bases of hte new SCDPM backup is everything is on VHDXs... that that itself isn't bad.
It's just that in this case... If i have a lot of different server images contained in a single VHD, and then that single VHD is on tape.... and I need to restore a specific server image...
Well, I need to first get that single VHD off of tape, so that I may pull out the server image I need.
But if each Linux server image is in it's own VHD... when I want to restore from tape, I can find the appropriate VHD just for that server and restore that.
Actually, it kind of is bad. Only backing up as VHDs, and not providing agent based backups, doesn't always work for all workloads and like here, doesn't meet your needs.
-
@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:
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.
Yosemite Server Backup client does install on Hyper-V Server luckily.
OHHHHH K - NOW we're getting somewhere...
YOU HAVE HYPER-V ROLE ENABLED ON A Windows Server install - This changes EVERYTHING.
Though I say this, and yet you're saying that you can't install NFS on Hyper-V...
So, do you really have Hyper-V role enabled on a Windows Server install on bare metal?
-
@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.
The reason it's irrelevant is because the software cannot change. I have my constraints, and need to find a way to work within them.
That's all that we needed to know, that, we know that RandR does what is needed. So problem definitely solved in the very first responses - it doesn't need to be backed up as you imagined and the underlying issue doesn't exist.
-
@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.
-
@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.
Yes, there is. This entire thread is because you think that those backups are terrible and can't do what is needed.
-
So, do you really have Hyper-V role enabled on a Windows Server install on bare metal?
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
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.
Right, we are all in agreement there
That sounds like a great answer, and solves everything. It's the Hyper-V backup tool that you are using that's the problem 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:
@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.
Yosemite Server Backup client does install on Hyper-V Server luckily.
OHHHHH K - NOW we're getting somewhere...
YOU HAVE HYPER-V ROLE ENABLED ON A Windows Server install - This changes EVERYTHING.
No, HV06 is running Hyper-V Server 2016... NOT Windows Server + Hyper-V Role...
If I was running Windows Server plus Hyper-V Role... there would NOT be any issues, as I'd simply be able to host an NFS share on the Host ^_^ (like I was before I switch to Hyper-V Server)
-
@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.
-
@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?
