ufhell.blogg.se - Veeam hyper v backup best practices

Is this something I can do without? If not, can I easily set up a replication server at a later date without having to do much reconfiguring? Until the migration from the current server has been fully completed, I don't have another server to be able to set this up.

I've found that best practice is to have a replication server that VMs are replicated to in case the primary server fails.

VM4 - Utility server - will be used as a web server for both internal and external pages.

HV1 - Hyper-V Host running with 4 VMs set up.

New server setup - Hyper-V Host and all VMs running Windows Server 2022:

DC, DNS, IIS, File Share, Exchange 2016, MySQL.

Backups will be stored on a Synology NAS as well as two external NAS drives that contain periodic backups and are kept unplugged when not used. I just can't seem to wrap my head around how I should be setting it up for my network with the current infrastructure I have at my disposal.

After extensive research, Veeam seems to be the best option for backing up VMs.

I've had no issue understanding everything else and getting things set up, but the part that I'm stuck on is backups. It's been roughly 7 years since I last touched virtualization in any real capacity, and I've never worked with Hyper-V at all, so these last few weeks have been a mess of research, planning, and trial and error to try to learn the best practices regarding Hyper-V, virtualization in general, and backing up/restoring VMs. I am configuring a new server to replace our physical server which was set up before my time and hosts all roles on one OS.