[notes_pclp]

In the past I managed 20 Domino BES servers and had them on a two week reboot schedule that worked well.

I am now working with a brand new Exchange 5.0.1 4 BES environment and trying to plan a reboot schedule. Each BES will host around 1250 users.

Curious what other Exchange BES admins do in regards to scheduled reboots, weekly, monthly, never?

If you reply please indicate the # of users, needless to say a BES with 20 users might could go for months, 2000 users might be a weekly/bi weekly reboot.

Thanks

[knottyrope]

I only reboot BES when updates are done on DC, GC, Exchange or SQL.

Only once in a great while is a reboot needed for a particular issue.

We lose power about every 4 months and every server is turned off usually.
I have to restart BES since it usually boots before exchange does.

[TargetIT]

I reboot once a week and always after the Exchange WSUS update window. Seem to have less issues since I started doing that so I stuck with it as no one would know that the service is unavailable for a couple of minutes at 3 in the morning.

[Flipg123]

We reboot once a month with 705 users.

[tduffy]

Once a month due to Microsoft patches. If there wasn't patches to install, it would never get rebooted.

[x14]

Whenever the server misbehave.

[Wiseass]

I've not rebooted since Oct when we moved it to the company we outsourced management to.

I've got about 350 users on a Domino 6.5.6 box...I'd love to get some maintenance time/regular restarts but upper management doesn't want to have to deal with the downtime....wtf...we got an outsourcing company to manage our servers so I don't have to be up at 4am to do the restart...let them handle it!

[raindownsugar]

I used to have to restart basically do to my own lack of knowledge as to what was happening with the server but we've got things ironed out (GroupWise shop) and I can troubleshoot the services better than I used to. We restart only after Windows updates requires a restart. We do have a batch job that restarts the Controller every sunday morning. We do this as the SQL instance we use undergoes maintenance in the wee hours that day and for some reason that process often kicks us out of the db and the BES does not recover.

[cyclmpc]

1000 users and only if there are any WSUS update.

[Sp1d3rM@n]

I have almost 10,000 BB users in 6 different BES environments of various versions to content with. Generally our reboots are timed with patches or ocasionally due to issues with GCs or Exchange, but we tend to do more restarting of services that are affected if possible. And it depends on the version too. For instance with 1 remaining BES v4.0.7.11 environment with ~2000 users on 3 servers. Generally the only issue I have is with cert lookups and so I schedule a restart of the MDS that has taken care of it... Nosuch issue with the 4.1.6.23 or the 5.0.1.30 environment, but they have their own other occasional issues.

[freakinvibe]

Only for monthly MS patches and if DC/Exchange hickup. 200 users. 4.1.6

[m4ilm4n]

Only if an OS patch requires it, and even then I'll delay that until I'm sure it won't impact operations. Only 65 users on Domino 8.5 with BES 4.1.6, but it's been rock solid.

[juwaack68]

Only if I have to reboot - no schedule.

[RichieRichR6]

Weekly scheduled reboot during the very early morning hours.