Don Lee Posted October 14, 2014 Report Share Posted October 14, 2014 I just upgraded a client to 11.5, and none of the backups worked! After a bit of debugging, I figured out that the problem is that the path to the catalog and the members all contain the bullet (option-8) in the path. I moved the sets, updated the sets in the retro console, and it seems to work now. This was an upgrade from 10.5 to 11.5. This was working fine in 10.5, so the bug was introduced at 11.x version. 1 Quote Link to comment Share on other sites More sharing options...
Maser Posted October 14, 2014 Report Share Posted October 14, 2014 Actually, this is not a bug. They had removed the option-8 privacy feature in an earlier release (maybe 10.5) and then put it back when users (well at least me) complained about this. If something has an option-8 in the file/folder name, it's supposed to be private from the backup (this is a per-client setting, but I think you can set it on the server to override the client settings...) Quote Link to comment Share on other sites More sharing options...
Don Lee Posted October 15, 2014 Author Report Share Posted October 15, 2014 No, that's not the case, because this is not on a client. This is on the server - local disk. The bullet in the name should be irrelevant, and was irrelevant for all versions I've run up until 11.5. Quote Link to comment Share on other sites More sharing options...
Maser Posted October 15, 2014 Report Share Posted October 15, 2014 What I am seeing on my test instance of 11.5: If I make a folder on my desktop called "•DID THIS BACK UP" and put some files in it... If I use the wizard to back up "all files" of the entire volume of the engine computer, it *does* want to back up this folder in the preview: However, if I add my internal hard disk as a *client* computer, it will *not* back up this folder (which is how I'd expect it to work as a client): Quote Link to comment Share on other sites More sharing options...
Maser Posted October 15, 2014 Report Share Posted October 15, 2014 Is your bullet within the file/folder name (rather than at the start/end?) Quote Link to comment Share on other sites More sharing options...
Don Lee Posted October 27, 2014 Author Report Share Posted October 27, 2014 No, the problem is that the media set is on /Volumes/FireWire/•backups/whatever Retro can find the set, but can't write to it. It has nothing to do with the client, or the backup. Retro can't write to the media set if the path to the media set contains a bullet. These are disk sets. Quote Link to comment Share on other sites More sharing options...
Maser Posted October 27, 2014 Report Share Posted October 27, 2014 Ah, sorry! I misread your original post. My guess is it's the same privacy setting. Open a case on that one... Quote Link to comment Share on other sites More sharing options...
Don Lee Posted November 10, 2014 Author Report Share Posted November 10, 2014 The privacy setting should have nothing to do with the location of the *media sets* on the server. If it does, it's busted. Quote Link to comment Share on other sites More sharing options...
Maser Posted November 10, 2014 Report Share Posted November 10, 2014 The privacy setting should have nothing to do with the location of the *media sets* on the server. If it does, it's busted. I would not be surprised if it's not the same code that checks for option-8 on the clients as well. I would agree that there should be a preference setting (maybe there's a hidden one?) that would let you toggle this off/on... Quote Link to comment Share on other sites More sharing options...
bdunagan Posted November 13, 2014 Report Share Posted November 13, 2014 Thanks for finding this. The option-8 privacy setting should only apply to Mac clients (when enabled), but you're right that the engine treats them differently as well. We created bug #5035 to track this, and it will be fixed in the next release. Quote Link to comment Share on other sites More sharing options...
Don Lee Posted January 2, 2015 Author Report Share Posted January 2, 2015 I tested this scenario with version 11.5.3, and it still does not work. I created a folder on the server called "•testme" and another called "testme2". The former yields an error when I create a media set. The latter works. screen shot enclosed. Quote Link to comment Share on other sites More sharing options...
bdunagan Posted January 2, 2015 Report Share Posted January 2, 2015 Yes, sorry for the delay. It wasn't included in 11.5.3, but we plan to fix it in the next release. Quote Link to comment Share on other sites More sharing options...
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.