Previous Contents Index Next |
iPlanet Calendar Server Installation Guide |
Chapter 4 Migrating iPlanet Calendar Server Data
This chapter describes the how to migrate calendar data from an existing iPlanet Calendar Server version 2.x installation to version 5.0 using the tool ics2migrate.exe. The ics2migrate tool is located in the server-root\cal\bin directory.
To migrate calendar data from iPlanet Calendar Server version 2.x to version 5.0, use the following steps:
Install iPlanet Calendar Server 5.0.
To ensure data integrity, it is highly recommended that you stop all iPlanet Calendar Server services. For more information, see "Starting and Stopping the Server" in the iPlanet Calendar Server Administration Guide.
Locate the file iPlanet Calendar Server 2.x version of the caldb.conf. The default location of this file depends on the platform you are using:
On Solaris, it is located in the /var/opt/SUNWicsrv/csdb directory.
Change the first line in the caldb.conf file as follows:On Unix systems other than Solaris, it is located in the opt/iplanet/var/SUNWicsrv/csdb directory.
On Windows NT, it is located in the server-root\var\csdb directory (for example, c:\Program Files\iPlanet\CalendarServer\var\csdb).
On the machine where you installed iPlanet Calendar Server 5.0, on the command line, change to the server-root\cal\bin directory and enter:
- ics2migrate
Running ics2migrate
The data migration tool provides two processes:
Syntax:
ics2migrate [-q] [-s def|none] [-f def|none] [-l min|max] source targetics2migrate [-q] [-m db] [-s def|none] [-f def|none] [-l min|max] source target
Table 4-1 describes the ics2migrate tool options.
Examples:
The following example migrates both the LDAP user information and the calendar database migrating the iPlanet Calendar Server version 2.x database stored in the directory /var/opt/SUNWicsrv/2x_db and creating a 5.0 database in the directory /var/opt/SUNWics5/50_db, plus it grants scheduling and free/busy access to all calendars and outputs minimal migration statistics in a log file called ics2migrate.log located in the server-root\cal\bin directory:ics2migrate /var/opt/SUNWicsrv/2x_db /var/opt/SUNWics5/50_db -l min
The following example performs the same operation as the previous example, except that it operates in quiet mode (migration statistics are not displayed in the console) and no log file is generated:
ics2migrate -q /var/opt/SUNWicsrv/2x_db /var/opt/SUNWics5/50_db
The following example migrates only the 2.x calendar database stored in the directory 2x_db (relative to the current directory) and creates a 5.0 database in the directory /var/opt/SUNWics5/50_db:
ics2migrate -m db 2x_db /var/opt/SUNWics5/50_db
The following example migrates only the 2.x LDAP user information to version 5.0 format:
The following example migrates both the LDAP user information and the calendar database migrating the iPlanet Calendar Server version 2.x database stored in the directory 2x_db (relative to the current directory) and creating a 5.0 database in the directory /var/opt/SUNWics5/50_db, plus it outputs maximum migration statistics in a log file called ics2migrate.log located in the server-root\cal\bin directory:
ics2migrate -l max 2x_db /var/opt/SUNWics5/50_db
The following example migrates both LDAP and calendar database information in the specified directories, plus it grants scheduling access only to each user's default calendar and denies free/busy access to all calendars on the server, and it does not output statistical information to a log file:
ics2migrate -s def -f none 2x_db 50_db
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated November 02, 2000