4100 s2s file permissions how-to

[Lethe]

I learnt this ages ago, so posting here for all to benefit.

This is 4100 running SnapOS 4.0.860 (UK) and Snap extension s2s (not the new one!).

So you have two Snap servers replicating overnight. The trouble is, the file permissions do not get replicated, so the second box has no file permissions and if you need to switch to that, you are in trouble!

On the main server (replicating FROM), goto Security->File/Folder Security. You will see an option to 'Save File/Folder Security'. So save it :-)

Once this is complete, the server has saved several files containing the permissions structure. Map in the server TOP level share in Windows Explorer using 'root' account and password. Opening this you will see a hidden directory called 'os_private'. In this directory are the files you need - IGNORE the java and temp folders here.

Copy all the *.dat and *.dat.bak files to another safe location. Disconnect the map drive and exit the server.

This part is now complete.

Ensure you have a nice new replica on server#2 (replicate TO server). Now map in server#2 using root account and password. Open up os_private and delete all the *.dat and *.dat.bak file there - you may need to do this several times as some are re-created on the fly. Once this is done, copy the files retrieved from server#1 os_private/ to server#2 os_private/ (overwrite as necessary).

Once that is complete, in the web interface goto Security->File/Folder Security and select Restore File/Folder Security. Then you will see the date of the 'saved permission files' from server#1 in the window to use. Restore it!

Once that is complete, you will now find all the files on server#2 have the same file permissions that are on server#1

One thing to note is that SHARES are local - on server#2 you will have to add permissions to the SHARES manually - but once done, you do not need revisit unless new shares are created on server#1, so you will have to recreate.

The main thing here is to ensure server#2 has a latest replica of server#1 before you do this.

Hope that helps somebody.

Nick

[re3dyb0y]

Originally Posted by Lethe

I learnt this ages ago, so posting here for all to benefit.

This is 4100 running SnapOS 4.0.860 (UK) and Snap extension s2s (not the new one!).

So you have two Snap servers replicating overnight. The trouble is, the file permissions do not get replicated, so the second box has no file permissions and if you need to switch to that, you are in trouble!

On the main server (replicating FROM), goto Security->File/Folder Security. You will see an option to 'Save File/Folder Security'. So save it :-)

Once this is complete, the server has saved several files containing the permissions structure. Map in the server TOP level share in Windows Explorer using 'root' account and password. Opening this you will see a hidden directory called 'os_private'. In this directory are the files you need - IGNORE the java and temp folders here.

Copy all the *.dat and *.dat.bak files to another safe location. Disconnect the map drive and exit the server.

This part is now complete.

Ensure you have a nice new replica on server#2 (replicate TO server). Now map in server#2 using root account and password. Open up os_private and delete all the *.dat and *.dat.bak file there - you may need to do this several times as some are re-created on the fly. Once this is done, copy the files retrieved from server#1 os_private/ to server#2 os_private/ (overwrite as necessary).

Once that is complete, in the web interface goto Security->File/Folder Security and select Restore File/Folder Security. Then you will see the date of the 'saved permission files' from server#1 in the window to use. Restore it!

Once that is complete, you will now find all the files on server#2 have the same file permissions that are on server#1

One thing to note is that SHARES are local - on server#2 you will have to add permissions to the SHARES manually - but once done, you do not need revisit unless new shares are created on server#1, so you will have to recreate.

The main thing here is to ensure server#2 has a latest replica of server#1 before you do this.

Hope that helps somebody.

Nick

Rather useful

Thanks

Mind if we stick it in the FAQ? (Im presuming not with how you've put it will help)

[Lethe]

Yes, stick it in the FAQs by all means.

Nick

[blue68f100]

Sam, I will add it to the FAQ's, there it want get wiped out like all of my FAQ's did.

[jontz]

Thanks for the info!

[jaylweb]

This is 4100 running SnapOS 4.0.860 and Snap extension s2s (not the new one!).

So you have two Snap servers replicating overnight. The trouble is, the file permissions do not get replicated, so the second box has no file permissions and if you need to switch to that, you are in trouble!

I found an easier way to do this plus it mirrors the shares along with the security settings. I have not found a way to automate it yet, but if I do, I will post a reply here.

Make sure you have mirrored your file system first, preferably with S2S!!!

1. Launch Assist.exe
2. Login to your "secondary" server. (Destination server)
3. Go to the Import Server tab.
4. Make sure the "All Server Settings" option is checked.
5. Highlight your "primary" server. (Source server)
6. Click Apply
7. You'll get an "Blah, blah, blah, Are you sure?" prompt, click Yes.
8. It'll prompt you to authenticate to the "primary" (source) server at this time.

You'll see a progress bar pop up and it'll quickly flash what it is working on then it'll say it's done.

Note: Every so often, Assist appears to lock up after the last step. The window is solid white. At this point, I just close Assist and do it again, which works fine. I'm wondering if it has a hard time authenticating when that happens.

[Phoenix32]

Now that is the method I used...