Ignite-UX for 10.20 for Visualize C3600 workstation

[dave1000_1]

I recently acquired the Media Kit for 10.20 (10.20 is required for my operating environment). Ignite-UX is on one of the four application CD's. I need to install Ignite-UX on to a single workstation that is not networked at this time to perform a make_recovery to the external tape drive (I do not believe that 10.20 operating envirnonment and/or December 2001 application CD with Ignite-UX was set up to use R/W CD?) for backing up the root, etc. I am in need of the process/commands to allow for me to do this. I do have some material that attempts to address the installation but content is somewhat confusing and contradictory.

I presume that the swinstall command is required. My concern is whether there is anything special that I must do or be aware of during intallation for this to be a successful installation.

Please keep in mind that I am not a UNIX administrator and we do not have a UNIX administrator although I do have a general understanding of UNIX file systems and commands.

This is a high priority for me and therefore an expeditious response is both needed and appreciated. Thanks in advance.

[Steven E. Protter]

Shalom,

You have three possible sources.

1) the OS media from 10.20
2) The last application cd from 10.20
3) If you have a software contract and a forgiving rep in the response center, they might grant temporary access to an ftp site from which to get the latest 10.20 Ignite.

Keep in mind the OS is out of support and HP would be well within their rights to make you ebay it for the media.

SEP

[Pete Randall]

So you just need to install Ignite, not the whole 10.20 Operating System, correct?

You will need to mount the CD that contains the Ignite filesets. If you don't know which CD Ignite is on, you will have to go through them one at a time. Insert the CD into the drive, then mount it with the mount command. First figure out which drive it is with "ioscan -fnCdisk". Look for one that seems CD like:

# ioscan -kfnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE TEAC CD-532E-B
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 10/0/15/1.5.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0

In my case it's the first one, so the mount command would be "mount /dev/dsk/c0t0d0 /cdrom". Your system may have a directory called something other than "/cdrom". Then use the swinstall command to see the contents of the CD "swinstall -s /cdrom". Scan the contents of each CD until you locate Ignite, then you can select Ignite for install.

That's the basics. Let us know if you have further questions.


Pete

[dave1000_1]

Thank you. My apologies for not being clear. I know that it is CD #3 and I can mount/umount the CD drive as required.

In the interim I used:

swinstall -s /SD_CDROM Ignite-UX-10-20

(Ignite-UX-10-20 is the directory for Ignite 10.20 Revision 3.5.89 on the CD).

The command was successful but I have not as of yet tried to invoke Ignite-UX via:

/opt/ignite/bin/ignite/make_tape_recovery

My real question was/is there anything special that I must do or be aware of during intallation or usage for this to be successful i.e. some of the material that I have for installation discusses setting up config files and software depots and clients and modifying login scripts, etc.

Since at this juncture my only need is to use Ignite-UX make_tape_recovery to back-up the root, etc., is it an absolute requirement to set up config files and software depots and clients and modify login scripts, etc.?

Thanks in advance.

[dave1000_1]

Yes, sorry, I am only installing the Ignite-UX, not OS.

[Pete Randall]

Ahhh!

In that case, it's pretty simple: no config files or the like, just run the following command:

make_tape_recovery -a /dev/rmt/0mn -I -x inc_entire=vg00

The -a option is used to identify your tape drive. /dev/rmt/0mn will be the default - substitute as needed but be sure to use the now rewind device file. The -I option says to make the subsequent restore interactive so you can adjust LV sizes if needed. You can still interrupt even if you don't specify the -I option, but it's kind of nice to have it pause automatically. The -x inc_entire option tells it you want everything in vg00, not just what Ignite deems important.


Pete

[Pete Randall]

Sorry - "no rewind", not "now rewind".

The fingers apparently think the weekend is already here!


Pete

[dave1000_1]

Hello Pete, thank you. Such is my luck I have further questions.

When archiving I get the following warnings:

a "The version of pax on the system to be
archived needs to be patched with one of
the following patches or newer ones. If
you do not load the pax patch some files
will not be correctly archived."

System OS Patch needed
10.20 PHCO_20388

I located the patch on the Support Plus
CD. Question is whether I indeed need
this patch, and, if so, what is the
correct protocol for installation.

b "list_expander returned a warning,
please check the log file"

Questions are where is the log file and
whether this warning is important, and,
if so, how to resolve.

