fattipants2016 Posted April 17, 2019 Share Posted April 17, 2019 Anyone using backblaze with their (home) client? Are you pointing the client at the physical disks? Or at your drivepool drive letter? I saw their client doesn't rely on VSS, but I wasn't sure if pointing it at the pool would cause any additional overhead. Quote Link to comment Share on other sites More sharing options...
0 Bowsa Posted April 20, 2019 Share Posted April 20, 2019 I think it's trash.. Has been running for 2 week and it hasn't backed up shit. Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted April 29, 2019 Share Posted April 29, 2019 It may not rely on VSS, but it may still be using it. @Bowsa Have you tried pointing it at the underlying disks in the pool? Quote Link to comment Share on other sites More sharing options...
0 Bowsa Posted May 2, 2019 Share Posted May 2, 2019 On 4/29/2019 at 7:23 PM, Christopher (Drashna) said: It may not rely on VSS, but it may still be using it. @Bowsa Have you tried pointing it at the underlying disks in the pool? No, but won't that be problematic in the following scenarios? 1) Purpose of "Physical" DrivePool is the organization, structure, and distribution of files between the pool of drives. Backing up the underlying drive would be out of order? 2) Pointing it towards my "CloudDrive" doesn't do anything either, it doesn't backup my CloudDrive. Quote Link to comment Share on other sites More sharing options...
Question
fattipants2016
Anyone using backblaze with their (home) client?
Are you pointing the client at the physical disks? Or at your drivepool drive letter?
I saw their client doesn't rely on VSS, but I wasn't sure if pointing it at the pool would cause any additional overhead.
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.