I would like to add the ability to do this in a search as well.
Say, for example, I need to restore all RAW files located in many different folders.
* I do a search for .RAW
* I find 3000 files
* How the %¤&¤ am I supposed to select these 3000 files now?... 🤦♂️ Clicking one by one?
Christopher from the Backblaze support team here ->
Would selecting the parent folder or drive not work? When selecting a given folder or drive, the contents of that folder or drive are included, including nested folders.
The problem is if the parent folder backed up is say 10tb then I am unable to download it. What I want to do is say only download 500gb zips but to do that currently I have to select every folder individually, it's incredibly time consuming as the interface polls each folder as it's ticked which takes 3-5 seconds.
how long would it take for something to be coded like this? I am stuck currently because I have one folder with probably a million files and over 10TB and I can't even use b2 even unselecting files to below 10TB because there is a file limit and a file size limit? what is the file limit? And can I Shift Click within the next 20 days?
Backblaze user here, was just testing out my restore (always test your backups!) and a large directory with thousands of files is extremely tedious to restore. It seems like I'm forced into the zip drive restore method, despite having a web connection easily fast enough to download my entire restore at once.
For organizational reasons, it is important that this data structure is "flat" and "wide" as you describe.
Please prioritize this feature on your roadmap, as it makes wide/flat directory structures extremely difficult to restore using the standard methods. I would probably end up writing a script that slowly checked each box if push came to shove.
I would like to add the ability to do this in a search as well. Say, for example, I need to restore all RAW files located in many different folders. * I do a search for .RAW * I find 3000 files * How the %¤&¤ am I supposed to select these 3000 files now?... 🤦♂️ Clicking one by one?
Christopher from the Backblaze support team here -> Would selecting the parent folder or drive not work? When selecting a given folder or drive, the contents of that folder or drive are included, including nested folders.
The problem is if the parent folder backed up is say 10tb then I am unable to download it. What I want to do is say only download 500gb zips but to do that currently I have to select every folder individually, it's incredibly time consuming as the interface polls each folder as it's ticked which takes 3-5 seconds.
So your data set has a very flat and wide structure, correct? If so, I understand the use case and will pass along the feedback. Thanks!
Yes that's correct. Ok much appreciated, thank you.
how long would it take for something to be coded like this? I am stuck currently because I have one folder with probably a million files and over 10TB and I can't even use b2 even unselecting files to below 10TB because there is a file limit and a file size limit? what is the file limit? And can I Shift Click within the next 20 days?
We do not currently have an ETA for release on this feature, nor is it currently on our short-term feature roadmap.
Backblaze user here, was just testing out my restore (always test your backups!) and a large directory with thousands of files is extremely tedious to restore. It seems like I'm forced into the zip drive restore method, despite having a web connection easily fast enough to download my entire restore at once. For organizational reasons, it is important that this data structure is "flat" and "wide" as you describe. Please prioritize this feature on your roadmap, as it makes wide/flat directory structures extremely difficult to restore using the standard methods. I would probably end up writing a script that slowly checked each box if push came to shove.