Toward the end of the archiving it shows 14,529+1 records in, 14,529+1 records out, and at the end it shows
"make_tape_recovery ... completed with warnings".

Question is whether the above constitutes a valid backup with the errors listed.

Lastly, the sequence I use to create the tape archive is first install tape and rewind, then invoke the make_tape_recovery ... command per your prior post. When I attempt to read the tape after archiving using
tar -tvf /dev/rmt/0m I get either:

Tar: blocksize =4
directory checksum error

or

Tar: blocksize =0; broken pipe?

or

Tar: tape read error

or

tape will actually be read!

This is across both tape readers. When I install an older tape with content it reads the tape as expected every time.

I will update all points when completed.

This is a high priority for me. Expeditious response is needed and appreciated. Thanks in advance.

[Pete Randall · Accepted solution]

Yes, you definitely need the patch. Just use swinstall:

mount the cd, then
swinstall -s /full_path_to_patch


Pete

[dave1000_1]

The Ignite-UX documentation is unclear. Some of it describes to copy the patch to /tmp and then go to this directory and unshare patch using:

sh PHCO_20388

Then states for standalone system run swinstall with command:

swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_20388.depot

Does any of this apply? Will simply using

swinstall -s /full_path_to_patch

ensure that patch is installed properly i.e. shared? and in proper directory?

Thanks in advance.

[TTr]

> The Ignite-UX documentation is unclear...

It assumes that you have downloaded the patch as a single file in shar format.

Since you have the patch on CD, mount the cd and try the same command as when you installed ignite.

swinstall -s /SD_CDROM PHCO_20388

or run swinstall interactively.

[Dennis Handly]

swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_20388.depot

>Does any of this apply?

With some simple corrections:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHCO_20388.depot \*

Those two -x options are probably a good habit to get into.

[dave1000_1]

Patch is located on CD at:

700QPK1020/PHCO_20388/PHCO_20388

2nd PHCO_20388 above is the directory with files sbin and usr which I believe to be the patch contents.

When I attempt to use:

swinstall -s /SD_CDROM PHCO_20388

or

swinstall -s /SD_CDROM/[space] 700QPK1020/PHCO_20388/PHCO_20388

I get ERROR: The depot "hpt04:/SD_CDROM exists but is currently empty. Source connection failed for "hpt04:/SD_CDROM".

When I attempt to use:

swinstall -s /SD_CDROM/700QPK1020/PHCO_20388
/PHCO_20388

I get a SD_Install window and then ERROR: There is currently no depot software on host "hpt04" at location ...

Not sure what is wrong. Note that I generated the /SD_CDROM depot above for debug purposes only.

Thanks in advance.

[dave1000_1]

Before I generated the depot I was getting the same results. The commands entered seem to seek a depot?

[dave1000_1]

And I did not configure Ignite-UX for depot!

[Dennis Handly]

>Patch is located on CD at:
700QPK1020/PHCO_20388/PHCO_20388

Ok, to be able to swinstall you have to swlist.

>2nd PHCO_20388 above is the directory with files sbin and usr which I believe to be the patch contents.

No, you have already looked too far under the covers. :-)

Try this:
swlist -s /SD_CDROM/700QPK1020/PHCO_20388

If that shows the patch, then:
swinstall -s /SD_CDROM/700QPK1020/PHCO_20388 \*

[dave1000_1]

Thank you. But ...

In root (su) if I use your swlist command per prior post I get

ERROR: The expected depot or root does not exist at "/SD_CDROM/700QPK1020/PHCO_20388"

ERROR: There is currently no depot software on host "hpt04" at location
"/SD_CDROM/700QPK1020/PHCO_20388"

If I use

swinstall -s /SD_CDROM/700QPK1020/PHCO_20388

I get a SD Install - Software Selection (hpt04) window and then a Error (hpt04) window that states There is currently no depot software on host "hpt04" at location
"/SD_CDROM/700QPK1020/PHCO_20388"

When I click OK I get a Note (hpt04) window that states The default source
"/SD_CDROM/700QPK1020/PHCO_20388" does not
exist or is not a valid source and there are no other registered depots on hpt04. You can type in the depot path on this host or choose a different host.

When I click OK I get a Specify Source (hpt04) window and selected the following when I generated the debug /SD_CDROM depot:

