ITEM: V0004L

1800-106 unable to read header in smit

Question:

Env:
  AIX 3.2.5 (4.1 will be affected too)
  Sysback ver 3

Desc:
  Customer is trying to restore a file from a system backup
  made with the sysback command in smit and is getting
  this error message:  1800-106 unable to read header in smit

Action:
  The customer made the backup with a block size of 1024 and
  tried to restore the backup with a block size of 512 in 
  smit and it failed with the above error message.

  This is a known bug with sysback ver 3
  
   This is what is happening in smit:

   sysback will first run the sysrestore -tf /dev/rmt\#
   to get the list of the VGs on the sysback tape.  The
   sysrestore command first will set the block_size=512 then read
   a file off of the 4th image (./tmp/...blksz) this file
   contains the block size of the rootvg and other vgs.
   It will set the block_size to that value and rewind and
   fast forward to the 5th images to read the header of the
   rootvg to get the list of all the vgs on this tape.  Once
   that commands runs it will set the bs back to the org
   block size which causes the tape to rewind.  Sysback thinks
   it is still position so on the next read will fail with the
   above error message.

   WORKAROUNDS:
   Set the block size to the value that the backup was made at.
   So if you did the system backup with 1024 set the block size
   to that value.

   Or restore from the command line using the sysrestore command.

   This is a known bug with sysback, it is currently be worked on
   by the devolper without any success.  Seems like a easy fix, 
   but working in smit is not a easy task.  It will be sometime
   before this is fixed.

   This problem will only happen in smit when restoring from 
   a system backup, it should not occur with the sysrestore command
   from the command line.



Support Line: 1800-106 unable to read header in smit ITEM: V0004L

Dated: May 1995 Category: N/A

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

Comments or suggestions?
Contact us