The csvdmig utility modifies the Calendar Server database and LDAP directory server database for sites that want to use hosted (virtual) domains.
Be sure to run csmig before using this utility if you are moving from a non-hosted environment.
This sections contains the following topics:
The csvdmig utility adds the domain name to the user ID as follows:
The format of calendar ID's (calids) is changed:
From: userid[:calendar-name]
To: userid@domain[:calendar-name]
Access Control List (ACL) access rules are changed:
From: userid
To: userid@domain
The LDAP directory server user entries for the Calendar Server attributes are modified as:
userid[:calendar-name] to userid@domain[:calendar-name].
Updates the owner and attendee fields in events and tasks in the calendar database.
For example: if jsmith in the domain sesta.com is the owner of an event, the new owner field would contain jsmith@sesta.com.
The csvdmig utility updates the databases and LDAP directory in place. That is, it does not create a separate migrated database, but alters the database you are converting. Therefore, to be safe, run csvdmig against snapshots of your databases and LDAP directory.
The csvdmig utility has the following syntax:
csvdmig [-t DestinationDB] [-c ConfigFile] [-e ErrorFile] [-m MappingFile] migrate [DB|LDAP] |
The following table lists the options used by csvdmig, and gives a description of each.
Option |
Description and Default Value |
---|---|
-m MappingFile |
Input parameter specifying a mapping file. For more information on the mapping file, see Mapping File. The default is MigrateMapping. |
-c ConfigFile |
Input parameter that specifies a Calendar Server configuration file. The default is the ics.conf file. |
-t DestinationDB |
Output parameter that specifies the location of the database. The default is MigratedDB. Tip – Always use the -t option. Attempting to migrate the databases in the working directory produces unpredictable results. See Destination DB. |
-e ErrorFile |
output parameter that specifies the name of the error file for errors that cannot be resolved. The default is MigrateError. |
DB | LDAP |
Specifies which database to modify: DB – the calendar database LDAP – the LDAP directory The default is the calendar database (DB). |
Table 4–1 Options for csvdmig
Option |
Description and Default Value |
---|---|
-m MappingFile |
Input parameter specifying a mapping file. For more information on the mapping file, see Mapping File. The default is MigrateMapping. |
-c ConfigFile |
Input parameter that specifies a Calendar Server configuration file. The default is the ics.conf file. |
-t DestinationDB |
Output parameter that specifies the location of the database. The default is MigratedDB. See Destination DB. |
-e ErrorFile |
output parameter that specifies the name of the error file for errors that cannot be resolved. The default is MigrateError. |
DB | LDAP |
Specifies which database to modify: DB – the Calendar Server databaseLDAP – the LDAP directory The default is the calendar database (DB). |
The mapping file is an input text file that maps existing users to their respective domains. You must create the mapping file before you run csvdmig. Specify one entry per line with a space between the old and new values. For example:
user1 user1@sesta.com user2 user2@siroe.com user3 user3@sesta.com ... usern usern@siroe.com
This utility does not move the migrated files into a new DestinationDB. If you specify the -t option, you must copy the database files to be migrated into that directory before running csvdmig.
If you do not use the -t option, the utility will migrate the files in the working directory, with unpredictable results.