Hello every one,
we will be having a Hyper V Server with 4 VMs running on.
The Size of the VMs will be 2 TB.
Which backup method will be the best ?
can you help us. Thanks!
-
- Novice
- Posts: 4
- Liked: never
- Joined: Nov 10, 2022 12:03 pm
- Full Name: Sipan Osspi
- Contact:
-
- Service Provider
- Posts: 605
- Liked: 155 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Hyper V, 4 VMs with 2 TB
daily 3-2-1 is a good start.
-
- Veeam Software
- Posts: 3881
- Liked: 657 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Hyper V, 4 VMs with 2 TB
Hello,
@sunpso
If you do not have any specific requirements, simply add the Hyper-V server to the Veeam infrastructure and create a backup job. It is important to note that Karsten's advice regarding the 3-2-1 rule is relevant. Here is the user guide section where you can find the instructions to create a backup copy.
Thanks!
@sunpso
If you do not have any specific requirements, simply add the Hyper-V server to the Veeam infrastructure and create a backup job. It is important to note that Karsten's advice regarding the 3-2-1 rule is relevant. Here is the user guide section where you can find the instructions to create a backup copy.
Thanks!
-
- Novice
- Posts: 4
- Liked: never
- Joined: Nov 10, 2022 12:03 pm
- Full Name: Sipan Osspi
- Contact:
Re: Hyper V, 4 VMs with 2 TB
Hello,
Thank you Karsten and Petr.
Would a single backup job be sufficient for all VMs together or should I create 4 backup jobs, one backup job for each VM? or at least 2 Backup jobs?
Regarding the 4 VMs have 2 TB
Thank you Karsten and Petr.
Would a single backup job be sufficient for all VMs together or should I create 4 backup jobs, one backup job for each VM? or at least 2 Backup jobs?
Regarding the 4 VMs have 2 TB
-
- Veeam Software
- Posts: 3881
- Liked: 657 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Hyper V, 4 VMs with 2 TB
Hello,
If you do not have any specific requirements such as separate backup schedules or specific settings for certain virtual machines (VMs), such as backup mode, compression algorithm, or block size, and if you do not need to store some VM backups on a dedicated repository, then using a single job would be fine. Based on the fact that you are asking this question, it seems that a single job would perfectly fit your case
Thanks!
If you do not have any specific requirements such as separate backup schedules or specific settings for certain virtual machines (VMs), such as backup mode, compression algorithm, or block size, and if you do not need to store some VM backups on a dedicated repository, then using a single job would be fine. Based on the fact that you are asking this question, it seems that a single job would perfectly fit your case

Thanks!
Who is online
Users browsing this forum: No registered users and 3 guests