How to move a Domino Resource Reservations database
To successfully move a Resource Reservations database to a new Domino server, here are the steps you must follow:
Tell Shedule Manager and Calendar Connector (Sched and CalConn) to quit on both servers.
Make a new copy of Resource.nsf on the new server.
At the operating system level, move or rename the original Resource.nsf file.
NOTE: Rather than move or rename, I decided to put a doclink to the new database on the “About” document and change the launch options to “Launch first doclink in About database.” This redirects users who already had the database bookmarked or on their workspace. It adds the new icon as well and makes the move relatively seamless.
Open the ACL (File -> Database -> Access Control) of the new Resource.nsf, select the Advanced icon, and set the Administration server to the new server name.
Check scheduled agents (which should just be the Purge Documents Agent) and change the schedule to run on the new server.
Sign the new database with your administrator/template ID file.
Open the Domino Directory.
Change to the Server -> Mail-in Databases view.
Create a Formula agent to change the Room and Resource documents to the new server:
FIELD MailServer:= “CN=newserver/OU=orgunit/O=org”
Select all the room and resource documents that need to be changed and run the agent.
Replicate the Domino Directory throughout the domain.
Delete busytime.nsf on both servers. This may not be necessary, but I have had issues with corruptions and double-bookings, so when I have a chance to rebuild, I take it.
Start Sched and CalConn tasks on both servers. Busytime.nsf will be rebuilt at this time.
Through the server console, enter tell router update config on both servers to allow the change in the Rooms and Resources mail server locations to be picked up in the routing table.
Open the new Resource Reservation database and run Actions -> Upgrade (same agent run after an upgrade). This prepares the database to receive and autoprocess requests on the new server.
NOTE: If this step is missed, the Domino database will receive reservations, but they will arrive as a “Notice” form and will not fall into the schedule/calendar or send out responses.
Test what you’ve done by creating a meeting and reserving a room. Autoprocessing should occur without a problem.