Backup cache location is not accessible

[millardjk]

I've been working with support for a couple of weeks on this (case 03433186) and after reinstalls, changed media, etc., we're still no closer to a solution.

The scenario: cache device working fine with v2, but after upgrading to v3 (and changing license models), the workstation is no longer able to use a cache. Period.

If anyone else has run into this...and successfully fixed it!...your input would be helpful.

[Dima P.]

Hello Jim,

Please try to change the cache location to a local folder and let us know if the issue still persists? Thank you in advance!

[millardjk]

Local folder? As in "a folder on one of the volumes that's being backed up"?

Wow, I'm _finally_ not getting the error. But that also defeats the purpose of the cache--having a current backup chain in the event of primary drive loss--if you chose a "local" folder. (it also means the backup is backing-up the cache chain when "entire machine" is the source)

And for the record, the cache device I'm using has been a USB thumbdrive; since the issue presented, I've tried different make/model & sizes, as well as different filesystems (although FAT32 is supposed to give the longest write life with these devices) with no luck. I've tried an SD card in the built-in reader, but between the fact that it also fails in the same way as the USB drive and the card sticking out much further (and likely to be damaged) than the mini-USB drives I've used, that's a non-starter.

[Dima P.]

Jim,

Thanks for the clarification! I was asking to test local folder in order to identify if the issue is related to usb location only. I've asked RnD team to check your case details, meanwhile please keep working with our support team.

[Dima P.]

Hi Jim,

Sorry for the delay. We've confirmed this behavior and it's marked as bug. We will prepare a hotfix as soon as possible and share it with you via support team. Cheers!

[millardjk]

Is it okay for me to be happy that this is the final analysis? Good to know it's "not just me" and can wait for a resolution.

[millardjk]

The release notes for 3.0.1 didn't say anything about fixes; should this be corrected in 3.0.1, or was it too soon to get into the build?

[Dima P.]

Jim,

3.0.1 unfortunately does not have a fix for your issue, we will make a private fix based on 3.0.1 code. That said it's safe to install 3.0.1 now.

[ursli123]

Hello

I'm dealing with the same problem.

Can you provide me the fix, too?

Without cache I can't sell it to my customers.

Kind regards

Urs

[millardjk]

I have hopes about 3.0.2, but 3.0.1 didn’t do the trick.

[Dima P.]

Hi folks,

3.0.2 contains this fix: you can request 3.0.2 right now via support or download it a bit later via our website. Cheers!

[millardjk]

I pulled the new VBR update—which had 3.0.2 for managed clients—and can confirm that it’s not throwing errors anymore.