upgrade from Teamsite 6.5 to Teamsite 7.1

hi

Check for upgrade from Teamsite 6.5 to Teamsite 7.1 (How is it done and how complex is this task; how much time can it take and what are the major dependencies)

Find more posts tagged with

Comments

IronFace

Likely a hope from 6.5 to 6.7.2 SP2 to 7.x.
Time: Lots
Complexity: High
Cost: Lots

Note: You will likely face a request from your boss that goes something like this:

Boss: How long for the upgrade?

You: After research and planning the resources, 6-8 weeks

Boss: 6-8 weeks? Are you crazy? We have 4 weeks maximum.

You: Yes, but with each installation, we should run through our entire (and very manual) test suite before and after the installation, each run taking a week X 5 testers. This is a must, in order to identify deprecated functions, broken code, etc. And in doing so, we're likely to uncover issues which will need to be addresses, the bucket of which is in the 6-8 week estimate as "fix - 1 week). And boss, this estimate could, and likely will, go up based on our findings during the testing.

Boss: (blank look on face). How long will it take with minimal testing?

You: Minimal?

Boss: Yeah, as in none. I mean, it should just work, shouldn't it? Besides, that 6-8 week estimate... you're just padding the numbers, aren't you?

And then reality hits Boss in the face and kills him.

IronFace

Boss talk, part #2:

Boss: I've reviewed your schedule. The part where you have "Install OpenDeploy", and then later, you have "Install TeamSite", I think you should do those at the same time.

You: Uhhhh... bu..

Boss: (interrupting) And what's this block for "Documentation". Doesn't the vendor provide clear and understandable documentation?

You: (containing laugh) Clearly, you've never been on the support site and attempted to download documentation from them. The links returned are great, but whenever you click on a link to get hold of a document, a 404 not found error is the likeliest of outcomes.

Boss: But..

You: And if you're lucky enough to find a document, chances are that it really was written by an infinite number of monkeys on an infinite number of typewriters, all powered by IDOL. The document is great, we just can't find it.

Out!

Adam Stoller

hi

Check for upgrade from Teamsite 6.5 to Teamsite 7.1 (How is it done and how complex is this task; how much time can it take and what are the major dependencies)

The same server or a new server?

For the same server - you've already gotten some semi-tounge-in-cheek (though reasonably accurate) responses.

For a new server you can cut out the middle release:

All told - this will probably still be on the order of 3-to-5 weeks (assuming proper skills and diligence)

ccprofessional

For a new server you can cut out the middle release:

Boss: Let's do this on a new server - and cut our upgrade time

You: Great idea boss. Do we have a temporary license to do that?

Boss: I'm sure our very friendly sales guy can give us one. Let me talk to him today.

... a couple of days later..

You: Boss, do we have the new license yet?

Boss: our sales guy is not returning my calls.

You: [check linkedin, and find out the sales guy has left and joined Adobe].. Boss, he's gone

Boss: gone? where? ...
[a week or two pass by]

Everyone: Do we have the temporary license to upgrade?

Boss: They want 50 grand (US dollars, not Indian rupees) for the temporary license. WTF?!

[5 weeks later]

You: Boss, I ran the installer over night and upgraded TeamSite on our dev environment. And it looks fine.

Boss: Great job Saravanorvelarekkashekarovan! Let me go and talk to my boss and say it's all taken care of...

You: But.. But .. its on dev, and I have not tested.....

Ok, someone else can continue this

Adam Stoller

Boss: Let's do this on a new server - and cut our upgrade time

You: Great idea boss. Do we have a temporary license to do that?

...

I'm not 100% positive, but I think all the IWOV products now provide a grace period (1 week?) before they require a valid license - also, from my experience, you can go through Support or Support Admin, explain what you are doing and obtain a temporary license with little to no hassle.

True, the OOTB 1-week grace period (if I'm right) isn't generally sufficient for the task being discussed, and even if you obtain a temporary (1 month?) license, you're still dealing with a month-long (+/-) intensive project.

nipper

I'm not 100% positive, but I think all the IWOV products now provide a grace period (1 week?) before they require a valid license - also, from my experience, you can go through Support or Support Admin, explain what you are doing and obtain a temporary license with little to no hassle.

True, the OOTB 1-week grace period (if I'm right) isn't generally sufficient for the task being discussed, and even if you obtain a temporary (1 month?) license, you're still dealing with a month-long (+/-) intensive project.

TS has a 2 day license. You can also generate a license and they will make it a 30 day license (until you call support and tell them you have deactivated another server)

ccprofessional

You can also generate a license and they will make it a 30 day license

I would be careful about following this advice. If your organization does not follow the proper channels to procure the contractual license before generating a technical license, you could be in non-compliance and therefore subject to legal ramifications.

Maybe I understood your comment wrong Andy, but as I understand, what you suggested can be risky.

nipper

I would be careful about following this advice. If your organization does not follow the proper channels to procure the contractual license before generating a technical license, you could be in non-compliance and therefore subject to legal ramifications.

Maybe I understood your comment wrong Andy, but as I understand, what you suggested can be risky.

Understood. From my experience, if you are licensed for 2 servers and try to generate a third, the system will automatically make it a 30 day license. May not be the official policy but that is my experience.

Worst thing that can happen if you generate an out of compliance license is a compliance audit. So if a permanent license was generated, then you need to email support with the details of what server is being taken out and what is going in.

Migrateduser

Hi,

We have a 6.7.2. TeamSite serevr that needs to have its store moved to a 7.3.2 server before we decomission it.

I am attempting to migrate the content.
According to most of the advice I have seen (e.g. ghoti below) you should copy the store fist to the new server before the doing an iwmigrate.
Question. copy? how?
Before getting into size, transfer time issues, what progarms commands are we talking about? A simple OS copy? and from which point? The Y: drive storename? the physical drive storename? and where to? the root of a new store?
And will we not loose all our version information this way?

Much thanks in advance

bemused

/Nick

[QUOTE=ghoti]The same server or a new server?

For the same server - you've already gotten some semi-tounge-in-cheek (though reasonably accurate) responses.

For a new server you can cut out the middle release:

nipper

xcopy is the most likely DOS based tool

Adam Stoller

Question. copy? how?

As nipper already pointed out, xcopy is the usual means on Windows, though any CLT or application that allows for copying the files is probably fine, including OpenDeploy.

and from which point? The Y: drive storename? the physical drive storename?

You want to copy the actual backing store, not the virtual mount point - so something like c:\iw-store\default should work I believe, though certainly copying all of c:\iw-store would be fine too.
In both cases, however, ....

and where to? the root of a new store?

If you copy c:\iw-store\default from one server to c:\iw-store on another server, you would need to specify the target directory as being something like "old_default" to avoid overriding the already existing "default" directory on the target server. The other option (and certainly the case if you were copying over the entire store tree) would be to locate it somewhere else entirely (e.g.: c:\old_store\default)
You can set things up in iw.cfg to mount the old store information as a [temporary] second store and/or utilize the iwstoreadm CLT

And will we not loose all our version information this way?

No - if you are bringing over the entire store you don't lose anything - though if you choose not to migrate all the editions from the old store, then you may lose some historical information in the target location.