Create NFS file share on Hyper-V Server 2016

Obsolesce

@dashrender said in Create NFS file share on Hyper-V Server 2016:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

Dashrender

@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:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

OK none of that changes my question.

Obsolesce

Key Points:

The bulk of the data (about 15 TB) comes from about 70 VMs on HV06 being backed up onto the direct-attached MD1000 DAS via SAS cable.
A few TB worth of physical Linux server backups also need to end up on the MD1000. This has to be done remotely via an NFS share, either hosted from HV06 or a VM running on HV06 (with NFS share data stored on the MD1000).

Goals:

The bulk data (15 TB of VM backups) should not touch the network. They should be transferred directly from the MD1000 to the Tape.
The few TB of physical Linux backups needs to be on the MD1000, and needs to be backed up to tape. This CAN be done over the network, but needs to be part of the same (single) tape backup job. (which is just an additional "location" to add in the configuration)
I don't want to have to restore any more data from Tape than what is needed. Example: I don't want to have to restore ALL Linux server backups from tape in order to restore a single Linux server.

DustinB3403

@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.

Nevermind, I must be tired

Dashrender

A VM (the VHD which lives solely on the MD) could act like a NAS - so the Windows Server backup solution could backup to that VM, the physical servers can all backup to this "NAS" via the NFS,
Then you can use Yosemite to backup the contents of the "NAS" to the tape via passthrough to the tape.

Even if you have to use the network, you should be able to use a 10 GB vNetwork inside the host, never touching the physical network outside the box for the data that lives on the HV06 host.

Obsolesce

@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:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

OK none of that changes my question.

Oh I see the question. Yes you can pass a tape drive to a VM using SW tape redirector... but it's slower.

I have a few things to test, but i'm going in order of least work required. So first I'm going to try the following:

Set up Linux VM to host an NFS share in a .VHDX on the MD1000.
Make sure that .VHDX is EXCLUDED in the main tape backup job.
Install Yosemite client in the Linux VM hosting the NFS share.
See if I can configure Yosemite to:
- Back up Hyper-V Backups directly from MD1000 to tape (as they currently are)
- Back up contents of NFS share to tape.

Obsolesce

@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:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

OK none of that changes my question.

Oh I see the question. Yes you can pass a tape drive to a VM using SW tape redirector... but it's slower.

I have a few things to test, but i'm going in order of least work required. So first I'm going to try the following:

Set up Linux VM to host an NFS share in a .VHDX on the MD1000.

Make sure that .VHDX is EXCLUDED in the main tape backup job.

Install Yosemite client in the Linux VM hosting the NFS share.

See if I can configure Yosemite to:

Back up Hyper-V Backups directly from MD1000 to tape (as they currently are)

Back up contents of NFS share to tape.

I think this is what both you and SAM were saying (right?)... it just took me awhile to get what you were saying.

Dashrender

@tim_g 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:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

OK none of that changes my question.

Oh I see the question. Yes you can pass a tape drive to a VM using SW tape redirector... but it's slower.

I have a few things to test, but i'm going in order of least work required. So first I'm going to try the following:

Set up Linux VM to host an NFS share in a .VHDX on the MD1000.

Make sure that .VHDX is EXCLUDED in the main tape backup job.

Install Yosemite client in the Linux VM hosting the NFS share.

See if I can configure Yosemite to:

Back up Hyper-V Backups directly from MD1000 to tape (as they currently are)

Back up contents of NFS share to tape.

I think this is what both you and SAM were saying (right?)... it just took me awhile to get what you were saying.

Yep, this is the end that we were going for.

scottalanmiller

@tim_g 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:

@dashrender said in Create NFS file share on Hyper-V Server 2016:

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?

So I take it there was no merit here?

The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.

OK none of that changes my question.

Oh I see the question. Yes you can pass a tape drive to a VM using SW tape redirector... but it's slower.

