ITEM: DA2292L

Don't use keyboard input with the sbom_backup command

Question:

Env:
  AIX 4.2
  RISC 390
  Tape 7208-011
  sysback 4.1.1.4  sbom 4.1.1.0

Problem:
  I have mirroring on rootvg setup this way:
  hdisk0 ---> hdisk1
  All of the LVs are mirrored.

  I ran the command this way:
  sbom_backup  -x sbom_sys -v rootvg -p hdisk1

  Notice I did not provide a -F flag, so it only could split one
  LV raw1lv.  The command failed, because I was trying to run a full
  system backup.  It then prompted me to hit enter because of a failure.
  This could be a bad thing if I was running this in cron or in the back ground.
  Should we just let it continue and provide the error at the end or provide
  Here is the output from the command below:

Checking LVM information .. this may take a while ..

A copy of each of the following mirrored logical volumes will be taken offline:
LVname            Temp LVname      Mount point
---------------  ---------------  ----------------------
raw1lv           raw1lvL          None

If a logical volume does not appear in the list, you may re-execute this
command with the -Q flag to indicate why other logical volumes were
excluded.

Saving logical volume maps ..
Disabling system dump device ..
Saving LVM records from hdisk1 ..
Taking physical volume hdisk1 offline .. 
Physical volume hdisk1 is now inactive.
Changing physical volume ID for hdisk1 ...
Creating phantom disk hdisk1_sbom ..
Creating phantom volume group sbomvg1 on disks: hdisk1_sbom
Making logical volume raw1lvL from offline copy ..
1+0 records in
1+0 records out
No filesystems to mount.

Executing Command file: sbom_sys ..
--------------------------------------------------------------------
Directory /sbom does not exist.
--------------------------------------------------------------------

Re-mirroring the volume groups .. please wait ...
-------------------------------------------------
\^G
An error has occurred! Please record the above message, then press ENTER
to restore the volume groups to their original configuration -> 

Recovering from failure .. please wait ..
-----------------------------------------
Removing temporary logical volume raw1lvL ..
Removing the phantom volume group sbomvg1 ..
Restoring original LVM records to hdisk1 ..
Removing the phantom disk hdisk1_sbom ..
Restoring the original physical volume ID to hdisk1 ..
Enabling primary dump device /dev/hd6 ..
Resynchronizing logical volumes. This may take a while ...
Logical volume raw1lv updated
Volume group rootvg updated

The volume groups have been re-mirrored successfully.

Action Taken:
  Open up a problem record with the developer

Response:

 If sbom_backup command started in the background using
 'at' or 'cron' commands, command would terminate on
 errors without resyncing the volume groups. If run in
 background using '&' specifier, the command would hang
 waiting for user input. New "-n" flag added to specify
 that command is run in the background and no attempt
 should be made to read from standard input.
 sbom_backup)

Fixed with sysback.sbom 4.1.1.1




Support Line: Don't use keyboard input with the sbom_backup command ITEM: DA2292L

Dated: May 1997 Category: N/A

This HTML file was generated 99/06/24~13:30:16

Comments or suggestions?
Contact us