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; } } }

Migration of teamsite 5.5.2 server

cheeku

Hi

Can you please help me in migrating 5.5.2 teamsite server to another of the same configuration?

Thanks
CHeeku

Find more posts tagged with

Comments

nipper

Provide more specifics.

What OS ?

Do you have a Dev server ?

Is there a config branch ?

How are users handled ?

Why are you going to 5.5.2 anyway ? That puppy is EOL'ed.

gzevin

...and.. what kind of help is required? moral support or something else ?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

sortcrosstab.rptdesign

cheeku

Its windows OS only.We do not have a dev server and there is no config branch as such. I hope you are not talking about any default folder created under c drive. Users are handled separately so I don't see any SID issues.

Please let me know if your need more info.

cheeku

Not moral support but the steps to migrate the server.

pranav

Hi,
Still you havn't answred the full configuration details.Which plate form ?
Are shifting the server to some othet domain ?
What is the size of the store ?

-Pranav

Nicholas

Here is some basic idea, hope it will help..
-- Ensure new TeamSite server with patches and other required installations.
-- Backup all the data from the backing store, templates, configuration files, custom scripts & uid files.
-- Update the iw-cfg with respective production server.
-- Freeze and Migrate the branches and check the permissions also
-- Ensure all uid files and their access
-- Copy configuration and custom scripts, perl modules etc.
-- VFE configuration files
-- Create custom menu items
-- Migrate odnode.xml and odbase.xml OpenDeploy config files

You may need other things also according to you setup.

Thanks Nicholas

nipper

Well, then do the following (non-inclusive list)

install TS on your new server.

copy over the iw-store from the old server to the new server,
copy iw-home from the old server to the new server (temp dir)

Pray that you all used domain logins or you will need to remap the UIDs.

Start manually going through files that were modified (templating.cfg,
submit.cfg, available_templates.cfg, wfts, anything in custom)
create a config branch and copy them into there. Manually mmerge the
new iw.cfg with the iw.cfg you imported.

Curse the fact that you did not have a config branch.

Copy the config branch files to iw-home. Then write a WF and deployment so it
is automated.

Do the same for OD.

Hire a consultant when you get hosed.

Andy

gzevin

the last sentence is the most cruical part!

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

cheeku

Pranav

What configuration details you require? The domain is same however the size of the store is 25 GB. Let me know if you need anything else.

Thanks

cheeku

I think you are talking about teamsite upgradation and not of teamsite migration.
I have two teamsite 5.5.2 servers and I need to migrate the content and data using backing store.

Let me know things to keep in mind for backing store restoration.

Please note that there are two different machines however the configuration and other programs are same.

Thanks