VTL - Installing VTL application patches via command line

Asset ID:	1-71-1016196.1
Update Date:	2011-04-25
Keywords:

Solution Type Technical Instruction Sure

Solution 1016196.1 : VTL - Installing VTL application patches via command line

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 - Release: 1.0 to 2.0
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076   [Release: 1.0 to 1.0]
Sun StorageTek VTL Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221   [Release: 4.0 to 4.0]
Sun StorageTek VTL Value System - Version: 1.0 - Build 1323 to 1.0 - Build 1323   [Release: 1.0 to 1.0]
All Platforms

Goal

Command line patch install procedure for VTL server.
This technical instruction is intended for field service.

Solution

1. Obtain VTL patch

Approved VTL server patches are available at the USR (Universal Software Repository) web site.
Search on "vtl" or on specific Build number (i.e., "1656"), to locate the build for VTL server you are patching.

Download patch(es) required.

2. Take Xray

Before applying patches run Xray and offload to safe place (do not store on VTL server itself).
NOTE: Also recommend to run Xray after patch install to record successful patch install.

3. Apply the patch

A. Non-disruptive patch on standalone server

1) Copy the patch to the server.
2) Uncompress patch if needed.
3) Set execution permission on the patch by typing the following command:
chmod +x update-vtl1323p1
4) Run the executable patch. For example:
./update-vtl1323p1
5) Copy patch file to /usr/local/vtl/patches on each server (this will allow rollback from Console if required).

B. Disruptive patch on standalone server (e.g., restart of services or reboot required):

1) Copy the patch to the server.
2) Uncompress if needed.
3) Set execution permission on the patch by typing the following command:
       chmod +x update-vtl1323p1
4) If you do not want the patch to stop VTL, stop the server yourself by typing the following command:
       vtl stop
5) Run the executable patch. For example:
       ./update-vtl1323p1
6) If you manually stopped VTL, restart it by typing the following command:
       vtl start (OR reboot server: sync;sync;reboot)
7) Copy patch file to /usr/local/vtl/patches on each server (this will allow rollback from Console if required).

C. Disruptive patch on failover configuration (e.g., restart of services or reboot required):

1) Copy the patch to both servers.
2) Uncompress if needed.
3) On both servers, set execution permission on the patch by typing the following command:
       chmod +x update-vtl1323p1
4) On both servers, suspend failover (via VTL Console GUI).
5) On the secondary server, if you do not want the patch to stop VTL, stop the server yourself by typing the following command:
       vtl stop
6) On the secondary server, run the executable patch. For example:
       ./update-vtl1323p1
7) On the secondary server, if you manually stopped VTL, restart it by typing the following command:
       vtl start (OR reboot server: sync;sync;reboot)
8) On the primary server, if you do not want the patch to stop VTL, stop the server yourself by typing the following command:
       vtl stop
9) On the primary server, run the executable patch. For example:
       ./update-vtl1323p1
10) On the primary server, if you manually stopped VTL, restart it by typing the following command:
       vtl start (OR reboot server: sync;sync;reboot)
11) On both servers, resume failover (via VTL Console GUI)
12) Copy patch file to /usr/local/vtl/patches on each server (this will allow rollback from Console if required).

4. Misc functions

- Check the patch execution log

After patch execution, a log file is generated in /usr/local/-archive directory called update-
You can view this file to get a report about the patch results.

Also, an entry is added to the file $ISHOME/etc/updates to keep track of patches that have been applied.

And the server messages file will also record status of patch install/

- Roll back a patch

Each patch has an option called "rollback" that allows you to undo the patch and restore the original files.
To roll back, use the rollback command. For example:
./update-vtl1323p1 rollback

- Get list of files included in patch

To get a list of files included in the patch, use the option --list. For example:
./update-vtl1323p1 --list

Note: This option only displays the list of files; it does not apply the patch

3. Updating the Console

First, read all server patch txt files for Console upgrade requirements. Look for the statement (or similar) "This fix requires also the Console patch 1323-04"

If a server patch requires a Console patch, a jar file will also be available on the USR site and named "VTL-Console-4.0-1323-04.jar" (following above example). A txt file with same name will also be available. Do the following to update Console:

1. Download the jar file to the workstation running the VTL Console.
2. Rename current 'IPStorConsole.jar' to 'IPStorConsole-old.jar' (or something like that)
3. Copy/rename new 'VTL-Console-4.0-1323-nn.jar' to 'IPStorConsole.jar'
4. Restart VTL Console

For Windows, the jar file is normally under "C:\Program Files\StorageTek\VTL\Console\Bin
For Unix, would be under whatever directory pkgadd was done in (usually /vtlconsole)

==================================================================
Previously Published As
STKKB61591

Attachments

This solution has no attachment