Migrate content between servers

We've developed a new branch on a development server and are ready to migrate to the production server. How can I do this while maintaining permissions, ownerships, extended attributes, etc?

We're running TS5.5.2SP3 on Solaris.

Find more posts tagged with

Comments

iwovGraduate

Read documentation on migrating backing store or upgrades available on support site. See CLTs like "iwmigrate" etc.

gzevin

from my own experience - if you are not concerned about staging area of the test envirinment (and/or editions) - what you do is just do the following

tar the branch on the workarea level
capture EAs using saveattr.ipl script (I think it's available in the tech lib)
create branch with appropriate permissions on the production box
untar the tar file
re-attach EAs using setattr.ipl
start development

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

skip11

Hi,

If you use Gregs methodology (which we use to the letter here) make sure you use the "p" switch to tar,
which will perserve the permissions on the files:

tar -cvpf some-branch.tar .

tar -xvpf some-branch.tar

Regards

Ralph Barger
CSFS TOP
Zürich

nipper

You may want to use Open Deploy. We did, since I had 20GB of content, tarring it up & ftping it
is a serious pain.

BTW, if you have the ability to rsh you can do something like:

cd /iwmnt/default/main/branch/WORKAREA/workarea; tar cf . - | rsh server (cd /iwmnt/default/main/branch/WORKAREA/workarea; tar xfBp -)

That will pass the tar via stdio which would be much faster than saving to disk and ftping.

Andy

ts_user

We had to work through a similar scenario where we had to migrate from production branch to test server branch to develop new templates. Opendeploy was the easiest option we found to migrate content and then use saveattr.ipl and setattr.ipl scripts to set the extended attributes. You can use non-transactional deployment to decrease to avoid the extra overhead as you can always use the log files to check if deployment completed successfully. Correct me if I am wrong, but iwmigrate does not migrate to an already existing backing store.

bagman

Thanks to all who responded...

I checked out iwmigrate and just didn't feel comfortable about exactlly what it did and how it did it, but found info on the saveattr and setattr which worked perfectly.

gzevin

I heard that OD 6 will deploy EAs as well... should try

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

rodigz

Hi there,
question? If I use the steps mentioned will the datacapture and tpl files will be included? Meaning it copy also the files in the new server? If yes. Is there a way not include.?
thanks

Adam Stoller

If you use *which* of the steps mentioned?
If you don't explicitly *exclude* those files, then they will probably be copied over too.
If the intent is to migrate templated files to a new server and to preserve the ability for those files to be interpreted correctly - you probably need the DCTs and PTs to be copied over as well - unless you have some other means of providing that information on the new server that you don't wish to overwrite when copying over the DCRs - in which case you're back to making sure you explicitly exclude them from the deployment or tar files or whatever mechanism you use to transfer all files between servers.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com