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

iwmigrate timelines

rpatiban

Environment:
TS 6.5 on Windows 2003
Our iw-store is 16GB on Size and 25GB on disk space

Also, there is only one branch under main and we are going to use iwmigrate to copy the entire branch.

At this point our backingup/restoring process on iw-store, is taking at least 20 + hours each way. We are thinking to use iwmigrate to copy a branch across servers rather than copying the entire content store.

Question to who had experience in running iwmigrate: How long should we expect to run for our content size?

Please let me know if any further info is needed.

Thanks much in advance,

Raghu

Find more posts tagged with

Comments

Adam Stoller

If your intent is to replicate the backing store on another server - I'd recommend doing some form of backup-from-server1-restore-to-server2 process becaues iwmigrate will be going through the process of replaying every edition and performing all the intermediate submissions etc in order to migrate the contents of the branch - which is generally bound to take longer than copying the entire backing store data over.

However, if your intent is to only pull over the last edition on the branch (I'm assuming there are reasonably frequent editions cut on the source side - yes?) - then iwmigrate might not be too bad (not sure of an exact timing - depends on a whole bunch of variables).

If you don't care about version history - create a brand new backing store on the target server, create all the branches and workarea, and then make a tar file from the source server's staging area and bring it over to a workarea on the target server, expand it, and submit it - that will certainly be the fastest method, but it retains the least amount of data.

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

rpatiban

Thank you much Fish for your response and insight of iwmigrate command .

Our ideal way would be copying the entire store to the new server. But because of time it is taking, 20+ hours for either backing up or restoring process, we are thinking of the iwmigrate.

We have tried Robo Copy which directly copies on the mapped drive, it is still taking 22+ hours for us.
You are right. If we don't cut the number of editions to be copied to the new store, iwmigrate will be even longer than copying.
Also you are right on your assumption. We are cutting editions reasonably frequent on the source.

We have 2500+ editions at this point in our branch. As I mentioned ideally we would like to copy all the history and all the editions.
I will look into the possibility of reducing number of editions.

Thanks again,

Raghu

Adam Stoller

Is the speed problem due to the backup / restore procedure or the network between the TeamSite server and the backup system?
Have you considered seeing if you can attach an external hard-drive to the source server, do a robo-copy or xcopy or whatever to there, and then move the external hard-drive to the target server (and either just leave it there, or do a copy from there to another disk on that server?

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