Teamsite instabilities

Hi,

I was just wondering if anyone has experienced persistant backing store corruptions on TS 5.0 on NT4.
This has been going on for us for a number of months and no ammount of iwfsck -d and iwfsfix's can stop these corruptions from occuring.
Examples are corrupted files and branches. Disappearing DCRs, teamsite crashes etc.
I know the best solution is to upgrade, which we are doing, but was wondering if anyone had any thoughts as to whether this is an inherent problem in the old backing store architecture or whether its just NT not coping with the millions of little files created by TS?

Rgds,
Chico

Francis Pacheco
www.t-zones.co.uk

Find more posts tagged with

Comments

Migrateduser

There is not really enough information in your post to advise you whether you are at the limits of 5.0 or not. How many branches do you have, how many files are being changed, how many users are on the system, etc. We have had hundreds of customers successfully use 5.0....What version of 5.0 are we talking about?

NT 4.0 was the most-current OpSys from MS when TS 5.0 came out, so it should not necessarily be a problem.

You can either give more information in this post, qualifying the scope of your TS usage, or you should consider opening a support case so someone can work more closely with you.

However, you are correct that upgrading is probably the right longer-term solution. If you have a development server, you could put 5.5.2 SP3 up on it, and move your customizations on top, and see how they perform.

Are you in production now, or in test?

lissa

Bryan_K

We ran 5.0 on Win2k and had no end to our problems. These included backing store corruption and service interruptions. Fortunately IW and their staff were extremely helpful in getting us to a stable environment. We have since upgraded to 5.5.2 with no SP and we have been up for 4-5 months with no issues.

ToriC

We also had and continue to have numerous backing store corruption issues with TS 5.0.1,5.0.2 and have not been able to resolve them after numerous attempts. We are upgrading to 5.5.2 in a few months and we are not migrating the backing store in the hope that all of our backing store issues will be left behind.

Adam Stoller

Backing store corruptions are a serious problem - if you encounter something that you believe to be indicative of backing store corruption - PLEASE - contact Interwoven support *before* attempting to fix it yourself. It is much better to have someone work through the steps with you - especially folks who have been through this before and who have access to other resources should the need arise.

Having just been with a customer who let this go too long before attempting to fix it (in 4.5.1), and who had to essentially take a cut from their existing backing store (from editions, and in some cases directly from their production servers) - I can assure you that it isn't a great position to be in (for either party).

The earlier the problem is detected (using iwfsck -d periodically) the more easily the problem can be corrected with little-to-no loss of data.

The longer it persists, and improper processes used for attempting to resolve it - the more likely that data will be irretrievably lost and downtime will be increased while trying to fix the situation like I just worked through with my customer (with assistance from Interwoven Support - yes, we use them too).

--fish
(Interwoven Senior Technical Consultant)

doctypes.doc