how do you sync into a specific namespace?

[tcabernoch]

Namespace properties seem to sync along with the actual backups.
If you try to sync something in namspace /a to a PBS with namspace /b, what you get is /b/a/.

I want to grab stuff from /a on the first server and put it into /b without its namespace properties.
I want /a from the first server to go into /b. Just that. Just the content, not the freakin namespace too.

How do I do that?

 

[tcabernoch]

I guess you just don't sync a namespace into another one.
Or rather, while you can do that, it does make an intractable mess.
Hard to imagine a use case where that would be useful.

So I guess I need to change the way I think about this.

You don't sync stuff from source namespace /a on the first server into destination namespace /b on the second server.
That winds up with a namespace of /b/a/ ... ?!?

Instead, you sync /a onto the root of the second server.
In the above scenario, source server would have /a. destination server would have both /b and /a.
I guess that's ok. If those are the rules, I can setup a system that uses them.

... If I'm getting this wrong or overlooking some aspect of how this mess might be logical, please let me know.

 

[dcsapak]

Hi,

can you post your sync job configuration?

i just tested this (albeit with a "local" sync instead of remote) and it behaves like expected to me:

datastore1: ns: a => host/test snapshot
datastore2: ns: b => empty

sync job:

local namespace: b
source datastore: datastore1
source namespace: a
max depth: 0

after the sync i have the 'host/test' snapshot in datstore2 in ns b

 

[tcabernoch]

Just a quick note ... thanks for your reply.
I'll get a chance to look at this in the next day or two. I'll try it again, see if its still doing stuff I don't expect, and post here again.

 

[tcabernoch]

Thank very much for following up.

After I rebuilt and retested my Primary to Secondary and my Site to Site sync jobs today, I did not have any sort of issue with the namespaces.
No problems at all, worked exactly like my naive expectation.
Before when I did this, it resulted in whole new namespaces registered on the target box, nested inside the intended ones.
This time I was able to sync stuff from one namespace into another and no additional properties came with them.

I think the problems i encountered before were because i made namespaces after the logins used to access them, so the existing logins weren't granted rights to the new namespaces. (That's a whole step with the logins, you have to grant rights. And that was skipped if the namespaces were made afterwards.)
Because of the issues i encountered, i had recreated all of the logins and all of the namespaces and then registered all of the PBS servers with all the clusters utilizing all these objects.
It was a huge PITA.
I think when i tested today ... well i'd already fixed the problem. I hope.