Moving a branch from 1 TS partition to another and closing the partition

Hello,
just wondered if anyone has tried to do this.

I've inherited a TeamSite (7.3.2 now) with 3 partitions (i.e. /iwmnt nfs mounts).

Q1) My understanding is that TeamSite is licenced per "content store" - which I assume means partition. Will it cost us less to have only 1 partition (default)? (Soon there will be only 1 functioning branch in the 2 extra partitions combined, so no need for them really).

Q2) I think I know the answer to this, but I don't believe there is any way to move a branch lock stock and barrel from 1 partition to another, so is the best way to populate a new branch in the default partition from 1 in another partition just to use iwupdate into a workarea (or maybe OD)?
(Have never tried that across partitions, and I'm assuming there will be no way to keep our versions).

Q3) If I succeed in moving the branch in to default, is it an easy matter to remove the 2 unneeded partitions?
I've heard of people who have partitioned their store (although I haven't done it), but I've never heard of anyone who has de-partitioned.
p.s. I believe I need to run iwstoreadm -d [store], but I believe it deactivates rather than deletes - wonder if we will still get charged....

Will be interested to hear from anyone who has been through this, or investigated the possibility.

Cheers
HF

Find more posts tagged with

Comments

Rick Poulin

Q1) My understanding is that TeamSite is licenced per "content store" - which I assume means partition.
That's true. However, it may not be "that easy" to alter your contract with the vendor unless you're about to renew. You might want to have a discussion with your HP rep before bothering with any of this work.

Q2) I think I know the answer to this, but I don't believe there is any way to move a branch lock stock and barrel from 1 partition to another
Not true. You can use the iwmigrate CLT to copy the branch with its entire version history, permissions, role assignments, etc. from one store to another on the same server.

Q3) If I succeed in moving the branch in to default, is it an easy matter to remove the 2 unneeded partitions?
Use the iwstoreadm CLT to "deactivate" (unmount) the store. You can then move/backup/delete the corresponding folder under `iwgetlocation iwstore` at your leisure.

PS. You should stick to calling them "content stores". They are not true partitions even though they might look like they are, so use of that term can lead to quite a bit of confusion.

HurricanesFan

Q1) My understanding is that TeamSite is licenced per "content store" - which I assume means partition.
That's true. However, it may not be "that easy" to alter your contract with the vendor unless you're about to renew. You might want to have a discussion with your HP rep before bothering with any of this work.

Q2) I think I know the answer to this, but I don't believe there is any way to move a branch lock stock and barrel from 1 partition to another
Not true. You can use the iwmigrate CLT to copy the branch with its entire version history, permissions, role assignments, etc. from one store to another on the same server.

Q3) If I succeed in moving the branch in to default, is it an easy matter to remove the 2 unneeded partitions?
This is what the iwstoreadm CLT does.

PS. You should stick to calling them "content stores". They are not true partitions even though they might look like they are, so use of that term can lead to quite a bit of confusion.

Thanks rpoulin,

Q1) Yes a renewal is coming up in < 2 months, so this is a good time. Interested to see how much money we will save with this.

Q2) iwmigrate, got it. You know I actually created a Support ticket a while back enquiring if I could move a branch down a level (within same store) and asked if I could use iwmigrate for that. I was told no, is it only inter-store rather than intra-store?
Note to self, back up first...

Q3) I found iwstoreadm -d after I wrote that but I note it deactivates rather than deletes. Wonder if we will still get charged...

Cheers
HF

nipper

There is a difference from what you have paid for and what you are using. You can check your license (TS.lic) to see how many stores you are allowed. BTW, the admin store does not count so you are likely using two.

Now if you paid for 2 and only need 1, they won't give you money back but maybe will drop some of the maintenance

Now if you paid for 1 and have been using 2 then you are out of compliance and could get charged for it.

HurricanesFan

There is a difference from what you have paid for and what you are using. You can check your license (TS.lic) to see how many stores you are allowed. BTW, the admin store does not count so you are likely using two.

Now if you paid for 2 and only need 1, they won't give you money back but maybe will drop some of the maintenance

Now if you paid for 1 and have been using 2 then you are out of compliance and could get charged for it.

Nipper,
I'm wise to the iwadmin store. Not counting that, we have paid for 3 and are using 3. But we really only need 1, not sure why we decided on 3 - they are all being backed-up at the same time, don't what other justification for them there is.

Not likely to save money going from 3 -> 1? We would probably try to use it as leverage to, say, swap a Dev server to a Standby.

p.s. we still haven't gone live with 732 version yet, so I am now thinking I could try the iwmigrate/iwstoreadm -d procedure before going live and if I run into problems all I have to do is re-load the backing store so there is no risk.

Adam Stoller

Note - after running iwmigrate to consolidate the stores - remember to run iwfsshrink on the resulting single store to remove redundant data (iwmigrate will cause the redundant data - so running iwfsshrink on the individual stores before running iwmigrate will not help)

Rick Poulin

You know I actually created a Support ticket a while back enquiring if I could move a branch down a level (within same store) and asked if I could use iwmigrate for that. I was told no, is it only inter-store rather than intra-store?

That's kinda true. What you could do is create a copy of the store and then move /storename/main/parent/branch to /storecopy/main/branch and then replace storename with storecopy (via a combination of iwstoreadm and moving around the content stores on the file system). Should work just fine, assuming you've kicked out all the users before you do this.