Copy configuration files to a backup location

This topic describes how to copy the networking and SAN File System configuration files before upgrading the SAN File System.

Context

The network and SAN File System configuration files that are currently on the metadata server engine are needed to restart the metadata server engine and add it back to the cluster after upgrading the engine. However, upgrading the metadata server engine to version 2.1 requires that you install a new operating system. Therefore, you will need to tar and copy the configuration files to another location before you proceed.

You can copy the files to any location to which you will have access after upgrading the metadata server. For example, you can copy the configuration files to a diskette.

The following network configuration files need to be included:
  • /etc/HOSTNAME
  • /etc/sysconfig/network/ifcfg-eth*
  • /etc/sysconfig/network/routes
  • /etc/hosts
  • /etc/resolv.conf
The following SAN File System configuration files need to be included:
  • /root/.tank.passwd
  • /etc/password (if it exists)
  • /etc/shadow (if it exists)
  • /etc/tank/server/Tank.Bootstrap
  • /etc/tank/server/Tank.Config
  • /etc/tank/admin/config/tank.properties
  • /etc/tank/admin/config/cimom.properties
  • /usr/tank/admin/truststore
  • /var/tank/server/DR/
  • All of the version 1 administrative command-line interface files you created when you verified the current state of the SAN File System. See Verifying the current state of the SAN File System for more information.

Steps

  1. From the metadata server to be upgraded, tar the network configuration files into a single file. For example, to create a file called network_config_mds2:
    tar -cPvf network_config_mds2 /etc/HOSTNAME /etc/sysconfig/network/ifcfg-eth*
    /etc/sysconfig/network/routes /etc/hosts /etc/resolv.conf
  2. Create a tar file containing the SAN File System configuration files into a single file. For example, to create a file called sfs_config_mds2:
    Remember: Do not forget to include the version 1 files you created when you verified the current state of the SAN File System.
    tar -cPvf network_config_mds2 /root/.tank.passwd /etc/tank/server/Tank.Bootstrap
    /etc/tank/server/Tank.Config /etc/tank/admin/config/tank.properties
    ...remaining files ...
  3. Copy the configuration tar file to a diskette.
    Tip: Rather than copy the file to diskette, you can copy the file to another location in the network, such as the master console. To copy files to the master console, use the pscsp and pftp commands. For information about using these commands, see the PuTTY documentation that is available on the master console.

    If you copy the files to another location in the network, you will need to ensure that you have network connectivity to restore them when needed.

    1. Mount the diskette drive.
      mount /dev/fd0 /media/floppy
    2. Copy the network tar file to a diskette.
      cp network_config_mds2 /media/floppy 
    3. Copy the SAN File system configuration tar file to a diskette.
      cp sfs_config_mds2 /media/floppy 
    4. Verify that the tar files are on the diskette.
      ls /media/floppy 
    5. Unmount the diskette drive and remove the diskette.
      unmount /media/floppy 

Parent topic: Preparing the first engine for upgrade

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.