Veeam 12, offloading to immutable Backblaze. When I look in History/Storage Management, I see SOBR Offload jobs for each backup job that goes to a given backup repository, and then I see a separate offload job for the SOBR itself. Both jobs appear to be moving data, so am I backing everything up to B2 twice?
What initially drew my attention to this area is that the SOBR-specific offloads frequently warn with "Object storage cleanup failed: Timed out waiting for the backup files to be released, cancelling the job." I see subsequent SOBR-specific jobs clean up the storage so I've been considering them to be benign warnings, but I've been encouraged to either root them out or make them stop sending emails.
			
			
									
						
							- 
				mikeely
- Veteran
- Posts: 255
- Liked: 75 times
- Joined: Nov 07, 2016 7:39 pm
- Full Name: Mike Ely
- Contact:
Are my backups going to S3 twice?
'If you truly love Veeam, then you should not let us do this  ' --Gostev, in a particularly Blazing Saddles moment
' --Gostev, in a particularly Blazing Saddles moment
			
						 ' --Gostev, in a particularly Blazing Saddles moment
' --Gostev, in a particularly Blazing Saddles moment- 
				Gostev
- Chief Product Officer
- Posts: 32784
- Liked: 7990 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Are my backups going to S3 twice?
No, it's not possible to set up SOBR offload in a way that will result in data being backed up to Capacity Tier twice even in theory.
			
			
									
						
										
						Who is online
Users browsing this forum: No registered users and 3 guests