LOCKSS on LINUX Network Data Transition 02/17/2011 1
Table of Contents Overview... 3 Prerequisites... 4 Network Transition Checklist... 5 Network Setup... 7 Test the Network Setup... 9 Create Transfer Script... 10 Run Transfer Script... 12 Appendix A: Netmask CIDR Translations... 13 Please read these instructions carefully if you have any questions, contact us by email at lockss-support@lockss.org we are here to support you through this process. 2
Overview This document explains how to transition archived content from an OpenBSD LOCKSS box to a Linux LOCKSS box over the network. It is one of two methods for data transition available the other method is disk-to-disk data transition and is preferred when an OpenBSD LOCKSS box has been reinstalled with Linux. This document is organized in the following sections: 1. Prerequisites Details about your OpenBSD LOCKSS box and your Linux LOCKSS box are discussed here. 2. Network Transition Checklist Gathering information about your OpenBSD and Linux LOCKSS boxes and downloading the LOCKSS Transition CD. 3. Network Setup Booting the OpenBSD LOCKSS box with the LOCKSS Transition CD and running a program to configure the network. 4. Data Transfer Generating and running the transfer script. Getting Help! If you have any difficulty during your network transition, please email your questions to lockss-support@lockss.org and we ll get back to you as soon as we can. 3
Prerequisites There are four prerequisites you should satisfy before starting the network data transition procedure. 1. Schedule downtime with your users - The network data transition could take anywhere from a day to a week, depending on how much archived content needs to be transitioned, as well as the quality and congestion of your network. During this time both LOCKSS boxes will be unavailable to your users. You might consider starting the transition later in the week, allowing it to run over the weekend. 2. OpenBSD LOCKSS Box - It must be connected to your network and configured with a unique IP address. 3. Linux LOCKSS Box It must be connected to your network and configured with a unique IP address (different from your OpenBSD LOCKSS box IP Address). The Linux LOCKSS box must be powered on. The LOCKSS software on the Linux LOCKSS box should already be configured by running the LOCKSS hostconfig program, but the LOCKSS daemon should never have been started. 4. Network Transition Checklist Complete the checklist in the next section and download the LOCKSS Transition CD. You ll need this information and the CD once you decide to start the network transition procedure. 4
Network Transition Checklist You will need to enter several pieces of information during the network transition. Please collect all this information before you start the transition procedure so it s available when you need it. OpenBSD LOCKSS Box Information Gather the following information from your existing OpenBSD LOCKSS box. Network Setup Information OpenBSD IP address OpenBSD Netmask (dotted decimal format) OpenBSD Gateway IP address Value OpenBSD DNS IP address OpenBSD DNS Search Domain NOTE 1: Please refer to the table in Appendix A to convert between CIDR notation and dotted decimal notation. NOTE 2: If you don t know your OpenBSD DNS Search Domain, log in as root on your OpenBSD system and look at the file /etc/resolv.conf. You may use this command to look at the file: cat /etc/resolv.conf Look for the line that begins with the word search to find your DNS search domain. 5
Linux LOCKSS Box Information Gather the following information from your new Linux LOCKSS box. Network Setup Information Linux IP address Value Linux root password Software Download LOCKSS Transition CD If you have not already done so, download and burn the LOCKSS Transition image to a blank CD. The image is published here: http://www.lockss.org/lockss/installing_lockss If you write down the root password on this piece of paper, be sure to store it in a safe place. You should always protect your root password and limit who has access to it. 6
Network Setup Replace the LOCKSS OpenBSD CD with the LOCKSS Transition CD in your OpenBSD LOCKSS box, then log in as root and type in the command shutdown h p now to shutdown your system and power it off. When the shutdown completes, wait three seconds and then power on your OpenBSD LOCKSS box. The LOCKSS Transition CD will take several minutes to boot on your OpenBSD LOCKSS box. When it is done booting, you should see the following screen: Step 1: Go to the net-transfer directory by entering cd net-transfer then hitting the Enter key. Step 2: Start the network setup program by entering./net-setup and then hitting the Enter key. 7
NOTE: Example values are used in the illustrations below for demonstration purposes only. Step 3: Enter the OpenBSD IP address from your Network Transition Checklist, then hit the Enter key: Step 4: Enter the OpenBSD Netmask from your Network Transition Checklist, then hit the Enter key: Step 5: Enter the OpenBSD Gateway IP Address from your Network Transition Checklist, then hit the Enter key: Step 6: Enter the OpenBSD Primary DNS IP Address from your Network Transition Checklist, then hit the Enter key: Step 7: Enter the OpenBSD DNS Search Domain from your Network Transition Checklist, then hit the Enter key: This completes the net-setup program and we are returned to the command prompt. 8
Test the Network Setup Your OpenBSD LOCKSS box should now be functioning on the network. It is critical that your network is working properly for the network transition to be successful, so let s run a few tests first before proceeding. Test 1: At the command prompt, enter ping c 5 lockss.org then hit the Enter key. This command should take 5 10 seconds to complete. Examine the ping statistics at the end: You should see 5 packets transmitted and expect to see 5 received, 0% packet loss Test 2: At the command prompt, try the same command as Test 1, but instead of using lockss.org as your ping target, use the Linux IP address from your Network Transition Checklist. Below is an example of a successful test to a Linux IP address. At the bottom of the screen we see 5 packets transmitted, 5 received, 0% packet loss NOTE: If either test reports packet loss or some other error, you may have a network issue that could prevent the rest of the data transition from completing successfully. Please contact LOCKSS support at lockss-support@lockss.org or your institution s network administrator before continuing with the network transition procedure. 9
Create Transfer Script The network transfer script is dynamically created based on user input and an automatic survey of the Linux LOCKSS box. The following steps create the network transfer script. NOTE: Depending on how much content you have archived, this step could take many hours to complete! Step 1: Start from the command prompt by entering./build-network-transfer then hitting the Enter key. Step 2: Enter the Linux IP address from your Network Transition Checklist, then hit the Enter key: Step 3: Enter the Linux root password from your Network Transition Checklist, then hit the Enter key: Step 4: Hit the enter key to accept the detected OpenBSD disk(s). NOTE: If you see a warning on the line that says Checking remote caches, this could indicate a bigger problem. Please contact LOCKSS support by email at lockss-support@lockss.org 10
The transfer script will now be created. This could take some time, depending on how much archived content is stored on the OpenBSD system. You should see output like this: You may inspect the network transfer script if you like using the command less /tmp/transfer 11
Run Transfer Script Now you are ready to run the transfer script. NOTE: Depending on how much content you have archived, this step could take many days to complete! Step 1: Start the transfer script from the command prompt by entering /tmp/transfer then hitting the enter key. The example below shows a very small transfer. A status line is printed out after each archival unit (AU) has been successfully transferred. The largest AUs are transferred at the beginning of the transfer script, so it might take a while before the first status line appears. 12
Appendix A: Netmask CIDR Translations This Netmask Translation Table shows CIDR values and the equivalent dotted decimal notation. You must supply a netmask in Dotted Decimal Notation when you run the Network Setup program. CIDR Dotted Decimal Notation /1 128.0.0.0 /2 192.0.0.0 /3 224.0.0.0 /4 240.0.0.0 /5 248.0.0.0 /6 252.0.0.0 /7 254.0.0.0 /8 255.0.0.0 /9 255.128.0.0 /10 255.192.0.0 /11 255.224.0.0 /12 255.240.0.0 /13 255.248.0.0 /14 255.252.0.0 /15 255.254.0.0 /16 255.255.0.0 /17 255.255.128.0 /18 255.255.192.0 /19 255.255.224.0 /20 255.255.240.0 /21 255.255.248.0 /22 255.255.252.0 /23 255.255.254.0 /24 255.255.255.0 /25 255.255.255.128 /26 255.255.255.192 /27 255.255.255.224 /28 255.255.255.240 /29 255.255.255.248 /30 255.255.255.252 /31 255.255.255.254 /32 255.255.255.255 13