Cool Solutions

Physical to Virtual Migration Procedures for NetWare 6.x



By:

January 25, 2008 6:33 am

Reads: 10426

Comments:1

Score:0

This document describes a set of procedures for restoring a physical NetWare server to a virtual machine following a disaster scenario. In order to follow these procedures, a number of prerequisites are assumed:

  • For each server to be restored, a recent backup image of that server’s SYS volume must be accessible via FTP.
  • A DOS partition image from a VMware install of NetWare must also be accessible. This should be at the same SP level as the production server.
  • Additional volumes needed to fully restore each server must be backed up to tape.
  • A Linux or Windows server with VMware Server software must be available for the target platform.
  • A Portlock Boot CD ISO file is needed on the Vmware server target.

When all of these prerequisites are met, we can proceed with step 1.

Step 1: Creating the Target Virtual Machine

Launch the VMware Server Console and create a new virtual machine. Choose Typical for the Virtual Machine Configuration. Next select Novell NetWare version 6.

Click to view.

Give the new machine a meaningful name that others would recognize and choose a location for the virtual disk that will be created.

Click to view.

Select Use Bridged Networking for the Network Type. Next, specify the disk capacity in Gigabytes. Be sure to choose a size larger than the total amount of data contained in the SYS volume image. 20 GB should be large enough for most SYS images, however you must also make sure that the disk is large enough to contain the DATA volume as well unless you plan on storing the DATA volume on a separate virtual disk.

Click to view.

Once the disk space has been allocated, select Edit virtual machine settings. Specify the amount of RAM to allocate to the virtual machine. At least 512 MB is recommended for NetWare 6.5. Configure the CD-ROM device to mount the Portlock Boot CD ISO file.

Click to view.

Once the virtual machine is configured, power it on. It should boot to the Portlock Linux Boot CD.

Click to view.

Step 2: Restoring the Image to the Virtual Machine

Accept the license agreement and choose Configure TCP/IP from the main menu. Choose the View Selected TCP/IP Configuration option and select eth0 for the Ethernet Device ID. If there is an active DHCP server on the network, no manual configuration should be necessary and the network information should already be provided.

Click to view.

If there is no DHCP server, the network configuration must be provided manually. After the IP address, subnet mask, and gateway address have been manually added, return to the main menu and choose Select Portlock Storage Manager. Cancel out of any license renewal or software update options. On the Select OS and Version menu, choose NetWare 6.5.

Click to view.

From the Main Menu choose Restore -> Read Image From an FTP Server.

Click to view.

Enter the IP address of the FTP server, file name of the volume image (case sensitive,) and FTP user/password. The first volume restored should be a DOS partition containing the Netware boot files. This should be made in advance using a barebones install of Netware at the appropriate SP level of the production server.

Accept all defaults and hit <Enter> to restore the DOS partition.

Click to view.

Once the DOS partition has been restored, repeat the steps to restore the SYS volume of the production server.

After the DOS partition and SYS volume have been restored successfully, reboot the server to continue.

Step 3: Preparing for Tape Restore

On the first boot after a successful Portlock restore, the virtual server will run a consistency check on the DOS partition. This is normal and should not prevent the machine from booting into NetWare.

Click to view.

The server will complain that it can’t load the NIC drivers because it will attempt to load them for the old physical NIC.

Click to view.

At the Netware console type inetcfg and hit enter. From the menu select Boards.
Delete any boards displayed.

Click to view.

Hit the <Insert> key and choose CNEAMD Novell Ethernet NE2100 driver from the list. This will take you directly to the Board Configuration menu. In the Board Name field, name the adapter CNEAMD1 and hit <Enter>. Hit <ESC> and select yes when prompted to save the settings.

Click to view.

Hit <ESC> to go back to the main menu and select Bindings. Hit <Insert> and hit <Enter> at the TCP/IP protocol selection prompt. Choose A NetWork Interface when prompted what to bind to. Choose CNEAMD1 (or whatever the interface was named in the previous step) and hit <Enter>. Enter the old IP address and subnet mask of the server.

Click to view.

Return to the main menu and choose Reinitialize System. Verify connectivity by pinging a router or another server.

Once connectivity has been established in NetWare, we need to create a target for the tape backup to be restored to. At the NetWare console, type nssmu and hit <Enter>. At the main menu select Pools. Hit <Insert> to create a new pool and name it DATA2 (the server will give an NDS error if the pool name is identical to the old one.)

Click to view.

Select the partition that the pool will reside on. There should only be one choice. Enter the size of the new pool. Unless more than one volume needs to be created, the pool can fill the rest of the available space on the virtual disk.

Go back to the main menu and select Volumes. Hit <Insert> to create a new volume and name it DATA. When prompted, do not encrypt. Select DATA2 for the pool that will contain the volume. Accept all defaults and arrow down to Create and hit <Enter>.

Click to view.

After the new volume has been created, reboot the server. At this point, the new virtual server should present a viable target for tape restore from the media server. Follow established procedures to restore the most recent backup from tape to the DATA volume.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

1 Comment

  1. By:hammoud

    I think you are representing here a stand alone Server, what is when you Have more than two Servers and what happens with the existing volume Object? eDirectoy synch bwith the other Servers in the NDS?.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)

Comment

RSS