Difference between revisions of "Vital Signs HPUX Server Migration"
>Jeremyb |
>Jeremyb |
||
| 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. | This document will present a scenario of migrating an existing Vital Signs install from a PA-RISC HPUX system to an ITANIUM HPUX system. | ||
| + | |||
==Step 1 - HPUX Software Dependencies== | ==Step 1 - HPUX Software Dependencies== | ||
| Line 8: | Line 9: | ||
* [https://wiki.vital-soft.com/index.php?title=Installing_the_Python_depot_for_HPUX_via_Sam Python 2.7.3] | * [https://wiki.vital-soft.com/index.php?title=Installing_the_Python_depot_for_HPUX_via_Sam Python 2.7.3] | ||
* [https://wiki.vital-soft.com/index.php?title=Installing_the_Configobj_Python_Module Python Configobj] | * [https://wiki.vital-soft.com/index.php?title=Installing_the_Configobj_Python_Module Python Configobj] | ||
| − | |||
| − | |||
| 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 | |
| − | + | * /var/summit/spectrum/LIVE/vsdata | |
| − | |||
| Line 36: | Line 34: | ||
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/vsdata | ||
| + | |||
==Step 3 - Link Creation== | ==Step 3 - Link Creation== | ||
| Line 43: | Line 42: | ||
su root | su root | ||
ln -fs /ASKPLUS/vsdata/jobs /VSJOBS | ln -fs /ASKPLUS/vsdata/jobs /VSJOBS | ||
| + | |||
==Step 4 - Verification== | ==Step 4 - Verification== | ||
| Line 48: | Line 48: | ||
'''Verify that the following profiles exist in the /ASKPLUS/vsrvtcp.ini file''' | '''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 | su askplus | ||
grep vsdata_ /ASKPLUS/vsrvtcp.ini | 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 | 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 | ||
| Line 90: | Line 84: | ||
$ ls -l /VSJOBS | $ ls -l /VSJOBS | ||
lrwxr-xr-x 1 root sys 20 Apr 21 2011 /VSJOBS -> /ASKPLUS/vsdata/jobs | lrwxr-xr-x 1 root sys 20 Apr 21 2011 /VSJOBS -> /ASKPLUS/vsdata/jobs | ||
| + | |||
| + | |||
| + | ==Step 5 - Test Run Daily / Modify UC4 Jobs== | ||
| + | |||
| + | 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 | ||
Revision as of 00:10, 25 October 2012
Contents
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.
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.
Example scp of /ASKPLUS/vsdata
su askplus scp -rp /ASKPLUS/vsdata askplus@192.168.1.xxx:/ASKPLUS/vsdata
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/vsdata
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 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 755 permissions
- /ASKPLUS/vsdata/scripts/vsftp - /ASKPLUS/vsdata/scripts/vsreload
$ ls -l /ASKPLUS/vsdata/scripts/vs* -rwxr-xr-x 1 askplus users 7951 Oct 17 10:23 /ASKPLUS/vsdata/scripts/vsftp -rwxr-xr-x 1 askplus users 11633 Sep 6 11:07 /ASKPLUS/vsdata/scripts/vsreload
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
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
