Backing Store Issue after TS 6.1 Solaris Install

System

G'day All -
I've got a support case going on this also, but I thought I'd cover all bases by posting here.

I was running 6.0 TS on Solaris on my dev server and attempted the 6.1 upgrade. It didn't work correctly for me. I tried fixing the issue unsuccesssfully and things got worse from there. At some point, I decided it would be better to do a fresh install of TS rather than attempt to fix the upgrade.

In preparation for this, I saved off the Backing Store that I'd been working with in 6.0. I did this by executing the following command:
> mv iw-store iw-store_bak

Then, I successfully performed the fresh install of 6.1. It created a new backing store at /iw-store. I stopped TeamSite and all associated processes then tried to swap in the backed up Backing Store:
> mv iw-store iw-store_new (move the freshly created backing store to another directory)
> mv iw-store_bak iw_store (move the previously backed up backing store back into production)
and then restarted TeamSite.

TeamSite came up fine, but now it doesn't recognize the contents within the 'old' backing store. It only shows the initial branch as if it were a brand new backing store. None of the content is showing up. In the TS Admin interface, the server status shows the correct disk space usage as if all of the content and branches exist, but TS isn't seeing them.

I've attempted to use the Admin CLTs: They recognize the store as in production. I've deactivated and readded the store successfully (according to the CLT feedback). Still no content.

Permissions all seem OK at the file level.

Here's one issue I see as a possible clue:
When I run the diagnostics tool against TS with the 'old' backing store in place, I get the message during execution:
It appears as though Teamsite is not running
or the mount point is unavailable. This means
some values will not be present in the output
so it appears that the diagnostic tool can't correctly find the content either. I've sent the truss output associated with the running of this portion of the diagnostics tool and they're taking a look.

One thing I'm hesitant to do is to add a new branch to the 'old' backing store, as I don't want to introduce any corruption.

Ideas? Suggestions? All are appreciated!

Thanks,
Wally Box
Nike, Inc.