How would you build this



  • @stacksofplates said in How would you build this:

    Anyway I vote for using your own host and what you know best.

    That would be my recommendation as well.

    Just the fact that they're giving me supported options is a great thing, that already rules out many software products.


  • Service Provider

    An obvious question is... does the customer have any needs beyond this that might influence it?



  • If we're talking a $10k solution, I would likely pick option one to simply avoid the finger pointing game and all of that.

    If this were a $100k solution, I'd opt to take the 20% savings.



  • @JaredBusch said in How would you build this:

    @Tim_G said in How would you build this:

    It sounds like the hardware will just be running one VM. Built-in back up on Hyper-V Server 2016 all the way via the host, no issues there if you can use block-level storage for your backups. It's so much easier and faster to backup and restore the VM as a whole anyways... no VM agent needed. Also, you get the option of "production" checkpoints (snapshots) on 2016. That's definitely noteworthy.

    What specific features are you talking about here? I have Hyper-V 2016 server up in a lab environment but have yet to actually test anything.

    I mentioned two in there. Windows Server Backup, and "Production Checkpoints".



  • Ok if it is a Vm what kind of finger pointing could be there? I think about performance and special setups. Virtualization is expected to abstract hw. If the vm image format is convertible I don't see why hypervisor/hw should matter.

    As first I could thick about performances, then guest agents not being available in vendor image, third strange network configs hard to be attained without kvm.

    For sure centos+your hw (can you buy the same machine?) should be near 100% ok!
    Other combinations should be checked for previous 3 points and if they are ok don't see any issue



  • @scottalanmiller said in How would you build this:

    An obvious question is... does the customer have any needs beyond this that might influence it?

    Wait is it to be run for your business or for a customers of yours? If it was for internal usage my previous post still hold. Otherwise I think that keeping the default witha 3rd party is better. Can they understand where a real issue is in case of finger pointing?



  • Beyond the aforementioned finger pointing, what prevents you from running the VM on your current virtual infrastructure w/o purchasing an additional server?



  • @Danp said in How would you build this:

    Beyond the aforementioned finger pointing, what prevents you from running the VM on your current virtual infrastructure w/o purchasing an additional server?

    just the hypervisor I think


  • Service Provider

    @Danp said in How would you build this:

    Beyond the aforementioned finger pointing, what prevents you from running the VM on your current virtual infrastructure w/o purchasing an additional server?

    Current infrastructure or not is a separate discussion point, and not one I need to have here. I know what is where with current infrastructure and how much that will weigh into a decision.

    This discussion is strictly regarding the information provided in the OP and follow up clarification posts.


  • Service Provider

    @Tim_G said in How would you build this:

    @JaredBusch said in How would you build this:

    @Tim_G said in How would you build this:

    It sounds like the hardware will just be running one VM. Built-in back up on Hyper-V Server 2016 all the way via the host, no issues there if you can use block-level storage for your backups. It's so much easier and faster to backup and restore the VM as a whole anyways... no VM agent needed. Also, you get the option of "production" checkpoints (snapshots) on 2016. That's definitely noteworthy.

    What specific features are you talking about here? I have Hyper-V 2016 server up in a lab environment but have yet to actually test anything.

    I mentioned two in there. Windows Server Backup, and "Production Checkpoints".

    I was not sure if those were that actual names of the features. I will have to check into them.

    Obviously Windows Server Backup used to be a specific thing in full installs of Windows Server. Likewise, Checkpoints are a standard thing, but I have not heard about Production checkpoints.



  • @JaredBusch said in How would you build this:

    @Tim_G said in How would you build this:

    @JaredBusch said in How would you build this:

    @Tim_G said in How would you build this:

    It sounds like the hardware will just be running one VM. Built-in back up on Hyper-V Server 2016 all the way via the host, no issues there if you can use block-level storage for your backups. It's so much easier and faster to backup and restore the VM as a whole anyways... no VM agent needed. Also, you get the option of "production" checkpoints (snapshots) on 2016. That's definitely noteworthy.

    What specific features are you talking about here? I have Hyper-V 2016 server up in a lab environment but have yet to actually test anything.

    I mentioned two in there. Windows Server Backup, and "Production Checkpoints".

    I was not sure if those were that actual names of the features. I will have to check into them.

    Obviously Windows Server Backup used to be a specific thing in full installs of Windows Server. Likewise, Checkpoints are a standard thing, but I have not heard about Production checkpoints.

    https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/checkpoints

    Windows 10 and Server 2016 Hyper-V
    Standard Checkpoints -- takes a snapshot of the virtual machine and virtual machine memory state at the time the checkpoint is initiated. A snapshot is not a full backup and can cause data consistency issues with systems that replicate data between different nodes such as Active Directory.

    Production Checkpoints -- uses Volume Shadow Copy Service or File System Freeze on a Linux virtual machine to create a data-consistent backup of the virtual machine. No snapshot of the virtual machine memory state is taken.



  • This post is deleted!


  • This is fairly low cost. Go with the vendor for the extra 20%. 2k isn't much. Should you save that now, and lose 'all' support, its only a few days of work on one issue, unsupported, perhaps less if you have to hire additional help, and that 2k is spent.

    One place to point the fingers at - spend the 2k.

    I'd make sure to have the support contract read and understood in detail to make sure that 2k actually gives me good support though.



  • @black3dynamite said in How would you build this:

    Production Checkpoints -- uses Volume Shadow Copy Service or File System Freeze on a Linux virtual machine to create a data-consistent backup of the virtual machine. No snapshot of the virtual machine memory state is taken.

    always using these in my hyper-v


  • Service Provider

    Thanks for your comments all.