ITEM: BH3406L
I can't restore my raw lv appended on a fullsystem backup
Question:
Env:
AIX 3.2.5
sysback 3.3.2.10
Desc:
I am getting not a error message:
Unable to read the volume header on device /dev/rmt0.1.
The command I used is lvrestore -i8 -lf /dev/rmt0
Action:
The customer is using the fsback.post script to append
raw logical volume backups to the full system backup tape.
Since the first 4 images are created with non sbwrite
commands you will have to first fast forward on the tape to
position yourself.
MAP of a fullsystem backup.
1 2 3 4 5 6 7 8
-----------------------------------------------------------------------------
| | | | | | | | |
| Bosboot | Mkinsttape | Dummy TOC | sysback | rootvg | vg1 | vg2 | raw |
| Image | Image | Image | Image | data | data | data | lv |
| | | | | | | | |
|-----------------------------------------------------------------------------
| | |
|\<-------------- Block Size 512 ------------>| Block size determined by the |
| | file on the sysback Image (4) |
| | ./tmp/...blksz |
| | |
The full system backup contains 4 boot images at block size
512. Each volume group is its own file image on the tape block
size of whatever the tape was set at pior to running the
sysback command. Rootvg is always included and is always the
5th image on the full system backup tape.
To restore your raw logical volume (image 8) run these commands.
If you don't know the block size your backup was made at do
steps 1-4. If you know the block size of your backup skip to
step 5
1. chdev -l rmt\# -a block_size=512
2. tctl -f /dev/rmt\# rewind
3. restore -s4 -xvqf /dev/rmt\#.1 ./tmp/...blksz
4. cat ./tmp/...blksz
If the value in step 4 is not 512 run this command
chdev -l rmt\# -a block_size=\
5. tctl -f /dev/rmt\# rewind
6. tctl -f /dev/rmt\#.1 fsf 7
(skipping to the beginning of the 8th image)
7. lvrestore -nlf /dev/rmt\# lvname
Next Action:
Closing with customer approval
Support Line: I can't restore my raw lv appended on a fullsystem backup ITEM: BH3406L
Dated: April 1996 Category: N/A
This HTML file was generated 99/06/24~13:30:21
Comments or suggestions?
Contact us