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

How to migrate content from TS 7.2.1 Prod to dev server?

Kapil_sape

Hi All,

We are using TS 7.2.1, SitePublisher and developed components and pages.

We have to make our development server in sync with Production server. How can we do that? As simply copying the .pages and .components file won't work due to changes in component ID.
Please suggest approach to achieve this.

Thanks.

Find more posts tagged with

Comments

santosh013

Hi All,

We are using TS 7.2.1, SitePublisher and developed components and pages.

We have to make our development server in sync with Production server. How can we do that? As simply copying the .pages and .components file won't work due to changes in component ID.
Please suggest approach to achieve this.

Thanks.

Check here to get some pointer.

HTH.

Bowker

Are you trying to migrate your content contribution side (TeamSite/SitePublisher) or the presentation side (LiveSite Runtime) from prod to a "lesser" environment?

We too will be facing the same issue shortly since the Powers That Be would like to have another Integration testing area for our LiveSite Runtime environment.

I know that deploying everything from TeamSite/SitePublisher is supposed to work, but in some cases the content in TS/SP it's not consistent (Whoops).

interDev

I know that deploying everything from TeamSite/SitePublisher is supposed to work, but in some cases the content in TS/SP it's not consistent (Whoops).

How is it supposed to work? Are you saying deployment through Opendeploy or something else?
Will deploying everything from TeamSite/SitePublisher server A to server B also set the extended attributes etc. on server B as well? How will the page IDs, component IDs be in sync? Versioning info is also present in EAs, will the version numbers be also changed automatically on server B?

Kapil_sape

Hi,

Thanks for your quick replies.
We have to migrate content contribution side i.e. (TeamSite/SitePublisher). So, do you think it can be achieved via OpenDeploy. Will it be mainting all the components ID among components and its .page file?
Can it be achieved by .spar file [as I am not very much aware about .spar]

Thanks,

Bowker

If you want an exact copy of the whole backing store you can use XCOPY to copy from one server to another. We just did this a few weeks ago when we migrated from old hardware.

If you want to limit what you copy to specific branches you can use iwmigrate.

As for the databases, let's hope you are doing a total copy, then a BCP out and BCP back in might work.

nipper

You have several choices.

The manual suggests building a SPAR, that is talked about in the SP Dev manual.

I tend to manually copy components from Dev to Prod as they *tend* to be one at a time. Get latest on templates and pages from those.

I also have a deployment with 2 filelists (with EA and without EA), I put what I want in there (or the root folders) and run.

When you have 25K files in TS and only need to push 2-3 K with EA, it makes significant sense to split them

Now you also have to consider that you should *seldom* push content from Dev to Prod. On initial setup of course, but you always risk overwriting existing content. One of my customers had a process designed by a consulting firm that guaranteed content would be lost. And the process followed up on that guarantee quite often. I did a week system check and spotted that design flaw in about 15 minutes.