What is best practice, I musst backup 6 PC which control the Maschine. I want to have only one JOB, but shuld i change the repository and choice option per maschine backup file? so i can when something get wrong copy the backup file of currupted PC to External disk and then is easy to restore.
when i backup normally i will get one file with 6 PC the files could be large. But when i use per vm backup file i dont have deduplication , i use synology as target.
-
- Enthusiast
- Posts: 76
- Liked: 6 times
- Joined: May 31, 2018 6:44 pm
- Full Name: Gregor Duzic
- Contact:
-
- Veeam Software
- Posts: 3624
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Repository file per vm backup file? or not?
Hi Gregor,
The per-vm option allows you to improve performance by writing data in multiple streams but more space is required on the repository since the deduplication ratio greatly depends on backup chain type. The per-vm is highly recommended when backing up to deduplication storage systems.
Obviously, you can restore workloads from any type of backup whether it's per-vm or not, you don't need to copy something to an external disk. However, I also suggest to use backup copy job to respect the 3-2-1 rule.
Thanks!
The per-vm option allows you to improve performance by writing data in multiple streams but more space is required on the repository since the deduplication ratio greatly depends on backup chain type. The per-vm is highly recommended when backing up to deduplication storage systems.
Obviously, you can restore workloads from any type of backup whether it's per-vm or not, you don't need to copy something to an external disk. However, I also suggest to use backup copy job to respect the 3-2-1 rule.
Thanks!
Who is online
Users browsing this forum: Paul.Loewenkamp, Semrush [Bot] and 287 guests