I’m looking for detailed information on how the validatation process works with RNRMGR and Sched in version 7. We’ve had several problems with rooms showing up in the freetime schedule as available when they should not be. We have one dedicated resource server that is clustered.
I’ve noticed that Sched will recreate the clubusy database and go through a validation process for each room and resource. However, clubusy.nsf is not populated with room and resource entries until RNRMGR begins validating.
I’m looking for details about what exactly each of these tasks is doing during validation. I can’t find any technical info printed about this.
Thanks,
Kristin
Subject: Looking for Details on RNRMGR/Sched
from http://www.alanlepofsky.net/alepofsky/alanblog.nsf/dx/notesdomino7
- How the new Rooms and Resources Manager works in Domino 7
- Functional changes in Domino 7 for reservations directly booked in the Resource database
- What is the purpose of the RnRMgr task in ND7?
- Clustering the Domino 7 Resource Reservations database
- How do Advance limits on reserving a room or resource work in Domino 7?
Subject: Looking for Details on RNRMGR/Sched
Some technical info was published in 2 DeveloperWorks articles I wrote when RnRMgr was first introduced in R7.0.
To save you some time though, as of 7.0 Schedule Manager (Sched) is NO LONGER involved in busytime where R&R is concerned. The Room & Resource Manager (RnRMgr) is now solely responsible for finding requests, processing them and keeping busytime updated.
I put RnRMgr thru thousands of stress tests and constant in-house use since it was built. The only time we saw a problem was when someone was using a 7.0 - 7.02 (?) template and modifying pre-R7 repeating entries. The template did not correctly prohibit this behavior and it caused some odd results including funky busytime data…
So you should check what version you are using and if any of the problems you are seeing involved instances of pre-R7 repeating meetings. You can tell the pre-R7 from the R7 ones by the lack of an RQStatus item or the fact that the StartDateTime (and EndDateTime) items are time ranges and note just TIMEDATEs.
I do not recall exactly which release has the fix so check the release notes. If you are using 7.03 (pretty sure its fixed there), open up a support ticket so we can get you some help in resolving your problem.
Bruce
IBM
Subject: RE: Looking for Details on RNRMGR/Sched
Bruce,
Thank you for replying. This is helpful. I did read all of the articles posted in the first link before upgrading the resource servers; but were still a little unsure if Sched handled any part of the busytime process for rooms and resources since we see it validating rooms on the console. Its good to have a confirmation of this.
Our resource reservations consist mostly of repeat meetings booked via work flow in R6. We’ve never allowed repeating meetings to be created on the resource database directly. Does what you are describing affect workflow or directly booked reservations?
We did have quite a bit of trouble with directly booked single-instance reservations created in R6. We corrected the problem by populating the documents with the 4 new fields and then resetting the RQStatus.
What we are seeing since January are rooms that are heavily booked, suddenly appearing in freetime as nearly 100% available. I’ve opened 3 PMR’s for this and we are still investigating.
Subject: RE: Looking for Details on RNRMGR/Sched
Hi KristinWe are seeing similar behavior as mentioned by you in our environment [Notes 7.0.2 FP2].
Bruce - Always enjoy reading your articles
Thanks.
Robert Mendonca