My current SOBR configuration uses a local MinIO repository, which I had been (off-line) syncing to BackBlaze via the B2 interface.
Now that they offer a direct S3 API, I'd like to transition that SOBR to that API (in a new bucket created after 5/4)...
Is there any way to preserve the existing backups for (most of) their retention period without having to wait for 1TB of data and ~4 million of files to be pushed to the new bucket over my SOHO-grade uplink?
At my file count, the Backblaze recommended copy object approach will break the budget.
			
			
									
						
										
						- 
				premeau
 - Influencer
 - Posts: 18
 - Liked: 4 times
 - Joined: Aug 26, 2016 4:30 pm
 - Full Name: SPremeau
 - Contact:
 
- 
				dalbertson
 - Veeam Software
 - Posts: 492
 - Liked: 175 times
 - Joined: Jul 21, 2015 12:38 pm
 - Full Name: Dustin Albertson
 - Contact:
 
Re: Transition to new capacity tier repository?
In short, no.  Even if it's on BB it will appears as a new endpoint when you add the new location as a object repo.
			
			
									
						
							Dustin Albertson | Director of Product Management - Cloud & Applications | Veeam Product Management, Alliances
			
						Who is online
Users browsing this forum: No registered users and 3 guests