The csmig utility assigns an owner to each calendar in the calendar database and maps each calendar ID (calid) to an owner, if needed.
The csmig utility supports hosted (virtual) domains and the LDAP Calendar Lookup Database (CLD) plug-in. Calendars in the migrated database are accessible using the LDAP CLD plug-in. For information about the LDAP CLD plug-in, see Chapter 6, Configuring Calendar Database Distribution Across Multiple Machines.
This section describes the following topics:
The csmig migration utility performs the following functions:
csmig migrates both user and resource calendars in the current calendar database (*.db files) specified by the caldb.berkeleydb.homedir.path parameter. In the new destination target database, csmig updates entries required by the LDAP CLD plug-in in the calendar properties (calprops), events, todos (tasks), and group scheduling engine (GSE) database files.
csmig writes only to the destination target database; it does not update your existing calendar database.
csmig assigns an owner to each calendar in the calendar database and maps each calendar ID (calid) to an owner, if needed. All default calids are kept as is, and no changes are made. Other calendars are mapped as follows:
User calendars that don’t have valid owners will be owned by the user passed to csmig by the -c option. For example, if calendar ID jsmith doesn’t have an owner, it will be converted to orphan:jsmith, where orphan is specified as the -c option.
Resource calendars that don’t have an owner will be owned by the resource user passed to csmig by the -r option.
If a resource calendar has any colons (:) in the name, the colons are converted to underscores, so that the migrated name has only one colon.
For example, a calendar named football with owner bkamdar will be converted to bkamdar:football. A calendar named tchang:soccer with the owner bkamdar will be converted to bkamdar:tchang_soccer. A resource calendar named auditorium:room1 with an owner admin1 will be converted to admin1:auditorium_room1.
csmig updates LDAP attributes for all relevant LDAP entries, including icsSubscribed, icsCalendar, icsCalendarOwned, icsFreeBusy, icsSet, and for resource calendars, uid. csmig creates the icsDWPHost attribute for each calendar in the LDAP directory server database. icsDWPHost specifies the host name of the back-end server where a calendar resides.
The requirements for using csmig are:
The calendar database must not be corrupted. Use the csdb check command to check your calendar database, and if necessary, run the csdb rebuild command to rebuild the database. For information about these commands, Appendix D, Calendar Server Command-Line Utilities Reference.
You must have sufficient disk space for the new destination target database and if applicable, your backup database.
To run csmig, 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.
You must also have privileges to manage the attributes of calendar users in the LDAP directory server that stores user preferences.
Calendar Server must be stopped.
The csmig utility has the following syntax:
csmig [-t DestinationDB] [-b Backend-DWPHost] [-o OutputFile] [-e ErrorFile] [-m MappingFile] [-c calendarOwner] [-r resourceOwner] { migrate|dryrun } |
The following table lists the utility options, gives a description of each, and gives the default value.
csmig Options |
Description and Default Value |
---|---|
-t DestinationDB |
Specifies the destination target database that csmig generates. The default is MigratedDB. |
-b Backend-DWPHost |
Specifies the name of the DWP back-end host server. This name must match the DWP back-end host server name specified in the ics.conf file. |
-o OutputFile |
Specifies an output file that captures the csmig output to the screen as well as any errors that occur. The default is MigrateOut. |
-e ErrorFile |
The file where csmig writes any errors or database entries that cannot be resolved. If database entries cannot be resolved, they are not written to the destination database. The default is MigrateError. |
-m MappingFile |
Specifies an output mapping file generated in dryrun mode that lists entries in the LDAP schema that need to be changed. For example: Old: calid=jsmith New: calid=jsmith:basketball The mapping file provides only a list of changes to make to the LDAP schema. csmig does not actually make the changes to the schema The mapping file is not used in migrate mode. |
-c calendarOwner |
Specifies the owner for user calendars that don’t have owners. |
-r resourceOwner |
Specifies the owner for resource calendars that don’t have owners. |
migrate|dryrun |
Specifies which mode the utility is running in. Use migrate mode to perform the migration. Use dryrun mode to generate the output mapping file before you actually migrate. |
After you have installed and configured Calendar Server 6, you must run csmig to migrate your existing Calendar Server and LDAP data. 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 csmig 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 csmig Migration Steps.
Install Calendar Server 6 (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).
cal_svr_base/SUNWics5/cal/sbin/stop-cal
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 (if necessary).
cal_svr_base/SUNWics5/cal/sbin/stop-cal
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
Check for any unresolved calendars in the error file (csmig.errors) and resolve them according to your plan from csmig Migration Steps under csmig Migration Steps.
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:
caldb.dwp.server.server-hostname.ip = "server-hostname" (for each back-end server including the local server)
caldb.cld.cache.enable = "yes" (if you want to use the CLD cache option)
caldb.cld.cache.homedir.path specifies the location of the CLD cache directory. The default is /var/opt/SUNWics5/csdb/cld_cache.
For information about setting configuration parameters for the LDAP CLD plug-in, see Chapter 6, Configuring Calendar Database Distribution Across Multiple Machines.
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”:
The section describes the following tips and trouble shooting examples:
A calendar named tchang:myCalendar has the owner jsmith in the calendar database, and the csmig dry run shows the mapping as jsmith:tchang_myCalendar. However, you would like to name this calendar tchang:myCalendar and assign the owner as tchang.
Before the migration, use the cscal utility to change the owner of the calendar tchang:myCalendar to tchang. Once this is done, the migration will map this calendar to tchang:myCalendar and add icsCalendarowned to the LDAP entry for user ID tchang.
After migration, the LDAP calendar search is enabled, but the calendar search dialog does not return any results or returns only partial results.
Enabling the LDAP calendar search allows Calendar Server to search (&(objectclass=icscalendaruser)(icscalendarowned=*substr*)).
Manually run two different searches on the LDAP data with the following filters and compare the output:
LDAP search with filter (&(objectclass=icscalendaruser)(icscalendarowned=*substr*))
LDAP search with filter (icscalendarowned=*substr*)
Since the server uses the filter that includes icsCalendarUser object class, the LDAP server might have been deployed with the schema check disabled, and some calendar entries may have been provisioned without the icsCalendarUser object class.
The csmig dry run mapping file and output file indicate that there is a duplicate calendar name. For example, in the original database, jsmith owns the following calendars:
basketball with 5 events
jsmith:basketball with 10 events
The dry run indicates that during a migration, the two calendars will be merged, and the resulting calendar will be jsmith:basketball with owner jsmith and 15 total events
The output file will include the following warning message:
Error modifying calendar properties, error=2
If you don’t want the two calendars to be merged, change the owner of basketball to a user other than jsmith before the migration. This will preserve the data integrity of the two separate calendars.
By default csmig assigns all orphan calendars to a single owner, but I would like to assign different owners for some orphan calendars.
csmig doesn’t accept the mapping file in the command line. However, you can assign owners to the orphan calendars in the original database before the migration. Check the dry run mapping file for all orphan calendars. Then use the cscal utility to assign owners to the orphan calendars before the migration. Run csmig in dryrun mode again to verify the new owners.
How do I move users from one back-end server to another?
To move a calendar user, you export each of the user’s calendars on the original server and then import the calendars on the second server. After the calendars are moved, you can delete the calendars on the original server. For instructions on how to move calendars, see Managing User Calendars.