Jump to content
Don Lee

11.5 can find, but can't write to disk sets that have option-8 in path

Recommended Posts

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.

  • Like 1

Share this post


Link to post
Share on other sites

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...)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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:

 

post-169-0-88861400-1413393185_thumb.png

 

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):

 

post-169-0-06243700-1413393197_thumb.png

 

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Ah, sorry!  I misread your original post.   My guess is it's the same privacy setting.   Open a case on that one...

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

post-24400-0-67884700-1420170275_thumb.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×