nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS mirrored backup server; best pratice

Migrateduser_427

Hello everyone,

I have opened a case with Interwoven over this, but was hoping that someone here might know first.

We are working on making a mirror of our current TeamSite production server and Content Stores and I want to make sure that the below scenario is supported in TS 6.7.1 in regards to keeping the TeamSite User Groups as well as TeamSite Users in sync on both servers.

Scenario:
TeamSite PROD1 server (Main) goes down. TeamSite PROD2 server (Backup) is triggered to take over. The same User Groups and Users that are on TS PROD1 server will be on TS PROD2 granted that the below was done:

In order to make sure the User Groups and Users are in sync on both PROD1 and PROD2:
1) Grab file 'tsgroups.xml' from TeamSite ‘conf’ folder on PROD1 server and place to TeamSite folder ‘conf’ on PROD2 TeamSite server.
2) Grab file 'tsusers' from TeamSite ‘conf/roles’ folder on PROD1 server and place to TeamSite folder ‘conf/roles’ on PROD2 TeamSite server.

I just want to make sure that the files above are the only ones that need to be transferred and that after such it will work.

Has anyone done this?
Thanks!

Find more posts tagged with

Comments

Migrateduser_427

Interwoven has answered my question.

Adam Stoller

Interwoven has answered my question.

Care to share the information for the rest of the forum users?

Migrateduser_427

Sure...

The two files in mentioned on my original posting are correct to copy to the second backup server. But the roles.xml file in the same folder as tsusers.xml should also be copied since roles can also now be edited via GUI in TS 6.7.1.

No other files are changed when a Group, User, or Role is created or edited via GUI.

Another question I posed to Interwoven:

Is it possible to hide the visibility of an entire content store from a group that is not assigned to it? We are using 3 CS's.
The answer was no from them; only branches under the CS can be hidden by setting “Restrict access” check to on under the properties of the branch and oonly assigning groups that should have access to it.

Not a big deal, but would be nice for Users; can be a little confusing to the untrained as to where their area is, but I guess that is why we create training manuals. Smiley Happy

Although, if any one knows a way to hide visibility of a CS that IW is unaware of please do share.

Phanie

See if you can give access to CCStd environment only for those users.

--
Phanie

Migrateduser_427

See if you can give access to CCStd environment only for those users.

--
Phanie

Yeah...

HAHA!
That would work, alas... not an option; the "business" has decided it to be difficult for the users to understand.

It is only CCPro for us.

Personally I would use CCStd and train the users, which are a blank canvas at this point to what TS is. The only users currently are Front End designers and they are deciding what ENV of TeamSite the other users will have access to.

Thanks though.