If you had a version of Calendar Server predating version 5.1.1, after you install and configure Calendar Server 6.3, run csmig to migrate your existing Calendar Server and LDAP databases. Migration of the LDAP data is required for the LDAP CLD plug-in to work properly. Use these steps to migrate calendar data using csmig:
Configure your Directory Server using comm_dssetup.pl.
If you have not already indexed LDAP attributes using comm_dssetup.pl, do so at this time. This will greatly help performance of the LDAP data migration.
Using a staging server (not your production server), perform a test dry run.
A dry run reports what csmig would do during an actual migration but does not migrate any data. After the dry run, and before you actually migrate, correct any errors and determine a plan to handle any unresolved calendars.
For instructions on how to perform a test dry run, see 3.5.4 csmig Utility Migration Steps.
Migrate Your Production Data
During a production run, csmig migrates the calendar database (.db files) and LDAP data (user and group preferences data), icsSubscribed, icsCalendar, icsCalendarOwned, icsFreeBusy, icsSet, and uid (for resource calendars). After the migration, all calendar resources will have an LDAP entry created.
For instructions on how to migrate your production data, see 3.5.4 csmig Utility Migration Steps.
Install Calendar Server 6.3 (if necessary) on the staging server.
Copy a snapshot of your calendar database to the staging server.
Mimic your production LDAP environment on the staging server by performing the following tasks:
Install Directory Server.
Install a snapshot of the LDAP database on this server.
Run comm_dssetup.pl to configure the staging Directory Server.
Run csconfigurator.sh to configure the staging Calendar Server.
Log in as icsuser (or, if its different, log in as the Calendar Server runtime user ID specified during configuration). If you run csmig as superuser (root), you might need to reset the permissions for the migrated files.
Change to the cal-svr-base/SUNWics5/cal/sbin directory.
Run the csdb check command to check your database for corruption. If corruption is indicated, run csdb rebuild to rebuild the database.
Consider creating a catchall calid for user calendars that don’t have an owner. For example, the following command creates a user with the calid of orphan:
./csuser -g orphan -s adminuser -y password -l en -c orphan create orphan
Stop the Calendar Server using the stop-cal command (if necessary).
Run csmig with the -dryrun option. For example, you might enter:
./csmig -b sesta.com -o csmig.out -e csmig.errors -m csmig.map -c orphan -r calmaster dryrun
This command assigns user calendars without an owner (orphan calendars) to the owner orphan and resource calendars without an owner to the owner calmaster.
Check the output mapping file (csmig.map). The mapping file lists entries that need to be updated in the LDAP schema.
Check the output, mapping, and error files. Resolve any LDAP issues or errors that you find. Determine how you will handle any unresolved calendars before the actual migration.
Several options are:
Delete any unneeded calendars before you migrate.
Assign owners to any unresolved calendars.
Allow csmig to assign owners to the calendars during migration using the -c and -r options.
Run csmig to migrate your staging calendar database.
For example, the following command migrates the calendar database to the /var/opt/SUNWics5/testcsdb/ directory:
./csmig -t /var/opt/SUNWics5/testcsdb/ -b sesta.com -o csmig.out -e csmig.errors -m csmig.map -c orphan -r calmaster migrate
After the test migration is finished, perform these steps to check out the newly migrated calendar database.
Copy the migrated database to the /csdb directory specified by the caldb.berkeleydb.homedir.path parameter. Or, edit this parameter to point to the new location of the migrated database.
Run csdb check on the new calendar database. The number of events and todos in the migrated database should match the pre-migration totals.
Search for icsCalendarOwned entries and make sure that the entries match the pre-migration number of calendars.
Log in to Communications Express and verify some of the calendars in the migrated database.
If the test migration is successful, you are ready to migrate your production database.
Log in as icsuser (or as the Calendar Server runtime user ID specified during configuration). If you run csmig as superuser (root), you might need to reset the permissions for the migrated files.
Change to the cal-svr-base/SUNWics5/cal/sbin directory.
Stop the Calendar Server using the stop-cal command.
Backup the following data:
Calendar database (.db files).
LDAP data: slapd database directory and LDAP database.
ics.conf file. This step is not actually required, but it can be useful if you need to revert to your original configuration.
Run csmig with the -migrate option.
For example, the following command migrates the calendar database to the /var/opt/SUNWics5/newcsdb/ directory:
./csmig -t /var/opt/SUNWics5/newcsdb/ -b sesta.com -o csmig.out -e csmig.errors -m csmig.log -c orphan -r calmaster migrate
Run the csdb check command to check your migrated database. If any corruption is indicated, run csdb rebuild to rebuild the database.
Copy the new migrated database to the /csdb directory specified by the caldb.berkeleydb.homedir.path parameter. Or, edit this parameter to point to the new location of the migrated database.
Enable the LDAP CLD plug-in by making any necessary changes to the following configuration parameters in the ics.conf file:
For information about setting configuration parameters for the LDAP CLD plug-in, see Chapter 5, Configuring Calendar Database Distribution Across Multiple Machines in Calendar Server Version 6.3.
Restart Calendar Server using the start-cal command.
Log in to Communications Express and verify that your configuration is working by checking several of the migrated calendars.
To disable alarms while you are making your checks, set each of the following parameters in the ics.conf file to "no":