At Admin2008 this year, in a few sessions, the speakers were talking about various Domino server tasks and how long it takes to run them.

In one session, a question came up about NSD's (when the Domino server crashes). The speakers (I think it was Francie and Paul) asked for a show of hands with the longest time it took to get NSD to run and finish. Someone in the crowd said six hours.

A few weeks ago, I was onsite and had to run compact on a corrupt database while the server was down. It took FOUR HOURS for one database. Just as we stood near the server to start to discuss "our options", it finished.

So, just when you think the tasks are hanging, it's always good to just let them finish! I need this reminder every once in awhile, too. Four hours? Yeesh.

So let's hear it. NSDs, fixup, compact, updall, agent, etc. What's the longest task you've ever seen run that you thought for SURE it was hung, but it really wasn't?

Jess

1. Tim Lorge05/12/2008 10:15:28 AM
Homepage: http://www.groupwarenews.com

My most memorable is client I had a few years ago whose backup was taking upwards of 22 hours to complete because they didn't remove the source server from a cluster during the backup nor did they reschedule any of the default tasks during backup time. Once they adjusted them, the backup finished in about 8 hours.

---

2. Randy Smith05/14/2008 01:17:21 PM
Homepage: http://www.certprimer.com

For the domidx (Domain Indexer) task you typically don't use "hours" as a unit of measure -- you use "days" instead (many, many days in some cases).

---