Source Depot Type: Local CDROM
Source Host Name: hpt04 (system selected)
Source Depot Path: /SD_CDROM

When I click OK I get Error (hpt04) window
that states The depot "hpt04:/SD_CDROM" exists but is currently empty".

If I change Source Depot Path to
/SD_CDROM/700QPK1020/PHCO_20388

and click OK I get Error (hpt04) window that states There is currently no depot software on host "hpt04" at location
"/SD_CDROM/700QPK1020/PHCO_20388"

Ahh the pain. Thanks in advance.

[dave1000_1]

The patch now loads. I had to go into the GUI and get it to work. Now I do not get the pax warning.

However, when I use your prior command (my tape drive is 1mn)

make_tape_recovery -a /dev/rmt/1mn -I -x inc_entire=vg00

I get Warning which states "... volume group /dev/dsk/c0t5d0 will only be partially included ..." and Warning "list_expander returned a warning, please check the log file", and at the end of archiving I believe it states completed with warnings

When I try command

make_tape_recovery -a /dev/rmt/1mn

I get Warning which states "... volume group /dev/dsk/c0t5d0 will only be partially included ..." although at the end of archiving it states successful

When I try command

make_tape_recovery -A -a /dev/rmt/1mn

I get no Warnings and at the end of archiving it states successful

Lastly, and reiterating somewhat from prior post, the sequence I use to prepare the tape for archive is first install tape and rewind, then invoke the make_tape_recovery commands per above. Regardless of command used when I attempt to read the tape after archiving using

tar -tvf /dev/rmt/1m or /1mn I get either:

Tar: blocksize =4
directory checksum error

or

Tar: blocksize =0; broken pipe?

or

Tar: tape read error

or

tape seems to actually read correctly as the archived files scroll on the monitor!

The tape drive is a HP C1537A DDS-3 12GB/24GB and I am using older 60m/90m DDS-1/2 (I believe?) 2GB/4GB tapes, the same tape type with content on it from years ago that I can read consistently. Maybe the archive tape should not be read back? Maybe the command I use to read is not entirely sufficient for the way the archive is written to the tape? Aside note I have just ordered 125m DDS-3 12GB/24GB for the final backup media.

I am close but seemingly so far away.

Thanks in advance.

[Dennis Handly]

>In root (su) if I use your swlist command per prior post I get

Hmm, I'm not sure where the root of the depot is. My next suggestion would be to try:
swinstall -s /SD_CDROM/700QPK1020

If that doesn't work, please provide this output in an attached file:
find /SD_CDROM -type d

And if not too large, only attach this:
find /SD_CDROM

[dave1000_1]

Not sure what to do with your last post. The patch is now installed and the pax warning is gone.

[Dennis Handly]

>Not sure what to do with your last post.

My reply was for your previous reply, "Ahh the pain". What was the final path that worked?

>Maybe the command I use to read is not entirely sufficient for the way the archive is written to the tape?

Yes, you need to skip forward some number of files before you can use tar. An advanced forum search shows these threads:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=749664
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=16520
mt -f /dev/rmt/1mn fsf 1

[dave1000_1]

Thank you. It appears that I can read the archive with the fsf 1. The path

swinstall -s /SD_CDROM/700QPK1020

opened up a GUI that allowed me to select a patch and subsequently install.

One (last?) question: Modified from my prior post, and noting that my tape drive is 1mn

When I use the command

make_tape_recovery -a /dev/rmt/1mn -I -x inc_entire=vg00

I get a Warning which states "... volume group /dev/dsk/c0t5d0 will only be partially included ..." and a Warning which states "list_expander returned a warning, please check the log file", and at the end of archiving I believe it states completed with warnings

When I use the command

make_tape_recovery -A -a /dev/rmt/1mn

I get no Warnings and at the end of archiving it states successful

However, my understanding is that the first command

make_tape_recovery -a /dev/rmt/1mn -I -x inc_entire=vg00

is the most inclusive command for backup

and my understanding is that the second command

make_tape_recovery -A -a /dev/rmt/1mn

is either close to or equal to the first command in terms of inclusiveness

Since I do not know why I get 2 Warnings when using the first command and 0 Warnings when using the second command, based on the specific Warnings and command inclusiveness, is it more prudent for me to use the first or the second command for Ingite-UX tape backups going-forward?

I will update points soon for all.

Thanks in advance.