4 ms·
Wow thanks Yev ! It's #499226 No hard feelings at all against the support guy, who probably has to deal with dubious customer claims all day. But it was pretty
by renaudg 7y ago
Wow thanks Yev ! It's #499226
No hard feelings at all against the support guy, who probably has to deal with dubious customer claims all day. But it was pretty frustrating when he told me the log file I looked at couldn't possibly have anything relevant in it, when I had in fact just showed him plenty of relevant things from it :)
- renaudg 7y agoWell, not trying to turn this into a support forum any further, but I've just upgraded to 7.0 and right now SMS 2FA seems broken ("The verification code is invalid" every time)
- atYevP 7y agoYev here -> I'll do support wherever I see my bat-signal :D Do you have an alternate method set? If you reach out to support -> https://help.backblaze.com/hc/en-us/requests/new https://help.backblaze.com/hc/en-us/requests/new (they have live chat right now) - they can try an alternate method if our primary provider isn't reaching your device!
- Operyl 7y agoIt's completely broken here as well, which was really frustrating. I already wasted 117 days of a yearly subscription on one machine because it ran Catalina Beta (which was my fault, I needed a test machine, and I ate the time lost without complaint), but not being able to inherit that back up really sucked afterwards.
- atYevP 7y agoYev here -> Have you reached out to support about the issue? They are working with our devs to track all of the issues and could use the additional data points -> https://help.backblaze.com/hc/en-us/requests/new https://help.backblaze.com/hc/en-us/requests/new. It's working for most users, so we're trying to whittle down the issue.
- Operyl 7y agoIt’s too late now, I already wiped the old backup and reassigned the license. I didn’t feel like wanting to waste the time much further after past experiences with support and what I read here.
- atYevP 7y agoJust spoke with support you'll be getting an update soon (part of the delay is every time it gets updated by the requester it automatically gets moved to the bottom of the queue due to the way they are ordered - it's a weird quirk). Support should give you more details but it is indeed the case that some of the logs we have aren't tied to every process - so the transmit logs are paramount for debugging inherit backup state issues, but other log files wouldn't be. That said, we should totally fix the typo in the other log files, I've let the devs know about that!