IMPORTANT:The term data migration
as used in this section, is essentially about creating a clone of an existing Vibe system.
Data migration between servers running different versions of Vibe is not supported. However, you can use data migration in conjunction with an upgrade (see Section 21.1, Using Data Migration in Conjunction with an Upgrade to Vibe 4).
This section describes how to migrate data from an existing Vibe 4 server to a new Vibe 4 server. You might want to do this for any of the following reasons:
Your existingKablink Vibe system has outgrown the server where you originally set it up.
You want to move your existing Vibe system to a different operating system.
In this case, you can install Vibe 4 on a new server, then migrate your existing Vibe 4 data to your new Vibe 4 system.
You want to preserve your old system in its current state.
You created your Vibe system by using the Virtual Eval version of the Novell Vibe Starter Pack.
You are upgrading from Kablink Vibe to Novell Vibe.
NOTE:In the instructions that follow, “target server” refers to the server where you install the Vibe 4 software, and “source server” refers to the existing server from which you are migrating Vibe data.
The instructions in this section are based on a single-server Vibe configuration. If you have a multi-server Vibe configuration, the single-server instructions can serve as a foundation to get you started with your more complex migration process.
This section does not include instructions for migrating an Oracle database. Use the instructions for your Vibe platform as a guideline for the tasks that are involved in migrating Vibe data, then apply these guidelines to your Oracle database migration.