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 Migration

Baskett

I need some information on how to migrate a backing store on an old box to a backing store on a new box, both with Unix operating systems and different IPs.

We are currently in the process of creating a new production environment for our production team and have a fresh install of TeamSite on a new box. I would like to move a copy of the backing store from the old box to the new environment without loosing any permissions or DCR/HTML associations in the process. Any suggestions?

The old system is running 6.1 and the new system is running 6.5.

Find more posts tagged with

Comments

nipper

Should be pretty easy.

If you can set up an NFS mount (with root access specified)

use tar to move the directory

something like:

cd /old_iwstore; tar cf - | (cd /new_iwstore; tar xfBp -)

That will preserve the permissions.

Andy

Adam Stoller

cd /old_iwstore; 
tar cf - | (cd /new_iwstore; tar xfBp -)

You forgot the . for the current directory on creation
Don't you want the p on both sides of the pipe?
I'm not sure you need the B option as I believe that's the default when reading from STDIN.

So - I think it's:
tar -cpf - . | (cd /new_iwstore; tar -xpf -)
or - if you like verbosity
tar -cvpf - . | (cd /new_iwstore; tar -xvpf -)

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

Baskett

My UNIX Admin. already tried out the tar option and it did keep the original permissions, but TeamSite no longer associates my DCRs (xml) with a DCT (do not open in templating). In addition, the DCRs are no longer associated with the generated HTML files. Suggestions?

gzevin

your admin has probably tar'ed not the physical store, but rather the filesystem mount - which does not preserve Extended Attributes.

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

iwovGraduate

Just making sure -
Did you copy over (tar) iw-store directory (i.e. the backing store itself) or files in your workarea to the new store ?

Use the iwextattr command on the DCR and see what attributes are set - on the original server and copmare with the new server.

nipper

Fish,

Yes you are correct about missing the period for current directory.

I thought you still need the B
B Block. Force tar to perform multiple reads (if neces-
sary) to read exactly enough bytes to fill a block.
This function modifier enables tar to work across the
Ethernet, since pipes and sockets return partial
blocks even when more data is coming. When reading
from standard input, '-', this function modifier is
selected by default to ensure that tar can recover
from short reads.

and no, you only need -p on extract.

p Restore the named files to their original modes, and
ACLs if applicable, ignoring the present umask(1).
This is the default behavior if invoked as super-user
with the x function letter specified. If super-user,
SETUID and sticky information are also extracted, and
files are restored with their original owners and per-
missions, rather than owned by root. When this func-
tion modifier is used with the c function, ACLs are
created in the tarfile along with other information.
Errors will occur when a tarfile with ACLs is
extracted by previous versions of tar.

So, Ghoti, rtfm

Adam Stoller

Yes you are correct about missing the period for current directory.

I thought you still need the B B Block. Force tar to perform multiple reads (if necessary) to read exactly enough bytes to fill a block. This function modifier enables tar to work across the Ethernet, since pipes and sockets return partial blocks even when more data is coming. When reading from standard input, '-', this function modifier is selected by default to ensure that tar can recover from short reads.and no, you only need -p on extract.p Restore the named files to their original modes, and ACLs if applicable, ignoring the present umask(1). This is the default behavior if invoked as super-user with the x function letter specified. If super-user, SETUID and sticky information are also extracted, and files are restored with their original owners and permissions, rather than owned by root. When this function modifier is used with the c function, ACLs are created in the tarfile along with other information. Errors will occur when a tarfile with ACLs is extracted by previous versions of tar.So, Ghoti, rtfm

I did - did you? ;-)

The 'B' flag is provided by default when reading from STDIN
If you want the ACLs recorded from the source side (so they can be used on the target side) you need to include the 'p' flag during creation

Perhaps we just interpret the FM differently?

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

gzevin

Hi Andy,

myself and Stephen think that you should come back over here.. too much fun, while you are arguing over tar

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

nipper

Actually Ghoti, I use the example in tar copying directories:

If the name of the tarfile is '-',
tar writes to the standard output or reads from the
standard input, whichever is appropriate. tar can be
used as the head or tail of a pipeline. tar can also
be used to move hierarchies with the command:

example% cd fromdir; tar cf - .| (cd todir; tar xfBp -)

Sun has not changed this since i first used it in 1990, so it may be inaccurate.

Bt I did get it out of the FM.

Adam Stoller

Okay - I'll grant you the example is from the man page - but so is the text - and the two don't seem to jive except for the fact that if the B is optional - it doesn't matter whether it's there or not. However, I remain convinced that for what was being asked - you'd want the 'p' flag on *both* sides of the pipe.

(like you thought Interwoven cornered the market on questionable documentation? ;-)

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