This section provides information on how to migrate iFolder running on OES 2 SP3 (32-bit) to OES 11 SP3. The OES2 SP3 or OES 11 server is referred to as the source server and the OES 11 SP3 server as the target server.
iFolder is installed and configured on an OES 2 SP3 32-bit machine.
iFolder is installed and configured on the target machine.
Perform the File System Migration for the source simias data path.
For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
In this scenario, the target server is installed in the same tree as the source server. After successful completion of Transfer ID, the target server functions with the same credentials (such as IP address and hostname) as the source server and source server node is no longer available in the network.
The following data is migrated from the source server to the target server:
The simias data store path
The configuration files
Proxy user (migrates along with simias and configuration files)
Install OES 11 by using YaST on the target server. For more information, see Installing iFolder on an Existing OES 11 Server in the Novell iFolder 3.9 Administration Guide.
Stop apache from source server using the following command: rcapache2 stop.
Configure iFolder on the target server with the same values as the source server.
For more information, see Novell iFolder 3.9 Administration Guide.
Stop Apache on the target server using the following command: rcapache2 stop.
Migrate the simias data store path from the source server to the target server in the same volume and directory structure. For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
Start Apache on the target server using the following command: rcapache2 restart.
After migrating iFolder,
Verify that admin and web access pages are accessible with the same details.
Ensure that all clients are able to connect to the server without issues.
Verify that the ownership of the ifolder data source is wwwrun:www