Just a quick clarification: per-vm backup file chains are not created with reverse incremental backup method, right?
Thanks for the answer!
Regars
Gregor
			
			
									
						
										
						- 
				GregorS
 - Veeam ProPartner
 - Posts: 58
 - Liked: 14 times
 - Joined: Apr 10, 2013 12:11 pm
 - Full Name: Gregor Smerke
 - Location: Ljubljana, SI - Slovenia
 - Contact:
 
- 
				Dima P.
 - Product Manager
 - Posts: 14946
 - Liked: 1836 times
 - Joined: Feb 04, 2013 2:07 pm
 - Full Name: Dmitry Popov
 - Location: Prague
 - Contact:
 
Re: Per-VM Backup Files and Reverse Incremental?
Hi Gregor,
Should be possible to use Per-VM Backup Files - the only limitation is you can’t use in on a backup repository with rotated drives.
			
			
									
						
										
						Should be possible to use Per-VM Backup Files - the only limitation is you can’t use in on a backup repository with rotated drives.
- 
				GregorS
 - Veeam ProPartner
 - Posts: 58
 - Liked: 14 times
 - Joined: Apr 10, 2013 12:11 pm
 - Full Name: Gregor Smerke
 - Location: Ljubljana, SI - Slovenia
 - Contact:
 
Re: Per-VM Backup Files and Reverse Incremental?
Hmm... Yesterday (Saturday) I enabled Per-VM backup files option on a repository where rotated hard drives option was never enabled before. At the time the repository contained a chain of 1 VBK and 59 VRBs. A scheduled active full backup started today at 00:00 (Sunday) and finished successfully however a new monolitic VBK file was created. Where should I look first to troubleshoot this? My goal is to have smaller backup files for better Windows Server 2012 R2 deduplication. I prefer reverse incremental as it enables me to easily manage free space on the backup repository by only adjusting the number of restore points. Thanks!
			
			
									
						
										
						- 
				dellock6
 - Veeam Software
 - Posts: 6208
 - Liked: 1995 times
 - Joined: Jul 26, 2009 3:39 pm
 - Full Name: Luca Dell'Oca
 - Location: Varese, Italy
 - Contact:
 
Re: Per-VM Backup Files and Reverse Incremental?
hi Gregor,
this is a bug that will be solved in the next update, so far in order to leverage per-vm chains the active full needs to be manually invoked, not through schedule.
			
			
									
						
							this is a bug that will be solved in the next update, so far in order to leverage per-vm chains the active full needs to be manually invoked, not through schedule.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
			
						Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Who is online
Users browsing this forum: Amazon [Bot], Baidu [Spider], ryoma and 3 guests