I probably just need to deviate from defaults and unhide the Snapshot storage. I'd originally intended to include snapshots along with the live data, however, despite casting a wide net with my Cloud Sync Task, they aren't currently being captured. So we can prioritize what directories we pull during restoration and there are no concerns regarding versioning creating weird folder structures.

We are backing up the live datasets to a B2 bucket with retention turned off. If that is so, then my follow up question would be, if I point the sync task at the raw data and turn on version retention in B2, when I need to pull data back later, is it going to automatically pull the latest version of the files or is it going to download all the different retained file versions?ĭue to my current ignorance, combined with pressure to get things moving, I have for now gone what I consider the 'safe' route. Correct? We wouldn't really have the chance to prioritize particular directories? With that in mind, am I best served by running the Cloud Sync on Primary, pointed at the actual raw data (maybe with retention turned on in B2), or Backup with the Sync just scooping up all the snapshots?Īny recovery is going to be held up by our ISP speed but while I like the idea of Backup handling all backup duties in principle, the Snapshot scenario seems like it would be trouble since we would need to download ALL the snapshots in order to start working with any of our data. We want to use B2 for our offsite backup/DR. 'Primary' and 'Backup', the Primary runs normally and Backup takes in snapshots from Primary via Replication Tasks.

Blaze b2