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:
@scottalanmiller Why does this need exist to backup from the VM directly to tape?
He is currently backup to Disk first and then to tape.
Why not use the same approach, but with an agent within the VM.
Backup to the same Disk, and let whatever is managing the Disk and Tape copy the backup to tape?
Huh?
Because "the VM" and "to a disk" are the same thing here. So how do you get from the VM to the tape if you don't let the VM talk to the tape?
You said conflicting things.
My point is, his physical linux systems, can be backed up to a VM on Hyper-V which would get it's storage from the MD1000.
Then from Hyper-V use what ever tape solution he has to copy the file to tape.
Um, have you even read this thread? That's what he was ALREADY doing that he's trying to fix.
The MD1000 is connected to the HV06 host, but is in no way associated with Hyper-V. It's strictly a backup repository for all of the VMs on HV06 (all 60-70 of them), and was the location of where the physical linux servers were backed up to.
-
@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 idea is to run a single tape backup job from the HV06 host, so that there is zero network usage from the MD1000 to Tape.
I don't want to run Tape backup from a VM. The VM won't see the main backup repository, only the Linux NFS backup repository.
Ah, so this is pretty huge. But this is the core of the issue, you don't want the thing that you asked for from the beginning.
At some point, you have to not want so many things...
- You don't want to change the software.
- You don't want to use separate software for the NFS.
- You don't want to restore a single VHD.
- You don't want to backup anything except a single VHD.
- etc...
These are brand new constraints.
But still, just stop doing the backup that you have today completely and fix it that way.
-
The backup software was never part of it. That was always irrelevant, as it has to stay the same (WSB, ReaR, Yosemite).
-
I would prefer to host the NFS share via the Hyper-V Host (HV06), straight into a folder on the MD1000. This is ONLY possible via 3rd party software, as Hyper-V Server doesn't allow you to create NFS shares.
-
That's right. When I need to restore something from Tape, I don't want to have to restore a 20 TB VHD that contains everything. Instead, I want to be able to, from Tape, select only what needs restored... for example, the ability to shove in a Tape, and restore a specific physical Linux server image, rather than a single VHD first that contains ALL backups. I don't want to spend 50 hours restoring a 20 TB VHD so, once restored, I can mount it and then finally get the backup image I want.
-
I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
The constraints have always been the same from the very beginning.
Some limiting factors:
- I don't want to "pass-through" the MD1000 to a VM. That's just always a bad idea to pass physical disks to a VM.
Sure, but just put the VM on it initially.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- The backup software was never part of it. That was always irrelevant, as it has to stay the same (WSB, ReaR, Yosemite).
This makes no sense. So you make a new VM and have no option to put a backup tool on it?
-
Before I switched HV06 to Hyper-V Server 2016, it was running Windows Server 2016 DC with Hyper-V Role.
Then, all Hyper-V VMs on HV06 were (and still are) being backed up to the MD1000 (which is the B: drive on the host).... and the host (HV06) was also hosting an NFS share to a folder on the MD1000 (B:\LinuxBackups) in which all physical Linux servers were backing up to via ReaR on each physical Linux server.
The tape drive is connected to HV06, which had Yosemite installed, and was backing up everything to Tape.
Now that HV06 is no longer running Windows Server, and is now running Hyper-V Server, I am no longer able to host that NFS share on the host in which all physical Linux servers backed up to.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- I would prefer to host the NFS share via the Hyper-V Host (HV06), straight into a folder on the MD1000. This is ONLY possible via 3rd party software, as Hyper-V Server doesn't allow you to create NFS shares.
But we covered this. The Linux VM is exactly this. It is third party software, it sits on Hyper-V, and you can put its data stores directly on the MD1000 meeting your criteria in every way.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- That's right. When I need to restore something from Tape, I don't want to have to restore a 20 TB VHD that contains everything. Instead, I want to be able to, from Tape, select only what needs restored... for example, the ability to shove in a Tape, and restore a specific physical Linux server image, rather than a single VHD first that contains ALL backups. I don't want to spend 50 hours restoring a 20 TB VHD so, once restored, I can mount it and then finally get the backup image I want.
Right, but this problem is only caused by point #1. Allow any flexibility in the tools used, not different ones, just reconfigure what you have, and this isn't an issue.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
-
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- The mentioned backup software is what I'm stuck with.
That's not an issue. It's not what you have, it's how it is configured.
-
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
-
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
-
If that VHD lives on the MD1000, it will be put onto tape with everythign else that's 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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
By running a backup from an agent in the VM. Like ReaR which can backup to tape.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
If that VHD lives on the MD1000, it will be put onto tape with everythign else that's on the MD1000.
That's a configuration problem. Nothing technically causes that problem.
-
@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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
By running a backup from an agent in the VM. Like ReaR which can backup to tape.
Okay, let's say I run my tape backup from the Yosemite agent in the VM. Great, now I have all that NFS share backed up to tape.
But that doesn't grab any of the Windows Server Backup data on the MD1000... only the NFS share that contains physical Linux server backups.
That VM isn['t going to see the rest of the MD1000.
-
Still, I would use Yosemite on the Linux VM to back up to tape, not ReaR. Yosemite works better on linux anyways. I'm ONLY using Yosemite for backing up to Tape.
-
If I use the Yosemite backup agent in the VM, and I configure it to back up the MD1000 (not the NFS share) to tape, it will go over the network I believe.
-
I'm going ot have to test this.
I think I understand what you're saying now.
Still have a single tape back up job, but run it all from the Yosemite backup agent on the VM...
I see, that way I can back up the NFS share directly to tape (not the VHD), and in the same job, have it also back up the Windows Server Backup folders.
-
Am I understanding correctly now?
-
If so, this is all dependent on the bulk of the data (the Windows Server Backup stuff) not having to go over the network.
The physical Linux server backups / NFS stuff can.
Yeah, i'm going to set up a test.