I have a few things to test, but i'm going in order of least work required. So first I'm going to try the following:

Set up Linux VM to host an NFS share in a .VHDX on the MD1000.

Make sure that .VHDX is EXCLUDED in the main tape backup job.

Install Yosemite client in the Linux VM hosting the NFS share.

See if I can configure Yosemite to:

Back up Hyper-V Backups directly from MD1000 to tape (as they currently are)

Back up contents of NFS share to tape.

I think this is what both you and SAM were saying (right?)... it just took me awhile to get what you were saying.

Yes!

scottalanmiller

And now you see why Dash really wanted to know which software was in use, so that we could figure out which pieces needed to be used in which way.

Obsolesce

@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:

And now you see why Dash really wanted to know which software was in use, so that we could figure out which pieces needed to be used in which way.

Yes, I started only wanting to run NFS on the HV06 host itself... as in not in a VM, but through a program to install that will allow you to share out a folder via NFS. I was thinking along those lines, and not wanting the software to be relevant.

But I guess in the end, running the backup software inside of a VM instead of the host may be the way to go. The backup software client still needs to be on HV06 (the host) so that stuff can be backed up and so that the tape drive is made available to Yosemite. But also putting the Yosemite client on the VM hosting an NFS share I think will allow me to back up that NFS share directly to tape and also the other stuff to tape in the same job (hopefully not over the network).

I'm going to be testing this today.

Thanks everyone!

Obsolesce

So far, it looks like it will let me do what I want. (serv-nfs) Installed on Fedora 27 minimal from net install, plus a few necessities like Cockpit etc.

Now to fill the linuxbackups directory with a physical Linux server backup test:

0_1516735801842_2aaef08c-0833-4d81-9d2a-b777766cd67b-image.png

matteo nunziati

@tim_g late to party. can this help with your original plan?

Obsolesce

@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:

@tim_g late to party. can this help with your original plan?

Yes, something like that but a little more current would have been perfect!

A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.

DustinB3403

@tim_g said in Create NFS file share on Hyper-V Server 2016:

@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:

@tim_g late to party. can this help with your original plan?

Yes, something like that but a little more current would have been perfect!

A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.

Or just don't use Yosemite

Obsolesce

@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:

@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:

@tim_g late to party. can this help with your original plan?

Yes, something like that but a little more current would have been perfect!

A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.

Or just don't use Yosemite

They stopped selling it, and they want to ride out this last year of support, which ends for everyone Sept 30th I think. Then we are forced to... which can't come soon enough.

Dashrender

With less than 9 months to go, Now is the prefect time to be looking at, testing other options. It's kinda crazy to wait until sept to do that.

Obsolesce

@dashrender said in Create NFS file share on Hyper-V Server 2016:

With less than 9 months to go, Now is the prefect time to be looking at, testing other options. It's kinda crazy to wait until sept to do that.

Already tested and decided on several options, it comes down to budget, which is not decided by me.

My boss already has all he needs from me, with my recommendations and costs.

scottalanmiller

@tim_g 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:

@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:

@tim_g late to party. can this help with your original plan?

Yes, something like that but a little more current would have been perfect!

A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.

Or just don't use Yosemite

They stopped selling it, and they want to ride out this last year of support, which ends for everyone Sept 30th I think. Then we are forced to... which can't come soon enough.

Sounds like it is time for Veeam.

Obsolesce

@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:

@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:

@matteo-nunziati said in Create NFS file share on Hyper-V Server 2016:

@tim_g late to party. can this help with your original plan?

Yes, something like that but a little more current would have been perfect!

A lot less moving parts with something like that... I'd be able to cut out needing another VM and Yosemite license.

Or just don't use Yosemite

They stopped selling it, and they want to ride out this last year of support, which ends for everyone Sept 30th I think. Then we are forced to... which can't come soon enough.

Sounds like it is time for Veeam.

That's great backup software, but for us, it's twice as expensive as other options that tested just as good or better.