=========================================================== = ARKEIA V5.3 OR V5.5 TO V6.0 MIGRATION PROCEDURE READ ME = = = = This file is the READ ME for the migration = = procedure from Arkeia v5.3.x or v5.5.x to Arkeia v6.x = = = = Version 1.1 released on 2006-10-03 = = = = Copyright (c) 2006 by Arkeia Corporation, = = All Rights Reserved. = = = =========================================================== =========================================================== = NOTATION = =========================================================== = In the rest of this document 5.y will stand for = = 5.3 OR 5.5 = =========================================================== =========================================================== = NOTE = =========================================================== = If you migrate from a version prior to 5.3, you need to = = migrate to 5.3 FIRST. = =========================================================== =========================================================== = WARNING!! = =========================================================== = PLEASE NOTE: = = = = While Arkeia Corporation has tried to provide a = = complete and fairly "safe" migration procedure for its = = products, your should be aware that this = = procedure can have potentially destructive effects = = on existing Arkeia v5.y.x servers. = = = = ARKEIA CORPORATION RECOMMENDS THAT YOU READ AND = = UNDERSTAND THIS FILE BEFORE ATTEMPTING THE MIGRATION = = PROCEDURE. = = = = FURTHERMORE, ARKEIA CORPORATION DISCLAIMS ANY LIABILITY = = FOR THE LOSS OF DATA RESULTING FROM THE USE OF THIS = = PROCEDURE. EXCEPT WHEN OTHERWISE STATED IN WRITING = = ARKEIA CORP AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS= = IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR = = IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED = = WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A = = PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY = = AND PERFORMANCE OF THE PROGRAM IS WITH YOU. = =========================================================== = WARNING!! = =========================================================== TABLE OF CONTENTS ================= 1. What is the migration procedure? 2. Obtaining the migration procedure. 3. Running the migration procedure on a server. 3.0 Keep a copy of the v5.y.x configuration. 3.1 Required operations before migration. 3.2 Upgrade the arkeia server backup to v6.x 3.3 Running the migration procedure 3.4 Tasks to be performed after the migration. 3.5 Test the migrated new version. 4. Running the migration procedure on a client. 5. How to obtain help on the migration procedure. 1. What is the migration procedure? =================================== The Arkeia migration procedure is designed to ease the transition from Arkeia 5.y to Arkeia 6.0 This migration procedure can be run manually or by script. It is designed to preserve the maximum amount of user information and configuration parameters, so that the existing v5.y.x configuration will be carried over to the new 6.x version of Arkeia, with minimal adjustment by the system administrator. Applying the migration procedure to an existing Arkeia v5.y.x server allows the administrator to transfer the following information to the Arkeia 6.x server: -- FILE Tape configuration. -- Drive configuration. 2. Obtaining the migration procedure. ===================================== The Arkeia migration procedure from the following sources: - the Arkeia Corporation web site, at the following URL: http://www.arkeia.com - the 6.0 arkeia backup server packages, where it can be found in the following directory: /opt/arkeia/bin/migration The procedure is installed by default at the same time as the Arkeia server. PLEASE NOTE: The Arkeia v5.y license must be upgraded to an Arkeia v6.0 license or the migration procedure will not be able to work properly. Please contact the Arkeia Sales Team for more information. 3. Running the migration procedure on an Arkeia server. ======================================================= The migration procedure requires these steps: - Make a copy of the v5.y configuration, for safety. - Close down Arkeia processes. - Run the migration, either manually or by script. - Delete the GUI preferences file. - Test the new version. 3.0 Keep a copy of the Arkeia v5.y configuration ------------------------------------------------ The automatic procedure makes a copy of the arkeia parts that will be migrated. We suggest you to make a copy yourself before starting modifications. * Make your own copy of the following directory (a) The Arkeia tape cartridge directory: /opt/arkeia/server/dbase/f3tape (b) The arkeia drive directory: /opt/arkeia/server/dbase/f3drv PLEASE NOTE: Although the automatic procedure will make these copies, it is absolutely ESSENTIAL to make them BEFORE the migration procedure itself is launched IF THE MIGRATION FAILS, AND YOU HAVE NOT MADE THESE COPIES, YOU MAY LOSE ALL YOUR BACKED UP DATA!! 3.1 Required operations before the migration -------------------------------------------- The following operations must be performed BEFORE attempting the migration of an Arkeia v5.y.x server to an Arkeia v6.x: * Stop all the Arkeia v5.y.x processes: (a) Stop all jobs and backup, restore or verification operations. (b) Stop all library processes (Library management + stop library) (all arkvlib, arklib processes must be stopped). (c) Quit the Arkeia v5.y.x GUI. (No "arktrans" processes should be left running). 3.2 Upgrade the arkeia server backup to v6.x ---------------------------------------------- For the moment, upgrade only the Arkeia backup server v5.y using rpm package or .tar.gz * Stop Arkeia v5: Arkeia version 5 must be stopped BEFORE the migration procedure can be started. To do this, enter this command as root: /opt/arkeia/bin/arkboot stop Check that all the Arkeia processes have been stopped by entering this command as root: ps -faxuw | grep ark 3.3 Starting the migration -------------------------- The migration can be run as a script, or manually. 3.3.1 Running the migration procedure script -------------------------------------------- To run the migration procedure, simply enter the following command as root: /opt/arkeia/bin/migration/arkmigrate-53-60 The following options must be supplied on the command line: --path [VALUE] Arkeia v5.y.x root directory. (Default is : /opt/arkeia). For example, the following command, entered as root, would perform a valid migration from the Arkeia v5.y.x to the new Arkeia v6.x, located in the directory /usr/local/arkeia /opt/arkeia/bin/migration/arkmigrate-53-60 --path /usr/local/arkeia Follow the instructions printed on the screen to complete the migration. 3.3.2 Manual migration procedure -------------------------------- The steps needed to manually migrate from v5.y to v6.0 are: - Modify the tape file definitions. - Modify the drive definitions. I) Modification of the "FILE tape" ---------------------------------- You can simulate a tape with "FILE tape", which allows you to write to a disk instead of a real tape. Now, in 6.0, each "FILE tape" has a MEDIA_SERVER property. It determines which host holds the tape. In order to write "FILE tapes", you have to modify their definition. a) cd /opt/arkeia/server/dbase ; tar cvf f3tape53.tar f3tape b) cd /opt/arkeia/server/dbase/f3tape c) grep FILE tp*/*lst tpdir20/tp41a3888b.lst:TP_TYPE "FILE" tpdird/tp41a3880e.lst:TP_TYPE "FILE" d) To make your TapeFiles compatible with 6.0, you must open tpdir20/tp41a3888b.lst with a simple text editor (vi for instance). Then : - add a line: MEDIA_SERVER "" where is the name of the backup server as it is written in /arkeiad/rhost.lst The TapeFiles from 5.y are now compatible with 6.0. II) Modification of the drive ----------------------------- a) cd /opt/arkeia/server/dbase ; tar cvf f3drv53.tar f3drv b) cd /opt/arkeia/server/dbase/f3drv c) To make your drives compatible with 6.0, you must open f3drv/drv*.lst with a simple text editor (vi for instance). Then : - add the following lines: 1) case 1: there is no NDMPID ITEM { "MEDIA_SERVER" "" "DEFAULT" "" "REWIND_DEV" "" } where is the name of the backup server as it is written in /arkeiad/rhost.lst where is the value of the "REWIND_DEV" property outside the ITEM 2) case 2: there is a NDMPID ITEM { "NDMPID" "" "DEFAULT" "" "REWIND_DEV" "" } where and are respectively the values of the "REWIND_DEV" and "NDMPID" properties outside the ITEM d) Remove lines containing any of the following properties: REWIND_DEV, NONREWIND_DEV, CONTROL_DEV, NDMPID The drives from 5.y are now compatible with 6.0. 3.4 Tasks to be performed after the migration --------------------------------------------- Do not forget to install the v6.0 license using the Arkeia GUI (Graphical User Interface). 3.5 Testing the migrated information ------------------------------------ We recommend that you test the Arkeia v5 server using the migrated information. To do this, follow the steps below: -- File library inventory: -- Start a small backup using file tape. -- Check that you can still use the drives 4. Running the migration procedure on a client machine. ======================================================= There is no need to immediately migrate the client to Arkeia version 6.0: an Arkeia version 6.0 server is backward-compatible and can backup and restore data to v5.y.x clients. Migrating 5.3 clients to 6.0 clients will enable unicode support. 5. Obtaining help on the migration procedure. ============================================= For any problems or issues regarding the migration procedure from Arkeia v5.y.x to Arkeia v6.x, please contact the Arkeia Technical Support Team. The web page for the Technical Support Team is: http://www.arkeia.com/support.html Thank you for using Arkeia version 6. We hope this migration procedure will be useful to you! Arkeia Corp.