This section provides information about the migration and upgrade capabilities of iFolder 3.9. It also discusses how to use the Novell Migration Tool to introduce the iFolder 3.9 services into an existing network environment without disrupting existing Novell iFolder 2.x and iFolder 3.x services.
One of the top priorities in designing Novell iFolder 3.7 and later was to ensure that new iFolder services running on Novell Open Enterprise Server (OES) 2 or later can bridge the gap between the Novell iFolder 2.x services and the iFolder 3.2 services that are currently running on OES 1.
Migration: Migration is the process of moving from,
iFolder 3.2 on OES 1 Linux
iFolder 2.x on OES 1 Linux
iFolder 2.x on NetWare
to iFolder 3.9.1 on OES 11 SP3.
Upgrade: Upgrade is the process of changing to a new version of iFolder on the same platform, such as from,
iFolder 3.2 on OES 1 Linux
iFolder 3.4 on OES 1 Linux
iFolder 3.6 on OES 2
to iFolder 3.9.1 on OES 11 SP3.
You can move iFolders and user data from an iFolder 2.x domain to iFolder 3.9. In the following sections, the iFolder 2.x server is referred to as the source server and the iFolder 3.9 server as the target server.
IMPORTANT:You cannot migrate encrypted iFolders. Use the client-side migration wizard to migrate the encrypted iFolders. For more information about the client-side migration, see Novell iFolder Migration and Upgrade in the Novell iFolder 3.9 Cross-Platform User Guide.
Table 26-1 Supported Platforms
|
Source Platform |
Destination Platform |
|---|---|
|
NetWare 6.5 SP8 |
OES 11 SP3 |
|
OES 2 SP3 or OES 11 |
OES 11 SP3 |
You must perform the File System Migration for the source data path.
For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
Ensure that the iFolder 3.9 servers, the iFolder 3.9 Web Access server, and the eDirectory services are up and running.
The iFolder 3.9 Web Access server and the Web Admin server should be running on the target server.
Ensure that the user objects are available in eDirectory and are accessible from the target server.
Novell iFolder Server: Novell iFolder 3.9 has the capacity to manage 1000 connected users simultaneously on a single server. This can vary based on the server hardware and network capabilities. If there are more than 1000 users, you can use a multi-server setup. For more information, see Deploying iFolder Server in the Novell iFolder 3.9 Administration Guide.
Web Access Server: The Novell iFolder 3.9 Web Access console for end users must run on the target server.
Web Admin Server: The Novell iFolder 3.9 Web Admin console for end users must run on the target server. Ensure that the policies for disk quota, iFolder limit, and file filter are set at the system level, because these policies affect the storage availability on the server. For more information about policies, see Configuring System Policies in the Novell iFolder 3.9 Administration Guide.
Multi-Server Setup: If you have a predefined choice of servers for a set of users or LDAP Groups, you must provision them and set the policies by using the iFolder 3.9 Web Admin console. If the users are not provisioned and no policies are set, the iFolder 3.9 server uses the round-robin provisioning method to provision the users. Novell iFolder 3.9 has its own LDAP attribute for provisioning users; it does not use the iFolder 2.x LDAP attribute for provisioning. You can use the iFolder 3.9 LDAP attribute for selective provisioning and use the Web Admin console for manual provisioning of users and groups.
The following scenarios are supported for migrating Novell iFolder Services. (For general explanation of the scenarios supported in OES 11, see Section 1.3, Migration Scenarios.)
Transfer ID: In this scenario, the target server is installed into the same eDirectory tree as the source server, with a temporary hostname and IP address. The iFolder 2.x data is copied to the target machine to perform the basic operations, while the original copy is operational in the source machine until the move completes. When the move completes, the source and target servers swap and all the iFolder 2.x data on the source server is available on the target server. The target server functions with the same credentials (such as IP address and hostname) as the source server and the source server node is no longer available in the eDirectory tree.
IMPORTANT:In a NetWare to OES 11 Transfer ID scenario, ensure that the target server is installed in the same context as the source server.
Migrate: In this scenario, you can copy the iFolder data from any number of existing source servers to a target server. The source server must be running NetWare 6.5 SP8, OES 2 SP1, OES 2 SP2, or OES 11. The target server must be running on OES 11 SP3 on 64-bit hardware.
In the Transfer ID scenario, only the Same Tree migration is applicable. In the Migrate scenario, both the Same Tree and Different Tree migration are possible.
Same Tree: In the Same Tree migration, the source and target server are on the same eDirectory tree. The source server must be running NetWare 6.5 SP8, OES 2 SP3, or OES 11. The target server must be running on OES 11 SP3 on 64-bit hardware.
Different Tree: In the Different Tree migration, the source server and the target server are on different eDirectory trees. The source server must be running NetWare 6.5 SP8, OES 2 SP3, or OES 11. The target server must be running SUSE Linux Enterprise Server 11 SP4 with OES 11 SP3 on 64-bit hardware.
Install, configure, and run iFolder 3.9 on the target server.
Open the Migration Tool GUI.
Desktop: Select Computer > More Applications > System > Novell Migration Tools.
Terminal: Log in as the root user and at a terminal prompt, enter miggui.
Authenticate to the source and target servers. All the associated services are listed in the Services panel.
Select Novell iFolder, then click Configure. The iFolder configuration window displays.
IMPORTANT:Ensure that you migrate the iFolder 2.x file system data by using the file system migration tools. For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
The default data path for iFolder 2.x is /var/opt/novell/<ifolderdata> for OES 1 Linux. For NetWare, the data path is configurable.
Fill in the following fields:
|
Parameter |
Description |
|---|---|
|
2.x Migration |
Select this option if you want to migrate the iFolder 2.x application to iFolder 3.9 on OES 11 SP3. iFolder Data Path: Specify the path where the iFolder 2.x system data is migrated to on the target server. This is the location on the iFolder target server where iFolder application files and the users' iFolders and files are migrated to. The path is case-sensitive. |
|
iFolder 3.9 Admin Name |
Specify the user name of the iFolder 3.9 administrator. |
|
iFolder 3.9 Admin Password |
Specify the iFolder 3.9 admin password. |
|
Partial Migration |
Select this option if you want to perform a partial migration that allows you to migrate a selected set of users to an iFolder 3.9 domain. You can perform partial migration either by using a user list file or by browsing and selecting users from an eDirectory tree. User List File: Specify the location of the user list file. This file is a text file that contains the list of user DNs for all the users selected for migration. Ensure that each user DN starts in a new line. Select LDAP Users: Browse the eDirectory tree and select the users for migration. |
Click OK to configure iFolder for migration.
In the main window, you can either configure other services or click Migrate to start the migration process.
The Migration Tool takes care of the order in which each service migrates. Therefore, iFolder migration initiates only after file system migration completes.
To run the Novell iFolder migration utility through the command line, run /opt/novell/migration/sbin/migif2 --option value with the following details:
Table 26-2 Command Line Options
|
Option |
Description |
|---|---|
|
--precheck |
(Optional) Checks whether migration is possible with the given parameters. |
|
--2xdatapath |
Specifies the path where the iFolder system data is stored. This is the location where the iFolder source server stores iFolder application files and the users' iFolders and files. The path is case sensitive. |
|
--serveripaddress |
Specifies the IP address of the iFolder 3.9 server. |
|
--adminname |
Specifies the user name of the iFolder 3.9 administrator. |
|
--password |
Specifies the password for the iFolder 3.9 administrator. |
|
--workarea |
(Optional) Specifies the location for the temporary migration files. |
|
--userlist |
(Optional) Specifies a text file that contains the list of users for migration. If you don’t specify this, a complete migration is performed. |
|
--sync |
(Optional) Performs the sync operation during migration for any changes made on the source server. |
To migrate user data to the master server, all the iFolder 3.9 servers must be up and running. The master server automatically provisions the home servers for each migrated user. Depending on the user provisioning priority you have set, each user is provisioned in the appropriate iFolder 3.9 server. If you want to move each user from a single iFolder 2.x server to different iFolder 3.9 servers or from many iFolder 2.x servers to a single iFolder 3.9 server, you must set the provisioning with the iFolder 3.9 Web Admin console. By default, the round-robin provisioning method is used. For more information about using the Web Admin console, see the following sections in the Novell iFolder 3.9 Administration GuideNovell iFolder 3.9.2 Administration Guide.
Managing iFolder Services via Web Admin
Managing iFolders
Managing iFolder Users
The iFolder 2.x user data format is converted to that of iFolder 3.9. The flat directory structure of the iFolder 2.x data is changed to the hierarchical structure of the iFolder 3.9 client.
NOTE:The 2.x configuration is not migrated.
The 2.x encrypted iFolders are not migrated. This is because the passphrase for each user is not known to the administrator. Each user is expected to do a client-side migration.
If the user list is provided, only those users specified in the user list are migrated.
In the Transfer ID scenario, iFolder 3.9 updates the configuration files with the new server IP address after the migration is completed.
You can find the migration logs at /var/opt/novell/log/ifolder/checkpoint.log. The checkpoint.log contains the status of the iFolder 2.x migration.
Post-migration configuration: No additional configuration is required because only data is migrated and no policies are migrated from iFolder 2.x to iFolder 3.9. You must set the policies again for each user by using the Web Admin console; this is because the iFolder 2.x policies are not compatible with iFolder 3.9.
For more information about using the Web Admin console, see the following chapters in the Novell iFolder 3.9 Administration Guide.
Managing iFolder Services via Web Admin
Managing iFolders
Managing iFolder Users
Merge: Users can have a local copy of the 2.x iFolders that are already migrated to the server. When they connect the iFolder 3.9 client to the iFolder 3.9 server, the migrated iFolders are also available for download. Instead of downloading them and having a different copy on the same machine, they can simply merge the iFolders on the local machine to the migrated iFolders on the server. This also reduces the data transfer traffic and effort. For more information about the merge functionality provided in the client, see Merging iFolders in the Novell iFolder 3.9 Administration Guide.
There is an automatic client-side migration from Novell iFolder 2.x to iFolder 3.9. The Migration Wizard provided for the user in the iFolder 3.9 client migrates the existing 2.x iFolder data to the iFolder 3.9 domain. The Migration Wizard appears soon after the installation of the iFolder 3.9 client and displays a message about the existence of previous version data and a request for a migration. This Wizard is also available on the Preferences menu so that it can be invoked at any time after installation.
IMPORTANT:The Novell iFolder 2.x client and the iFolder 3.9 client can run independently and concurrently on the same user machine. They are separate applications and should not be installed in the same directory. However, if you migrate the 2.x data to 3.9, you must remove the 2.x client when the client-side migration is complete.
The user must have both an iFolder 2.x account and a corresponding iFolder 3.9 account.
The user must use only the Migration Wizard available in the iFolder client to migrate an existing 2.x iFolder to a 3.9 iFolder. The user should not perform an iFolder 2.x to 3.9 conversion by any other means, such as using iFolder shell integration (Windows Explorer or Nautilus) or the iFolder 3.9 client upload mechanism from the thick client.
If the user selects to make a copy of the iFolder 2.x data and move it to the iFolder 3.9 domain, ensure that you allocate sufficient space (at least 10 MB larger than the size of the iFolder 2.x data) on the hard disk (user’s Home directory for Linux and user’s Application Data directory for Windows) before performing the migration. The additional space is used to store the iFolder database.
In this case, the user must log out of the 2.x client before performing the migration to avoid synchronization issues and related possible data corruption.
If the user selects to migrate the iFolder and disconnect it from 2.x domain, the folder is not accessible through the 2.x account after the migration, because it is completely moved to the 3.9 domain and 2.x registry entries are removed in the client. It is possible that the same 2.x iFolder is available on another user desktop. If so, make sure that it is manually removed to avoid data inconsistency, because it is not under the control of iFolder 3.9 domain.
You can move iFolders and the user data from an iFolder 3.2 domain to an iFolder 3.9 domain. In the following sections, the iFolder 3.2 server is referred to as the source server and the iFolder 3.9 server as the target server.
Table 26-3 Supported Platforms
|
Source Platform |
Target Platform |
|---|---|
|
OES 2 SP1, OES 2 SP3, or OES 11 |
OES 11 SP3 |
Before proceeding with the migration, see Prerequisites.
Novell iFolder Server: Novell iFolder 3.9 has the capacity to manage 1000 connected users simultaneously in a single server. This can vary based on the server hardware and network capabilities. If there are more than 1000 users, you can use a multi-server setup. For more information, see Deploying iFolder Server in the Novell iFolder 3.9 Administration Guide.
Web Access Server: The Novell iFolder 3.9 Web Access console for end users is running on the target server.
Web Admin Server: The Novell iFolder 3.9 Web Admin console is running on the target server. Ensure that the policies for disk quota, iFolder limit, and file filter are set at the system level, because these policies affect the storage availability in the server. For more information about policies, see Configuring System Policies in the Novell iFolder 3.9 Administration Guide.
Multi-Server Setup: If you have a predefined choice of servers for a set of users or LDAP Groups, you must provision them, and set the policies by using the iFolder 3.9 Web Admin console. If the users are not provisioned and no policies are set, the iFolder 3.9 server uses the round-robin provisioning method to provision the users. Novell iFolder 3.9 has its own LDAP attribute for provisioning users; it does not use the iFolder 3.x LDAP attribute for provisioning. You can use iFolder 3.9 LDAP attribute for selective provisioning and use the Web Admin console for manual provisioning of users and groups.
The following scenarios are supported for migrating Novell iFolder Services. (For a general explanation of the scenarios supported in OES 11 SP3, see Section 1.3, Migration Scenarios).
Transfer ID: In this scenario, the target server is installed into the same eDirectory tree as the Source server, with a temporary hostname and IP address.The iFolder 3.2 data is copied to the target machine to perform the basic operations, while the original copy is operational in the source machine until the move completes and all of the iFolder 3.2 data on the source server is available on the target server. The target server functions with the same credentials (such as IP address and hostname) as the source server and the source server node is no longer available in the eDirectory tree.
Migrate: In this scenario, you can copy the iFolder data from any number of existing source servers to a target server. The source server must be running OES 2 SP3 or OES 11. The target server must be running on OES 11 SP3 on 64-bit hardware.
In the Transfer ID scenario, only the Same Tree migration is applicable. In the Migrate scenario, both the Same Tree and Different Tree migration are possible.
Same Tree: In this scenario, the source server and target server are on the same eDirectory tree. The source server must be running OES 2 SP3 or OES 11. The target server must be running on OES 11 SP3.
Different Tree: In this scenario, the source server and the target server are on different eDirectory trees. The source server must be running OES 2 SP3 or OES 11. The target server must be running on OES 11 SP3.
You can perform the migration through either the Migration Tool GUI or the command line.
Install, configure, and run iFolder 3.9 on the target server.
Copy the simias.config file from the source server to the location /var/lib/wwwrun/.local/share/simias in the target server.
Open the Migration Tool GUI.
Desktop: Select Computer > More Applications > System > Novell Migration Tools.
Terminal: Log in as the root user and at a terminal prompt, enter miggui.
Authenticate to the source and target servers. All the associated services are listed in the Services panel.
You must configure the file system before configuring the iFolder 3.2 service. To configure NSS or NCP volumes, select File System, then click Configure. For any other file system, perform the migration using Command Line Utilities. For more information about configuring the file system, see Section 16.6, Migrating the File System Using Command Line Utilities.
Select Novell iFolder, then click Configure. The iFolder configuration window displays.
IMPORTANT:Ensure that you migrate the iFolder 3.2 file system data by using the file system migration tools. For more information, see Section 16.4, Migrating the File System Using the Migration GUI.
The default data path for iFolder is /var/lib/wwwrun/simias for Linux.
Fill in the following fields:
|
Parameter |
Description |
|---|---|
|
3.2 Migration |
Select this option if you want to migrate the iFolder 3.2 application to iFolder 3.9 on OES 11 SP3. iFolder 3.2 Data Path: Specify the path where the iFolder 3.2 system data is migrated to on the target server. This is the location on the iFolder target server to which iFolder application files and the users' iFolders and files are migrated. The path is case-sensitive. |
|
iFolder 3.2 Admin Name |
Specify the user name of the iFolder 3.2 administrator. This is the fully distinguished name of the iFolder admin user. For example: cn=admin,o=acme. |
|
iFolder 3.2 Admin Password |
Specify the iFolder 3.2 admin password. |
|
iFolder 3.9 Admin Name |
Specify the user name of the iFolder 3.9 administrator. For example: admin. |
|
iFolder 3.9 Admin Password |
Specify the iFolder 3.9 admin password. |
|
Partial Migration |
Select this option if you want to perform a partial migration, which allows you to select a set of users and migrate them to an iFolder 3.9 domain. User List File: Specify the location of the user list file. This file is a text file that contains the list of user DNs for all the users selected for migration. Ensure that each user DN starts in a new line. Select LDAP Users: Browse the eDirectory tree and select the users for migration. |
Click OK to configure iFolder for migration.
In the main window, you can either configure other services or click Migrate to start the migration process.
The Migration Tool takes care of the order in which each service migrates. Therefore, the iFolder migration initiates only after file system migration is completed.
To run the Novell iFolder migration utility through the command line, run /opt/novell/migration/sbin/migif3 --option=value with the following details:
|
Option |
Description |
|---|---|
|
--precheck |
(Optional) Checks whether migration is possible with the given parameters. |
|
--oldadminname |
Specifies the user name of the iFolder 3.2 administrator. |
|
--newadminname |
Specifies the user name of the iFolder 3.9 administrator. |
|
--oldadminpassword |
Specifies the iFolder 3.2 admin password. |
|
--previousserverurl |
Specifies the IP address of the iFolder 3.2 server. |
|
--newserverurl |
Specifies the IP address of the iFolder 3.9 server. |
|
--workarea |
(Optional) Specifies the location for the temporary migration files. |
|
--userlist |
(Optional) Specifies a text file that contains the list of users for migration. If you don’t specify this, a complete migration is performed. |
|
--sync |
(Optional) Performs the sync operation during migration for any changes made on the source server. |
The user data (iFolders) is migrated.
If the user list is provided, only those users specified in the user list are migrated.
In the Transfer ID scenario, the iFolder 3.9 updates the configuration files with the new server IP address after the migration is completed.
You can upgrade iFolder 3.x on OES 2 SP3 or OES 11 to iFolder 3.9 on OES 11 SP3. This is a single-server scenario, where the source and target servers reside on the same machine.
Ensure that the server-side data is backed up before you perform the upgrade.
You must use the YaST-based Novell iFolder configuration for the in-place upgrade. A YaST upgrade of OES 2 SP3 or OES 11 to OES 11 SP3 upgrades the configuration values of the iFolder enterprise server from the 3.x iFolder server to the 3.9 iFolder server.
For details on YaST-based configuration, see Deploying iFolder Server in the Novell iFolder 3.9 Administration Guide.
Install OES 11 by using YaST. For more information, see Installing iFolder on an Existing OES 11 Server SP3 in the Novell iFolder 3.9 Administration Guide.
Select Use Following Configuration, then click Novell iFolder to change the default configuration settings for iFolder.
or
If you decide to use default settings, click Next to start Novell iFolder 3 configuration.
For security reasons, it is recommended that you always change the default iFolder configuration settings.
Follow the YaST on-screen instructions to proceed through the Novell iFolder 3.9 configuration.
The table in the Configuring the iFolder Enterprise Server in the Novell iFolder 3.9 Administration Guide summarizes the decisions you make.
NOTE:In an upgrade scenario, the following fields in the YaST UI for iFolder are disabled, so you don't need to specify them.
Path to the Server Data files
Install into Existing iFolder Domain
Private URL of Master server
Directory Server Address
iFolder Admin Password
Verify iFolder Admin password
LDAP Search Contexts
LDAP Naming Attribute
Require a secure connection between the LDAP server and the iFolder server
If you have upgraded an iFolder server to OES 11 in a cluster setup, the move to common proxy using the move_to_common_proxy.sh script fails. This is because during the upgrade, the cluster volumes are not mounted. After the upgrade successfully completes, use the following command on the node where the iFolder cluster is running:
/opt/novell/ifolder3/bin/ifolder_mono_setup
This will update the Simias.config file with the necessary configuration information required for the common proxy framework. In non-cluster setups, this runs automatically as part of the post-install script.
With the client upgrade, binaries are upgraded with the new version of binaries and the client data is auto-upgraded.
Make sure that you perform the following server-side operations so that the user is notified of the new version of the iFolder client and prompted to accept the client upgrade.
IMPORTANT:Ensure that the user backs up the Simias store before upgrading the client.
Enter http:\\ IP address of iFolder serverin the browser to go to the OES 11 SP3 home page.
Download the client RPMs or executables from the OES 11 SP3 home page.
Place the RPMs under the respective platform directories in the path ifolder_installDirectory/lib/simias/web/update/unix
The latest client RPMs are installed only if they are present in the given path. The automatic installation happens when the user attempts to connect the 3.x or 3.4.1 client to the iFolder 3.9 server. The names of the platform-specific directories are in the version.config file in the same path. A script file named install-ifolder.sh in the unix directory contains the commands for upgrading the RPMs to the latest version.
Examples for install-ifolder3.sh are as follows:
Modify version.config to include entries for the directory where in the RPMs or the executables are placed.
Connect the existing client to the server.
The client automatically prompts the user to accept the client upgrade when he or she attempts to connect an iFolder 3.x or 3.4 1 client to a 3.9 server. For more information, see Automatically Upgrading to iFolder 3.9.2 client on Linux in the Novell iFolder 3.9 Cross-Platform User Guide.
For instructions on performing a manual upgrade, see Manually Upgrading to iFolder 3.9.2 client on Linux in the Novell iFolder 3.9 Cross-Platform User Guide.
On the OES 11 client Downloads page, click the iFolder client for Linux link to download the RPMs as desired.
For more information, see Deploying iFolder Server in the Novell iFolder 3.9 Administration Guide.
Follow the on-screen prompts to download the files to a directory on your machine.
Enter cd <location where you have downloaded the files>.
Run rpm -Uvh *.rpm to upgrade to iFolder 3.9.
If you use both iFolder 2.x and Novell iFolder 3.9 services, we recommend that you install each version on its own dedicated server. OES 11do not support iFolder 2.x service.
Do not install the iFolder 3.9 client in the same application folder as a Novell iFolder 1.x or 2.x client.
The iFolder 3.9 client can coexist on the same workstation as the Novell iFolder 1.x client or 2.x client, with the following caveats:
The iFolder 3.9 client and its iFolders work only with the Novell iFolder 3.9 enterprise server.
The Novell iFolder 1.x or 2.x client and its iFolders on the workstation continue to work only with the assigned Novell iFolder server of the same release.
The single iFolder created with the iFolder 1.x or 2.x client can coexist with the multiple iFolders created with the iFolder 3.9 client. The iFolders function independently on the workstation; they do not exchange information or data. However, you can manually transfer local data between old and new iFolder folders.
You should not attempt to convert the Novell iFolder 1.x or 2.x folder to an iFolder to be managed by Novell iFolder 3.9 by any other means other than using the Migration Tool. Similarly, you should not convert parent folders of that iFolder to a next-generation iFolder.
For example, if abc is the parent directory of the xyz directory, you should not attempt to migrate abc to iFolder 3.9 while xyz still remains an iFolder of type 2.x or 1.x. In addition, you should not attempt to migrate xyz to iFolder 3.9 while abc still belongs to a 2.x or 1.x domain.
If the folder is no longer used by a prior version of the Novell iFolder client, such as after you uninstall the old client from the workstation, you can convert the folder or its parent folders to a next-generation iFolder.