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:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Can a tape drive be passed to a VM?
Yea, but there is no need.
It's a pretty big need, from what I can tell.
It's a misplaced need though.
What's the way around it? The VM needs to get its files, to tape. The backup software runs inside the VM. How does it backup the files inside of itself to a tape drive without talking to the tape drive?
-
@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?
-
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.
I think I will be creating a single Linux VM to host multiple NFS shares each using their own VHD on the MD1000.
This way, when I run the tape backup job, all VHDs/VHDXs/etc will be backed up to tape in one giant swoop as needed (for right now).
And that will just have to be okay until we can replace the backup software with something real.
-
@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?
He's using either Windows Backup or Yosemite to backup to tape. Windows Backup doesn't have an agent situation.. I'm not sure about Yosemite.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The VM won't see the main backup repository, only the Linux NFS backup repository.
@scottalanmiller or did I misunderstand you and you are saying to back up all HV06 VMs to an NFS share that the VM is hosting???
Hmm... somethign to think about
But I need to head out for a bit. I'll jump back on this in a couple hours.
-
@dashrender 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?
He's using either Windows Backup or Yosemite to backup to tape. Windows Backup doesn't have an agent situation.. I'm not sure about Yosemite.
Not on the linux systems he's not. He can use the linux system and without explanation any other backup solution in the world to back these up to disk on whatever he creates as a VM on his Hyper-V host and the appropriate shares.
Then just backup directly to that NFS share from each physical system to that singular VM.
-
What is pushing the data to tape today?
-
@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.
-
@dashrender 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?
He's using either Windows Backup or Yosemite to backup to tape. Windows Backup doesn't have an agent situation.. I'm not sure about Yosemite.
Windows Backup IS an agent.
-
@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.
Sorry, hold that thought... i think I misunderstood you: https://mangolassi.it/post/373820
But I really gotta head out!!! I'll jump back in in an hour or two!
-
@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.
-
Scott - is there a way to get the data of the backups of the local VM's on HV06 into a VHD that is also on HV06?
Assume VM01 is the 15 TB VM that needs to be backed up... currently Hyper-V backs it up using Windows backup to from (just go with me) c:\vms\vm01.vhd to e:\backup\backupupfile e: being on the MD1000.
Is there a way to backup VM01 to the filesystem inside VM99 instead? Then pass the tape through to VM99 and backup everything inside there?
Can this be done and never touch the network? -
@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.
-
@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.
-
@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.
- The mentioned backup software is what I'm stuck with.
- The tape drive is hooked up to HV06 physically, so it's preferred that backup of the MD1000 to Tape be done through the host it's connected to.
- I don't want to install agents on every single VM. HV06 contains 60-70 VMs. Host-based agentless (Windows Server backup) backup is the only way to go here. ReaR is already on physical Linux servers that need backed up.
-
@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.
