Workaround for error 0511-163 when using tar as backend for Sysback/6000 V4


About this document
    Related documentation
Workaround options
Sample scripts

About this document

When using Sysback/6000 to back up a system, the tar command can be used as the actual backup process to preserve sparse files, such as those used by Oracle. However, this method may cause problems for backing up the rootvg as tar has a limitation that cannot handle pathnames longer than 100 characters. This document provides two options as workarounds to this situation.

This document applies to AIX Version 4.x and Sysback Version 4.

Related documentation

The AIX 4.3 and RX/6000 product documentation library can be accessed at the following URL:

Additional information can be found in the document "Cloning with mksysb for rootvg and Sysback V4 for Additional Volume Groups", 4FAX Number 8561.

Workaround options

There are two workaround options for this error.

  1. Use mksysb to back up the rootvg, then use the Sysback option to do a volume group backup of the secondary volume groups to another tape. This process is covered in greater depth in the document "Cloning with mksysb for rootvg and Sysback V4 for Additional Volume Groups".

  2. The second option involves writing a script to change the backend that Sysback uses applying the backup command for a Sysback backup of only the rootvg and other non-sparse volume groups. Then tar should be used as the backend, and either a mkvgback should be stacked onto the same tape or written those to a new tape.

    The following steps are necessary only if you intend to use option 2.

    1. Set the Sysback backend to tar. Enter:
           sbdefaults -B tar
    2. Make a copy of the /usr/lpp/sysback/.settings file with the tar setting. Enter:
           cp /usr/lpp/sysback/.settings /usr/lpp/sysback/.settings.tar
    3. Set the backend to backup. Enter:
           sbdefaults -B backup
    4. Make a backup copy of the settings. Enter:
           cp /usr/lpp/sysback/.settings /usr/lpp/sysback/.settings.bak

Sample scripts

NOTE: These scripts are samples only and are provided to assist users in creating their own custom scripts. They are not supported by IBM.

Script for option 1

 # Make mksysb backup to drive rmt0, then Volume Group backups to rmt1
 # Note: stacking mkvgback backups after mksysb backup is not advisable
 # mksysb backup of rootvg (mksysb can only backup rootvg)
 mksysb -i /dev/rmt0
 # mkvgback of secondary Volume Groups with TAR backend with
 #  progress indicator
 mkvgback -xf/dev/rmt1 appvg oravg

Script for option 2

 # Set to BACKUP
 cp /usr/lpp/sysback/.settings.bak /usr/lpp/sysback/.settings
 # Make Sysback backup of rootvg and appvg with the progress indicator
 sysback -xf/dev/rmt0 appvg
 # Set backend to TAR
 cp /usr/lpp/sysback/.settings.tar /usr/lpp/sysback/.settings
 # Make Volume Group Backup of Oracle Volume Group with the 
 #  progress indicator.
 #The 'n' flag tells the system to not rewind the tape drive
 #  'stacking' this backup onto the same tape as the sysback
 mkvgback -nxf/dev/rmt0 oravg

[ Doc Ref: 96231073320858     Publish Date: Jul. 18, 2000     4FAX Ref: 8597 ]