Calendar Server 6.3: csstored Now a Required Process
A heads-up to those of you who will be running Sun Java System Calendar Server 6.3: the csstored process has changed in the new 6.3 release. Whereas it used to be a PERL script that could be enabled and disabled at will to implement automatic backups, and could be stopped and started at will, now in version 6.3, csstored is a required daemon that is started and stopped automatically by the start-cal and stop-cal scripts, along with other required daemons.
The csstored daemon manages the various Calendar Server databases. Because each service that accesses the store depends on the successful start of this store service, it should remain running on all servers, both front-end and back-end, whenever the Calendar Server system is running.
It is no longer optional to run this daemon, whether you decide to configure automatic backups or not. Previously, you could disable the script from running by setting the ics.conf parameter local.store.enable to "no", but now the local.store.enable parameter must be set to "yes", which is the default.
The Calendar Server 6.3 Administration Guide will be re-released shortly with this updated information (Chapter 9).