Difference between revisions of "Vital Signs HPUX Server Migration"

From Vital Soft Wiki
Jump to: navigation, search
>Jeremyb
(→‎Step 2 - File Migration)
>Jeremyb
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Overview==
 
==Overview==
−
This document will present a scenario of migrating an existing Vital Signs install from a PA-RISC HPUX system to an ITANIUM HPUX system.
+
How to Migrate an existing Vital Signs install from one HPUX '''production''' system to a new HPUX '''pre-production''' system.
  
−
==Step 1 - Software Dependencies==
+
 
 +
==Step 1 - HPUX Software Dependencies==
 
The following software is required to be installed prior to running Vital Signs.
 
The following software is required to be installed prior to running Vital Signs.
  
−
-AskPlus 8.3.3+
+
* [https://www.vital-soft.com/product-downloads/ AskPlus 8.3.3 or Later]
−
 
+
* [https://wiki.vital-soft.com/index.php?title=Installing_Python_on_HPUX Python 2.7]
−
-Python 2.7.3
+
* [https://wiki.vital-soft.com/index.php?title=Installing_the_Configobj_Python_Module Python Configobj]
−
 
 
−
-Python ConfigObj library
 
  
  
Line 16: Line 15:
 
The following folders should be migrated from the old HPUX system to the new one retaining their file permissions.   
 
The following folders should be migrated from the old HPUX system to the new one retaining their file permissions.   
  
−
- /ASKPLUS/vsdata
+
* /ASKPLUS/vsdata
−
- /var/summit/spectrum/LIVE/vsdata
+
* /var/summit/spectrum/LIVE/vsdata
 +
 
  
 
This is possible using the scp command with -rp, r stands for recursive copy and p stands for preserve.
 
This is possible using the scp command with -rp, r stands for recursive copy and p stands for preserve.
Line 27: Line 27:
  
 
     su askplus
 
     su askplus
−
     scp -rp /ASKPLUS/vsdata askplus@192.168.1.xxx:/ASKPLUS/vsdata
+
     scp -rp /ASKPLUS/vsdata askplus@192.168.1.xxx:/ASKPLUS/
  
  
Line 33: Line 33:
 
      
 
      
 
     su bolive
 
     su bolive
−
     scp -rp /var/summit/spectrum/LIVE/vsdata bolive@192.168.1.xxx:/var/summit/spectrum/LIVE/vsdata
+
     scp -rp /var/summit/spectrum/LIVE/vsdata bolive@192.168.1.xxx:/var/summit/spectrum/LIVE/
  
 
==Step 3 - Link Creation==
 
==Step 3 - Link Creation==
  
−
A symbolic link for the jobs directory should be created as root
+
A symbolic link for the jobs directory should be created as root on the new system
  
 
     su root
 
     su root
 
     ln -fs /ASKPLUS/vsdata/jobs /VSJOBS
 
     ln -fs /ASKPLUS/vsdata/jobs /VSJOBS
 +
 +
 +
==Step 4 - Verification==
 +
 +
'''Verify that the datachng.so(.sl) exists in the /ASKPLUS directory'''
 +
 
 +
  #Example PA-risc
 +
  $ ls -l /ASKPLUS/datachng*
 +
  -rwxr-xr-x  1 askplus    users        69792 Jan 19  2012 /ASKPLUS/datachng.sl
 +
 +
  #Example Itanium
 +
  $ ls -l /ASKPLUS/datachng*
 +
  -rwxr-xr-x  1 askplus    users        69792 Jan 19  2012 /ASKPLUS/datachng.so
 +
 +
 +
''NOTE : If you are migrating from PA-risc to ITANIUM you need to download the datachng.so file : [https://vital-soft.com/download/secure/vitalsigns/CU_Install/DataChng/datachng.so Download datachng.so]
 +
 +
''NOTE : If you are migrating from ITANIUM to PA-risc you need to download the datachng.sl file : [https://vital-soft.com/download/secure/vitalsigns/CU_Install/DataChng/datachng.so Download datachng.sl]
 +
 +
 +
 +
'''Verify that the following profiles exist in the /ASKPLUS/vsrvtcp.ini file'''
 +
 +
* [vsdata_test]
 +
* [vsdata_live]
 +
* [vsdata_test_eom]
 +
* [vsdata_live_eom]
 +
* [vsdata_test_restore]
 +
* [vsdata_live_restore]
 +
 +
    su askplus
 +
    grep vsdata_ /ASKPLUS/vsrvtcp.ini
 +
   
 +
 +
If they do '''NOT''' exist, copy them from the existing vsrvtcp.ini on the old system '''OR''' do the following to add them and then compare them to the profiles on the old system
 +
 +
    su askplus
 +
    cd /ASKPLUS/vsdata
 +
    ./vsinstall
 +
   
 +
    #Verify again
 +
    grep vsdata_ /ASKPLUS/vsrvtcp.ini
 +
   
 +
 +
'''Verify that the following files have 750 permissions'''
 +
 +
- /ASKPLUS/vsdata/scripts/vs*
 +
 +
    $ ls -l /ASKPLUS/vsdata/scripts/vs*
 +
    -rwxr-x---  1 askplus    users        21500 Dec 18 16:33 /ASKPLUS/vsdata/scripts/vsftp
 +
    -rwxr-x---  1 askplus    users        14628 Dec 18 16:33 /ASKPLUS/vsdata/scripts/vsreload
 +
 +
 +
- /ASKPLUS/vsdata/jobs/*
 +
 +
    $ ls -l /ASKPLUS/vsdata/jobs
 +
    -rwxr-x---  1 askplus    users        11744 Dec 18 16:33 JVSLOAD_GLDATA
 +
    -rwxr-x---  1 askplus    users        21619 Dec 18 16:33 JVSLOAD_HIST
 +
    -rwxr-x---  1 askplus    users        16834 Dec 18 16:33 JVSLOAD_MBRSHLN
 +
    -rwxr-x---  1 askplus    users        6310 Dec 18 16:33 JVSLOAD_OANR
 +
    -rwxr-x---  1 askplus    users        11673 Dec 18 16:33 JVSRELOAD
 +
 +
 +
'''Verify that the /VSJOBS link exists'''
 +
 +
    $ ls -l /VSJOBS
 +
    lrwxr-xr-x  1 root      sys            20 Apr 21  2011 /VSJOBS -> /ASKPLUS/vsdata/jobs
 +
 +
==Step 5 - Test Run Daily / Modify UC4 Jobs==
 +
 +
Before running a test run, we must make sure to disable the FTP portion of Vital Signs so we don't push bad data from the '''pre-production''' database to Vital Signs.
 +
 +
    su askplus
 +
    cd /ASKPLUS/vsdata
 +
   
 +
    # Edit vitalsigns.ini
 +
    vi vitalsigns.ini
 +
 +
    # Comment out the existing VS_HOSTIP and replace it with an empty one as shown below
 +
    cat vitalsigns.ini
 +
   
 +
    # Vital Signs Configuration File:
 +
    # -------------------------------
 +
    # FTP_USER      - Vital Signs server - FTP username
 +
    # FTP_PASSWD    - Vital Signs server - FTP password
 +
    # FTP_PORT      - Vital Signs server - FTP password
 +
    # VS_PID        - A unique run ID
 +
    # VS_HOSTIP    - IP address of the Vital Signs Server
 +
    # VS_HOSTPORT  - Port for the Vital Signs listener
 +
    # VS_PATH      - The path on the Vital Signs Server.
 +
    #                (Must be a full path from the FTP login.)
 +
    # VS_WORKPATH  - The path where temporary extracts are stored. Default: /var/summit/spectrum/LIVE
 +
   
 +
    FTP_USER=vitalsigns
 +
    FTP_PASSWD=pswd
 +
    FTP_PORT=21
 +
    VS_PID=`VS_$$`
 +
    #VS_HOSTIP=192.168.1.xxx
 +
    VS_HOSTIP=
 +
    VS_HOSTPORT=30601
 +
    VS_PATH=/vitalsigns/CU1
 +
    VS_WORKPATH=/var/summit/spectrum/LIVE
 +
 +
 +
 +
Now that all of the prior steps have been completed successfully, run a test daily extract for History and Membership Analysis
 +
 +
    su bolive
 +
    cd /var/summit/spectrum/LIVE
 +
    /VSJOBS/JVSLOAD_HIST
 +
   
 +
    #When JVSLOAD_HIST finishes, run
 +
    /VSJOBS/JVSLOAD_MBRSHLN
 +
 +
 +
If these test runs do not have any issues then update the UC4 jobs to point at the new Host and give yourself a big pat on the back.

Latest revision as of 19:17, 6 February 2014

Overview

How to Migrate an existing Vital Signs install from one HPUX production system to a new HPUX pre-production system.


Step 1 - HPUX Software Dependencies

The following software is required to be installed prior to running Vital Signs.


Step 2 - File Migration

The following folders should be migrated from the old HPUX system to the new one retaining their file permissions.

  • /ASKPLUS/vsdata
  • /var/summit/spectrum/LIVE/vsdata


This is possible using the scp command with -rp, r stands for recursive copy and p stands for preserve.

Scp man.PNG


Example scp of /ASKPLUS/vsdata 

   su askplus
   scp -rp /ASKPLUS/vsdata askplus@192.168.1.xxx:/ASKPLUS/


Example scp of /var/summit/spectrum/LIVE/vsdata 

   su bolive
   scp -rp /var/summit/spectrum/LIVE/vsdata bolive@192.168.1.xxx:/var/summit/spectrum/LIVE/

Step 3 - Link Creation

A symbolic link for the jobs directory should be created as root on the new system 

   su root
   ln -fs /ASKPLUS/vsdata/jobs /VSJOBS


Step 4 - Verification

Verify that the datachng.so(.sl) exists in the /ASKPLUS directory 

  #Example PA-risc
  $ ls -l /ASKPLUS/datachng*
  -rwxr-xr-x   1 askplus    users        69792 Jan 19  2012 /ASKPLUS/datachng.sl

  #Example Itanium
  $ ls -l /ASKPLUS/datachng*
  -rwxr-xr-x   1 askplus    users        69792 Jan 19  2012 /ASKPLUS/datachng.so


NOTE : If you are migrating from PA-risc to ITANIUM you need to download the datachng.so file : Download datachng.so

NOTE : If you are migrating from ITANIUM to PA-risc you need to download the datachng.sl file : Download datachng.sl


Verify that the following profiles exist in the /ASKPLUS/vsrvtcp.ini file

  • [vsdata_test]
  • [vsdata_live]
  • [vsdata_test_eom]
  • [vsdata_live_eom]
  • [vsdata_test_restore]
  • [vsdata_live_restore]
   su askplus
   grep vsdata_ /ASKPLUS/vsrvtcp.ini

If they do NOT exist, copy them from the existing vsrvtcp.ini on the old system OR do the following to add them and then compare them to the profiles on the old system 

   su askplus
   cd /ASKPLUS/vsdata
   ./vsinstall
   
   #Verify again
   grep vsdata_ /ASKPLUS/vsrvtcp.ini

Verify that the following files have 750 permissions

- /ASKPLUS/vsdata/scripts/vs* 

   $ ls -l /ASKPLUS/vsdata/scripts/vs*
   -rwxr-x---   1 askplus    users        21500 Dec 18 16:33 /ASKPLUS/vsdata/scripts/vsftp
   -rwxr-x---   1 askplus    users        14628 Dec 18 16:33 /ASKPLUS/vsdata/scripts/vsreload


- /ASKPLUS/vsdata/jobs/* 

   $ ls -l /ASKPLUS/vsdata/jobs
   -rwxr-x---   1 askplus    users        11744 Dec 18 16:33 JVSLOAD_GLDATA
   -rwxr-x---   1 askplus    users        21619 Dec 18 16:33 JVSLOAD_HIST
   -rwxr-x---   1 askplus    users        16834 Dec 18 16:33 JVSLOAD_MBRSHLN
   -rwxr-x---   1 askplus    users         6310 Dec 18 16:33 JVSLOAD_OANR
   -rwxr-x---   1 askplus    users        11673 Dec 18 16:33 JVSRELOAD


Verify that the /VSJOBS link exists 

   $ ls -l /VSJOBS
   lrwxr-xr-x   1 root       sys             20 Apr 21  2011 /VSJOBS -> /ASKPLUS/vsdata/jobs

Step 5 - Test Run Daily / Modify UC4 Jobs

Before running a test run, we must make sure to disable the FTP portion of Vital Signs so we don't push bad data from the pre-production database to Vital Signs. 

   su askplus
   cd /ASKPLUS/vsdata
   
   # Edit vitalsigns.ini
   vi vitalsigns.ini

   # Comment out the existing VS_HOSTIP and replace it with an empty one as shown below
   cat vitalsigns.ini
   
   # Vital Signs Configuration File:
   # -------------------------------
   # FTP_USER      - Vital Signs server - FTP username
   # FTP_PASSWD    - Vital Signs server - FTP password
   # FTP_PORT      - Vital Signs server - FTP password
   # VS_PID        - A unique run ID
   # VS_HOSTIP     - IP address of the Vital Signs Server
   # VS_HOSTPORT   - Port for the Vital Signs listener
   # VS_PATH       - The path on the Vital Signs Server.
   #                 (Must be a full path from the FTP login.)
   # VS_WORKPATH   - The path where temporary extracts are stored. Default: /var/summit/spectrum/LIVE
   
   FTP_USER=vitalsigns
   FTP_PASSWD=pswd
   FTP_PORT=21
   VS_PID=`VS_$$`
   #VS_HOSTIP=192.168.1.xxx
   VS_HOSTIP=
   VS_HOSTPORT=30601
   VS_PATH=/vitalsigns/CU1
   VS_WORKPATH=/var/summit/spectrum/LIVE


Now that all of the prior steps have been completed successfully, run a test daily extract for History and Membership Analysis 

   su bolive
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_HIST
   
   #When JVSLOAD_HIST finishes, run
   /VSJOBS/JVSLOAD_MBRSHLN


If these test runs do not have any issues then update the UC4 jobs to point at the new Host and give yourself a big pat on the back.

Retrieved from "https://wiki.vital-soft.com/index.php?title=Vital_Signs_HPUX_Server_Migration&oldid=998"