24x7 TeamSite availability. When?

System

Hi DevNetters -
I'm in a 'flame on' / 'flame off' mood today. Here goes:

---- Flame on ---------

Given the nature of the TeamSite environment, why can't there be more thought / work put into solidifying the TeamSite infrastucture and minimizing the amount of back end administration necessary to keep it up and running?

I would gladly trade any number of front-end enhancements that have been added to the product set for straightforward methods to perform:
- monitoring,
- backup,
- log file rotation
There are unresolved threads in DevNet (and in Support) on all of these going back years.

Using TeamSite as an enterprise-level application, I imagine there are lots of companies like us with users from several time zones, making it nearly impossible to freeze the backing store for extended periods of time for backups or to bounce the TeamSite process to refresh the log files.

We spend an inordinate amount of time keeping the system running smoothly - because when the system doesn't run smoothly its credibility falls with its users and we also can lose critical business functionality.

So right now, our users are happy with the functions we've implemented for them because we've spent the time to keep it going.

But what if we didn't have to spend this time on the back end? I imagine we'd have a lot more adoption and usage of the product set.

We have a very limited number of people working to support TeamSite. I imagine that's the case with many installations. With these limited resources spending time on the back end, the business-focused functions of researching and 'selling' the great potential of implementing business solutions on top of TeamSite often goes undone.

It's analogous to having a cool MGB (sorry, MG lovers..) that doesn't often get driven because the electrical, etc. systems so often need tweaking.

------ flame off ----------

That all said - what we DO implement on top of TeamSite / OpenDeploy rocks.

Comments? Additional case studies?