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 question

System

I made a new edition and used iwmigrate to migrate my content to a new backing store location on the same server. My reason for doing this is that my original backing store is extremly corrupted on one of the branches and unfixable.

I want to be able to have the new backing store look identical to the old one (jobs, tasks, and unsubmitted files also need to come over)

What's the best way to copy over the jobs?
- do I copy the workflow folder from the original store folder over to the new one, there are two workflow folders in the iw-store folder (workflow and workflow.4107897129), should I copy both

How do I move over the files that are currently not in staging (new or unsubmitted) and retain their locks, and original status?

Find more posts tagged with

Comments

Adam Stoller

I made a new edition and used iwmigrate to migrate my content to a new backing store location on the same server. My reason for doing this is that my original backing store is extremly corrupted on one of the branches and unfixable.

I want to be able to have the new backing store look identical to the old one (jobs, tasks, and unsubmitted files also need to come over)

What's the best way to copy over the jobs?
- do I copy the workflow folder from the original store folder over to the new one, there are two workflow folders in the iw-store folder (workflow and workflow.4107897129), should I copy both

How do I move over the files that are currently not in staging (new or unsubmitted) and retain their locks, and original status?

Are you saying that you're planning to delete your old store after the migration?

If so - you should only be blowing away the actual store (e.g. 'default') not the store directory tree (e.g. /iw-store, or c:\iw-store) - the workflow information is kept in a separate store but if you're playing around with files that are in one store and are attached to the workflow you will likely run into problems. You *might* be able to migrate the edition, remove the old store, re-migrate the edition back to the default store (remove the temporary second store) and things *might* work out okay.

With respect to modified files in the workarea - you'll have to copy those by hand from one store to the next - but if you're going to migrate it back into place after removing the old / corrupt store - you should probably just create a tar / zip file of the modifications and record all the information about locks and such - and wait until you've re-migrated the content back into the (new) default store before applying them. iwmigrate only migrates editions - not workareas.

Migrateduser

Are you saying that you're planning to delete your old store after the migration?

Yes

It would be even better if I was able to do a View\Modified to select all the files in the old store and then do a copy to from the new store . Then, when all is said and done, I could delete the old default store from the iw-store location and then copying the new store into the old default store's location. Then rename the new store to default. But, that's probably not possible. I would think that would screw up alot of pointers and stuff, but then again maybe not.

Adam Stoller

Yes

It would be even better if I was able to do a View\Modified to select all the files in the old store and then do a copy to from the new store . Then, when all is said and done, I could delete the old default store from the iw-store location and then copying the new store into the old default store's location. Then rename the new store to default. But, that's probably not possible. I would think that would screw up alot of pointers and stuff, but then again maybe not.

At this point - I'm not sure what you're asking, nor what you are attempting to do.

I suggest you re-collect your thoughts and try to itemize them in a step-by-step fashion to indicate (in a fair amount of detail) what you intend to do and where you have questions about it.

Migrateduser

Goal - make new backing store from current corrupted backing store, retain the exact path (\default\main\....), all jobs, tasks, unsubmitted content, locks, etc

I suppose I could do the following using one server. (this is getting messy) I could also do it without as many steps using two servers.

make a new edition for each branch
run iwmigrate and create a default_new store
start up both stores (default and default_new)
submit everything
copy everything over all the changed or new files that I need from default to default_new so that the default_new mimics the old store.
shutdown the old store (default), rename iw-store to iw-store-old or delete it all together
run iwmigrate and create a third store called "default" from default_new
start up the default_new store and the new "default" store
submit everything
copy everything the changed or new files (files that aren't in staging) that I need from default_new to default so that the default mimics the old store.
shutdown default_new
start up default

This would hopefully retain all the pathing and in the end I would have my "default" store with the same paths, workflows and locks (locks probably won't come over, but that's okay)

Adam Stoller

Goal - make new backing store from current corrupted backing store, retain the exact path (\default\main\....), all jobs, tasks, unsubmitted content, locks, etc

I suppose I could do the following using one server. (this is getting messy) I could also do it without as many steps using two servers.

make a new edition for each branch
run iwmigrate and create a default_new store
start up both stores (default and default_new)
submit everything
copy everything over all the changed or new files that I need from default to default_new so that the default_new mimics the old store.
shutdown the old store (default), rename iw-store to iw-store-old or delete it all together
run iwmigrate and create a third store called "default" from default_new
start up the default_new store and the new "default" store
submit everything
copy everything the changed or new files (files that aren't in staging) that I need from default_new to default so that the default mimics the old store.
shutdown default_new
start up default

This would hopefully retain all the pathing and in the end I would have my "default" store with the same paths, workflows and locks (locks probably won't come over, but that's okay)

I'm not 100% positive about this - but here's what I would consider trying:

I have no idea whether files that were associated with workflows before the process will still be "correctly" associated with the workflows after the process - I'd suggest expecting that part not to work, and maybe you'll be pleasantly surprised.

Migrateduser

I may try that. It's the "Rename iw-store/default to iw-store/old_default" that is the uncertain area. If it works, then that would be great. I'll let you know what the outcome of this is next week when I try it.

Adam Stoller

I may try that. It's the "Rename iw-store/default to iw-store/old_default" that is the uncertain area. If it works, then that would be great. I'll let you know what the outcome of this is next week when I try it.

You may need to do a [codde]iwstoreadm -a old_default first, before bringing down TS - then remove the empty old_default store that command created and rename the existing default store into its place.

Migrateduser

An update on how my iwmigrate went, in case anyone is interested.

I used "Copy To" from the menu in CCPRO to copy everything from staging in 1st branch into a new 2nd branch, I then submited all the files in the new 2nd branch. I then made a 3rd branch, went back to the 1st, did a view list modified and used "Copy To" to copy over all the modified files to the 3rd branch. I then submitted all files in both the 2nd and 3rd branch to staging and made a new edition in 2nd and 3rd branch.
I then migrated the second and third branch over to my new store, stopped Teamsite, renamed the folders (iw-store to iw-storeold and iw-store new to iw-store) and restarted the service. I then renamed the 1st branch on the newly created store (this is the migrated contents of the 2nd branch from the old store) to the name of my original branch on the old store. I then copied everything from staging in the 2nd branch (migrated contents of 3rd branch) into the workarea of the 1st branch and was able to retain my modifed files. In the end I had both the files that were submitted to staging and the modified files with their usernames still attached. When users went into CCSTD their work in progress remained unchanged and contained the list of their files.

Notes : I made the 2nd branch in the old store out of the items from staging in the 1st branch because I didn't care about keeping history (I still have the old store and can rename the store folders and switch back at any time if needed, revisions are seldomly asked for)

I also copied over the workflow and events folders in the old iw-store folder into the new iw-store folder and the workflows worked. So far, the old workflows and tasks seem to be working properly.

Migrateduser

Another update. I found out that (could be because of the corrupted backing store I'm trying to replace) that doing a "Copy To" from Staging of one branch into a new branch was a failure and missed over 400 files. The way it missed them was random, so I scrapped my new backing store and used did an iwmigrate on the original branch (branch1 from previous post). I still used my 3rd branch which was a "Copy To" of all the changed, work in progress files. That was still successfull.