A.6.1 Alternate Pre-Upgrade Backup

This procedure is an alternative to the normal pre-upgrade backup provided in Site Preupgrade Backups. This procedure is a manual alternative backup. It conducts a full backup of the Configuration database and run environment on site being upgraded, so that each server has the latest data to perform a backout, if necessary.

1. Log into the Active SOAM
   Use the SSH command (on UNIX systems – or putty if running on Windows) to log in to the active SOAM:

   ssh admusr@<SOAM_VIP>

2. Start a Screen Session.
   Enter the command:

   $ screen 

   The screen tool creates a no-hang-up shell session, so the command continues to execute if the user session is lost.

3. Backup all servers managed from the SOAM to be upgraded.
   Run the backupAllHosts utility on the active SOAM. This utility remotely accesses each specified server, and runs the backup command for that server.

   The --site parameter allows the user to backup all servers associated with a given SOAM site to be upgraded:

   Caution:

   Failure to include the --site parameter with the backupAllHosts command results in overwriting the NOAM backup file created in Back Up TKLCConfigData Files. Backing out to the previous release is not possible if the file is overwritten.

   $ /usr/TKLC/dpi/bin/backupAllHosts --site=<NEName>

   where <NEName> is the Network Element Name (NEName) as seen using the following command:

   $ iqt NetworkElement

   This output displays when executing either of the options:

   Do you want to remove the old backup files (if exists ) from all the servers (y/[n])?y

   It may take from 10 to 30 minutes for this command to complete, depending upon the number of servers and the data in the database.

   Do not proceed until the backup on each server is completed.

   Output similar to the following indicates successful completion:

   HOSTNAME | STATUS

   --------------------------------------------

   HPC3blade02 | PASS

   HPC3blade01 | PASS

   HPC3blade04 | PASS

   Errors also report to the command line.

   Note:

   There is no progress indication for this command; only the final report when it completes.
4. Exit the Screen Session

   # exit 

   [screen is terminating]

   Note:

   screen -ls is used to show active screen sessions on a server, and screen -dr is used to re-enter a disconnected screen session.
5. Alternative Method to run backup on individual server
   This is an alternative backup method that can be executed on each individual server instead of using the backupAllHosts script. A manual backup can be executed on each server individually, rather than using the script. To do this, log in to each server in the site individually and execute the following command to manually generate a full backup on that server:

   $ sudo /usr/TKLC/appworks/sbin/full_backup 

   Output similar to the following indicates successful completion:

   Success: Full backup of COMCOL run env has completed.

   Archive file /var/TKLC/db/filemgmt/Backup.dsr.blade01.FullDBParts. SYSTEM_OAM.20140617_021502.UPG.tar.bz2 written in /var/TKLC/db/filemgmt.

   Archive file /var/TKLC/db/filemgmt/Backup.dsr.blade01.FullRunEnv. SYSTEM_OAM.20140617_021502.UPG.tar.bz2 written in /var/TKLC/db/filemgmt.

6. Verify Backup Files are Present on Each Server
   1. Log in to the active NOAM GUI using the VIP.
   2. Navigate to Status & Manage, then Files.
   3. Click each server tab.
   4. For each server, verify the following (2) files have been created:
   5. Repeat steps 1 to 4 for each site.