Workarea copy from server to server

Does anyone know what is the best way to copy/synchonize a workarea from one TeamSite server to another? Both servers running TS 5.5.2 SP2 on Windows 2000. We are in the process of setting up our Development server and would like to make a copy of certain Production server workareas onto the development server on a nightly basis to have access to current content when testing new functionality. The plan is to have a Dev workarea and then a Prod branch and workarea in Development. The Prod workarea wouldn't be used for anything but having access to a snapshot of what is currently in Production. The iwcpwa.exe CLT only appears to be for copying workares from Pre-5.5 servers. The only way I could think of doing it is deploying between servers and then running a DNR to copy the extended attributes.

Anyone else have any ideas?

Sebouh

Find more posts tagged with

Comments

Jeremy

Hi,

Just a thought, what about using iwmigrate? This can be used to copy a backing store from one server to another. Obviously you don't want the entire backing store, but you can specify a singly Branch.
Not sure if it would meet your requirements but just throwing some other ideas out there.
Good luck.

Jeremy

Migrateduser

Jeremy,

Thanks, but if it works like iwconvert.exe worked for upgrading, the target backing store can't be mounted when the actual migration is done.

Sebouh

MattP

Deployment is probably the best way. I may be wrong, but I thought it would keep the EAs?

Otherwise, this is the manual approach (ugh)

On the old machine, backup the extended attributes from each original branch using the attached script:
(1 line):

\iw-home\bin\iw-perl\iwperl saveattr.ipl Y:\default\main\origbranch\WORKAREA\XFER > C:\TEMP\saved_attributes.txt

Then transfer the content on the old machine in the Workarea XFER on each branch to the corresponding branch/workarea on the new machine.

Reapply the extended attributes:
(1 line):

\iw-home\bin\iw-perl\iwperl setattr.ipl < C:\TEMP\saved_attributes.txt

You need to bring the saved_attributes.txt file from the old machine to the new.

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Jeremy

True, and I am guesing having to do a reboot of the machine each day to get the Y: back is not an option.

Oh well - then I guess your idea of the DnR option is pretty good.
You would have to run a script before hand to get all the extended attributes, then deploy all the files, including the file storing the EA's and then run a DnR script to set them again.

Hope it all works!

Migrateduser

I just checked with an OpenDeploy person, he says:
Use a pre-deployment DNR to extract EAs and a post-deployment DNR to write the EAs.

Hopefully a future OD version will handle this automagically!

lissa

MattP

Lissa/Todd -
Have you logged this as a feature request? Those in favor should express interest...

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Migrateduser

Its an expensive solution but if you got the doe, why not.. If you happened to have network storage such as network appliance you can snap mirror the backingstore to the other teamsite server mounted to a network storage with minimal downtime. Or you can simply use rsync.

Using OD to deploy is another viable solution but getting those extended attribute can be tricky. I have it done it before on a entire branch, it just took a while.

Adam Stoller

The NetApp approach for the backing store will handle both content and metadata.
rsync will only handle the content
OpenDeploy with DNRs will handle both content and metadata (as has already been mentioned, a future version of OpenDeploy should provide this capability internally)

--fish
(Interwoven Senior Technical Consultant)