This section describes how to migrate data from an existing Vibe server to a new Vibe server. You might want to do this for any of the following reasons:
Your existing 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 3.2 on a new server, then migrate your existing Vibe 3.2 data (or data from a previous version of Vibe) to your new Vibe 3.2 system
If you are migrating from a Teaming 2.1 server, follow the instructions in “Update” in the Novell Vibe OnPrem 3 Installation Guide.
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
Complete the following sections to migrate your Vibe data:
NOTE:In these instructions, “target server” refers to the server where you install the Vibe 3.2 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.