To move a user or resource calendar from one back-end server to another back-end server, follow these steps:
On the original server, disable the calendar resource using the D.15 csresource utility. For example to disable the resource with the common name Auditorium:
csresource disable Auditorium
On the original server, export each of the resources calendars from the calendar database to a file using the D.10 csexport utility. For example:
csexport -c aud100 calendar aud100.ics
Copy the exported calendar (*.ics) files from the original server to the new server.
On the new server, for each calendar exported, import the calendar from the file to the calendar database using the D.11 csimport utility. For example:
csimport -c bkamdar calendar bkamdar.ics
On the LDAP directory server, update the calendar owner’s icsDWPHost LDAP attribute to point to the new back-end server using the D.3 csattribute utility. To update an attribute, you must first delete the attribute and then add it with the new value. For example, to set the new server name to sesta.com:
csattribute -a icsDWPHost delete bkamdar csattribute -a icsDWPHost=sesta.com add bkamdar
On the new server, enable the calendar resource using the D.15 csresource utility. For example:
csresource enable bkamdar
On the new server, use the following commands to verify that the attributes are correct and that each calendar has been moved correctly. For example:
cscal -v -o bkamdar list bkamdar csattribute -v list bkamdar
On the original server, delete each calendar you just moved. For example:
cscal -o bkamdar delete bkamdar
The -o option deletes all calendars whose primary owner is bkamdar.
If you are using the CLD cache option and you have moved a calendar to a different back-end server, you should clear the CLD cache to remove the server names. An out-of-date entry in the CLD cache can prevent a front-end server from finding a calendar after it has been moved. To clear the CLD cache, follow these steps:
Stop Calendar Server.
Remove all files in the /var/opt/SUNWics5/csdb/cld_cache directory, but do not remove the cld_cache directory itself.
Restart Calendar Server.