Create NFS file share on Hyper-V Server 2016
-
OK, sounds like a solution has been found.
Use Windows Backup in Hyper-V to backup the VM's running on HV06, except for VM99 to the MD1000. If the Windows backup also supports a tape drive, use it to backup that local disk backup to tape. D2D2T If Windows backup won't work, use Yosimite or whatever will run in Hyper-V to move the backup files to tape.
From within VM99, use ReaR or whatever Linux software supports tape backups, to backup files within VM99 to the tape drive.
-
@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.
-
@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.
How do you figure?
short of using my crazy solution above with many mountpoints/VHDs - how does he get file level recovery of his Linux server backup files? -
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Everything is being backed up to tape just fine and as it should be.j
Can't be "just fine" or this thread wouldn't exist. It is getting backed up in a form that you don't like, it's not adequate. If it was backed up "just fine", there wouldn't be anything more to discuss.
-
@dashrender 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.
How do you figure?
short of using my crazy solution above with many mountpoints/VHDs - how does he get file level recovery of his Linux server backup files?The VM never needs to see the block storage, the hypervisor does, nothing else.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
How is everything on the MD1000 getting backed up to tape? Currently that is being done via the physical host (HV06)
Through the backup software. ReaR specifically supports NFS, CIFS, and Tape.
-
@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.
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@dashrender 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.
How do you figure?
short of using my crazy solution above with many mountpoints/VHDs - how does he get file level recovery of his Linux server backup files?The VM never needs to see the block storage, the hypervisor does, nothing else.
It does to send the backups to it. You can't use a tape mount for live VHD storage.
-
@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.
-
@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.
