To multi-store or not to multi-store? and when?

Keep in mind the significant charge Interwoven charges you to add a new store. I don't know the exact number, but it is a lot of money.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

gsumers22texas

So product licensing in 5.5.2 is no longer just a function of the number of users seats and processors as in previous versions, but it now includes the number of stores as well?

can somebody from IW confirm this (not that I don't believe you Smitty Smiley Embarassed

) or is this typically something to address with account representative because it's decided on case-by-case basis?

tvaughan

My Sales rep told me $50,000 per extra backing store

That's a 5 with four zeros after it.

So, you'd better have a **** compelling reason to use it. I was going to have a:

"main/default" -- version control my IWOV source code and config files

"internet/default" -- for our 5 GB internet web site

"intranet/default" -- for our 10 GB intranet web site

"demo/defaul" -- for roadshows, etc.

Now I've just got "default/main" and $150K. The drawbacks to not splitting the backing store is just that lots of Get Latest/Submit operations probably get affecting by disk speed, which could be mitigated on different backing stores. Not to mention the fact that you can freeze your intranet backing store to do a full backup without affecting your internet backing store.

Splitting them out later may be a problem. I don't know if any of those IW conversion utilities can transfer branches between 5.5 backing stores and preserve the metadata in them.

Tom

gsumers22texas

wow
ouch

I'll paraphrase: you asked about a utility to copy a branch from one TS 5.5.2 backing store (in)to another TS 5.5.2 backing store.

There is such a utility, so they say: it's called IWMigrate, and it's documented in the Admin Guide, I think. I have NOT been able to get this utility to do what would seem to be the obvious nice-to-have of putting a branch from one TS backing store into another TS backing store. I've had DevNet dialogs and an IW Support case, but I can't get the thing to work like I think it should.

Just wanted to let you know about the existence of the utility. If you dabble and have success, let me know.

I've exchanged email with someone in engineering who would like to see the support information. Could you post the support case ID? It is trud that the purpose of iwmigrate is to migrate content from one store to another.

lissa

case 1122065

OK, I'm going to try to answer the 2 sets of questions that I think are being asked in this thread. The original question was: When might I want multistore. There is a decent white paper on the IWOV support site about this:

https://support.interwoven.com/library/manuals/teamsite/552upgrade/us_006_multistore_bp.pdf.

This paper outlines the choices people converting to 552 may wish to consider. I can also say that if the content is being owned/managed by distinct organizations, putting it in separate stores makes sense.

There is also a newly updated TS admin guide available on the support site, Chapter 7 talks about backing stores and conversion. Here's the link to the Windows admin guide:

https://support.interwoven.com/library/manuals/teamsite/pdf/552/ts.552sp3.admin.win.pdf

It is true that multistore is an optional capability, that costs extra. This is because multistore makes TeamSite far more scalable.

The second set of questions in this thread pertain to the proper usage of iwmigrate. People are interested in seeing a working example of it. I'll see if I can have someone post a functioning example here.
Regards,

lissa

I don't have a functional example - but I believe that iwmigrate is intended to be used with multi-store to migrate a specific branch (or specific editions of a specific branch) from one store to another store on the same TeamSite server. I'm not sure if it was ever intended to be used to migrate a specific branch (or specific editions of a specific branch) from one store to another store on *different* TeamSite servers ... Perhaps, but I'm just not sure if that was ever the intent.

