pst files (1.5-2GB each) because like practically everyone on the planet, he leaves his e-mail client open when the computer is turned on. Right now I'm dealing with a client who just lost several large. If you have an example, we would love to hear it so we can work on it. So far we've had trouble finding these examples of files that are ONLY possible to copy through VSS and not possible using our other techniques. So Backblaze isn't opposed to VSS, it's just a matter of finding the programming time to figure out how to use it and possibly how to auto-configure it for customers, and to find at least 1 example where the other 12 techniques we have to copy a file won't work. But more and more we have lots of extra programmers, and we can possibly write the code that if we are running on Windows, and if a normal file copy fails we could also try to figure out how to turn on VSS for the customer, configure it correctly for the customer, and make a copy of the file that way. Now BEFORE this year, we were so busy and had so few client programmers at Backblaze it wasn't worth considering. And won't work on many file systems we see on PCs. We just want to keep them safe, with zero configuration.Īll fixes we do related to VSS won't work on Macintosh. We live in the consumer world, and that is a world where the consumer doesn't setup every last thing to work correctly with Backblaze. Since we have to solve the IDENTICAL PROBLEMS on file systems without VSS, we try to do it some more general way, then get more specific if the general system didn't work. So no matter what, Backblaze has to deal with the problems of what happens on say Apple Extended Filesystem. So why didn't we ONLY support systems with VSS from the beginning? Ok, so VSS is not always available on all systems and all file systems. But Backblaze could take over figuring out how to configure VSS and make it appear easy and simple to customers. VSS is really hard to understand and use, so it isn't clearly inside of our charter. Our goals are simple: make a backup without requiring the customer to configure anything. We are not opposed to using VSS or any other technology. Backblaze uses tons of technologies, which ever is required or appropriate in each situation. Longer Answer: VSS (Volume Shadow Service Copy Support) is a technology, not an answer or the only solution to whether you can copy files or not. Short Answer: no current plans to support VSS, but it is probably a good corner optimization for maybe 1 file out of billions of customers' files that there is no other way to make copies, and you might see it within 2 years. But here is the situation with VSS on Backblaze Backup: Plus the nagging worry everybody will have (Backblaze included) that Microsoft will cancel VSS as a supported technology and we'll have to scramble for some other solution anyway.Īny roadmap to solve this issue - or do need to stick it out with CrashplanĬrashPlan is a great service, it's not so bad to stick with them. Which I think everybody would prefer considering the massive difficulties and complexity and possible performance hit VSS introduces. So we MIGHT (no promises) be able to achieve a backup for you without using VSS. It turns out there are a variety of different techniques to read locked files, VSS is not the only one. You can post the full paths here, or PM me, or just open a support ticket if you want to keep the list private (and that's TOTALLY understandable and we'll keep that confidential). We would love to hear about which files those are. Disclaimer: I work at Backblaze on the Backblaze Backup product line.įiles that are open 95% of the time so backup will likely never work
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |