Based on this from
here,
The Schedule Manager server task manages busytime for people, rooms, and resources.
It is therefore critical for this task to run on all Domino servers that host calendar usersxxx8217; mail files.
The Schedule Manager maintains a busytime database (busytime.nsf on non-clustered servers, clubusy.nsf on clustered servers) where the schedule information is maintained for all users, rooms, and resources. The busytime database does not require any manual maintenance. By default, only the server has access to the busytime database because data contained in it is not stored in "human readable" format and is accessible only using the published APIs.
I'd say, nope, don't need it there...
And just in case...
From
here:
Just a heads up for those of you recently or about to upgrade to Domino 7. With the introduction of the new RnRMgr task to help manage Rooms and Resources, I've discovered an interesting dilemma that can occur.
The RnRMgr task requires that the busytime.nsf exist. If you have a habit during maintenance of deleting busytime.nsf and letting it rebuild, you will probably notice sometimes the RnRMgr tasks errors our and fails to load. The reason is because when the busytime.nsf does not exist, the Sched task must first create the busytime.nsf. If the RnRMgr loads to fast or prior to the Sched task, it will fail because the busytime.nsf does not exist.
And, one last link for you...
IBM Redbooks | Domino Tuning Parameters in notes.ini