The most compelling reason I know of for MultiStore is the ability to subdivide large (100's of gigabytes or more [terabytes]) of data across multiple stores so that backups can be done efficiently and effectively - there comes a point where trying to backup a HUGE backing store may take days, but splitting it up may allow you to accomplish the same feat in less time. Also, MultiStore allows you to only freeze *part* of your TeamSite server instead of all of it at once, so you can choose the best times for different parts of your backing store to be frozen while doing backups.

--fish
(Interwoven Senior Technical Consultant)

OK. I'm interested in the functional example of IWMigrate, and I think what I'm trying to do matches well with what's described as the original intent of the utility.

On W2K TS 5.5.2 w/SP2B, I have a 'default' store under d:\iw-store and two other stores 'newstore1' and 'newstore2' on the same server, also under d:\iw-store ('sisters' to 'default'). I can activate both additional stores, and when they're active, I can navigate them within the TS GUI -- no problem there.

Now, I'm trying to use iIWMigrate to *merge* newstore1 with newstore2. I tried:

iwmigrate -g -m d:\iw-store\newstore1 -b /main/branch_abc -o d:\iw-store\newstore2

I understand from IWOV Support (case #1122065) that "the -m (mount point) should point to a TeamSite mount point like the Y: drive," but -- aside from situating the newstore1 under iw-store, I don't know what else I can do to establish newstore1 as a TeamSite mount point. Any ideas on this?

Note that when I'm trying IWMigrate, I have newstore1 activated and newstore2 deactivated.

I do not believe that iwmigrate (or any tool currently supplied) *merges* data from different branches or stores together. iwmigrate is intended to copy N editions from a branch on store-1 to a [new] branch on store-2

--fish
(Interwoven Senior Technical Consultant)

Maybe my word choice isn't great. In fact, what I'm trying to do is place a branch from one store into a second, existing store, where the branch has no previous presence whatsoever in the target strore. I don't intend for this (or any other such utility) to merge versions of files or anything like that.

Here's the output from the last time I ran this.

Command line: iwmigrate -g -m d:\iw-store\freshness_store -b freshness/main/vanguard/internet/vanguardcom/freshness -o d:\iw-store\saf_prd_store
[Mon Jun 09 16:56:17 2003] No locale specified, using native locale for this system
[Mon Jun 09 16:56:17 2003] Converted backing store location is d:\iw-store\saf_prd_store
[Mon Jun 09 16:56:17 2003] Configured backing store on system is d:\iw-store
[Mon Jun 09 16:56:17 2003] Starting backing store environment
[Mon Jun 09 16:56:42 2003] Error locating freshness/main/vanguard/internet/vanguardcom/freshness
[Mon Jun 09 16:56:42 2003] Error opening SCI session
[Mon Jun 09 16:56:42 2003] Edition replay failed
[Mon Jun 09 16:56:42 2003]
[Mon Jun 09 16:56:42 2003] Total files/directories/symlinks copied: 0
[Mon Jun 09 16:56:42 2003]
[Mon Jun 09 16:56:42 2003] Total bytes of data copied: 0
[Mon Jun 09 16:56:42 2003]
[Mon Jun 09 16:56:42 2003] Total EA's copied: 0
[Mon Jun 09 16:56:43 2003] Shutting down backing store environment...
[Mon Jun 09 16:56:43 2003] (This may take a while because the cache must be flushed)
[Mon Jun 09 16:56:43 2003] Please wait...
[Mon Jun 09 16:56:44 2003] Shutdown of backing store environment complete.
[Mon Jun 09 16:56:44 2003] Backing store environment is shut down
[Mon Jun 09 16:56:44 2003] iwmigrate failed
[Mon Jun 09 16:56:44 2003] iwmigrate can be restarted by running
[Mon Jun 09 16:56:44 2003] "iwmigrate -o d:\iw-store\saf_prd_store/"
[Mon Jun 09 16:56:17 2003] Reading users and groups...
ERROR: no valid autoprivate file found in the current configuration (d:\iw-home\local\config\autoprivate.cfg, d:\iw-home\config\autoprivate.cfg, d:\iw-home\local\config\autoprivate.cfg) (2)
Local system: "PSNVA235"
Domain "VANGUARD" is added to the domain list, pdc="\\PSNVA951".
[Mon Jun 09 16:56:39 2003] done. 345 users and 1 groups read.
[Mon Jun 09 16:56:40 2003] Cache size: 200000
[Mon Jun 09 16:56:42 2003] TFSEnvironment: inode cache 200000
[Mon Jun 09 16:56:42 2003] Batch Jobs Thread started
[Mon Jun 09 16:56:43 2003] TEnvironment::Flush flushed 0, unlinked 0
[Mon Jun 09 16:56:43 2003] TEnvironment::Freeze freeze until Tue Jun 08 16:56:43 2004
[Mon Jun 09 16:56:43 2003] TEnvironment::dtor found 0 dirty.

Here's what I ended up doing that seemed to work:

Looks like the source store in your example is the default store. As I described in my 06/10/03 06:52 AM entry in this forum thread, I'm trying to migrate from one alternate (non-default) store into another non-default store. Both source and target stores already exist.

In your IWMigrate example, you use Y: as the source, and I think the crux of the issue for me is how to specify my source store as a switch on the IWMigrate command line.

Thanks for your help.

If you have something like y:/some-store - see if you can map another drive to it / share it - so that you can do something like -m M:\

Perhaps that will work?

--fish
(Interwoven Senior Technical Consultant)

I see a couple of problems in the command line options specified. The -m option should be Y:/freshness and the -b option should start with a '/'.

Try the following command
Command line: iwmigrate -g -m Y:\freshness -b /freshness/main/vanguard/internet/vanguardcom/freshness -o d:\iw-store\saf_prd_store

If it complains about a previously running iwmigrate then go to d:\iw-store\saf_prd_store and delete and *.restart files that might be present.

I don't have Y:\some-store. The Y: drive is the share for d:\iw-store\default. (When I go to the Y: drive at a command prompt, I see the 'main' directory, etc.) The additional stores I've made are d:\iw-store\new-store and another sister at the same level.

Maybe you're suggesting that I share

\iw-store\new-store as a drive letter. I'll have to see if I can do that.

Thanks but wouldn't what you're suggesting mean that the freshness store is really a sub-directory under the Y: drive? I don't think this is the case: Y: maps to d:\iw-store\default, and the freshness store is a sister to default, not a child of default.

Y: should not map to d:\iw-store\default

On my systems there is a Y:\default directory (and a Y:\test directory for a test store I created)

If your system has Y:\main and not Y:\default\main - then I think there is some other problem here that needs to be investigated and I'd recommend contacting Support to work with them ontrying to figure out what it is and how to resolve it.

--fish
(Interwoven Senior Technical Consultant)