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

iwupdate CLT

jude_asanka

Can I use iwupdate to transfer a file from store to store? Does this carry Extended attributes of the source file

Find more posts tagged with

Comments

kaalraa

Can I use iwupdate to transfer a file from store to store? Does this carry Extended attributes of the source file

Never tried from a store to store. However your answer to next question is YES.

Give a try and put your observation.

jude_asanka

Thank you for the reply. I tried. It syas stores are not matched.
My requirement is to trnasfer files from one store to another.
Say I have 10 editions in a store. The size of an edition is 2GB (But they contains pointers to editions then total size is not 10GB)

When I transfer those editions using iwmigrate, the target store consumes 20GB :-(

Is there a way to overcome this issue.

kaalraa

Thank you for the reply. I tried. It syas stores are not matched.
My requirement is to trnasfer files from one store to another.
Say I have 10 editions in a store. The size of an edition is 2GB (But they contains pointers to editions then total size is not 10GB)

When I transfer those editions using iwmigrate, the target store consumes 20GB :-(

Is there a way to overcome this issue.

There is something called as Incremental Migration. If you are not in need of any version history or such for files in question, you can do so forthe latest editon of source.

HTH

jude_asanka

There is something called as Incremental Migration. If you are not in need of any version history or such for files in question, you can do so forthe latest editon of source.

HTH

I think you understand my problem. I need file versioning as well. Can you give me some information on Incremental Migration

kaalraa

I think you understand my problem. I need file versioning as well. Can you give me some information on Incremental Migration

In that case, a migration of that particular branch would be the only option, as far as i know.

jude_asanka

Thank you. You said somthing about Incremental migration !!
Can you give bit of information on this.

If we transfer branch itself , then dont we get a space issue? Is it a identical copy of the same branch with versioning?

kaalraa

Thank you. You said somthing about Incremental migration !!
Can you give bit of information on this.

If we transfer branch itself , then dont we get a space issue? Is it a identical copy of the same branch with versioning?

Incremental migration could be done, in case you had migrated the edition completely and once that is done... another edition being published on source.

To update and merge the changes along with edition, you can do incremental migration.

jude_asanka

You mean to say we need to take the difference of those two editions in the source side and transfer to the destination store?

Then can we maintain the histry of files?

kaalraa

You mean to say we need to take the difference of those two editions in the source side and transfer to the destination store?

Then can we maintain the histry of files?

Yes, thats what incremental migration is to be used for.

jude_asanka

If I transfer the whole branch at once, whould this maintain my history of files? And does it resolve the space factor as well.

Adam Stoller

There is something called as Incremental Migration. If you are not in need of any version history or such for files in question, you can do so forthe latest editon of source.

HTH

What is this something called "Incremental Migration" that you speak so authoritatively about ?

Frederik

When I transfer those editions using iwmigrate, the target store consumes 20GB :-(

Is there a way to overcome this issue.

as mentioned by others, combine iwmigrate with iwfsshrink. See KB article 57161 https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57161