topic Re: IGNITE Backup problems in Operating System - HP-UX

IGNITE Backup problems

Jim Morakeas — Fri, 14 May 2004 17:32:54 GMT

Good morning all, I am attempting to create an IGNITE backup and I am getting the following errors.

The command invoked is the following;

/opt/ignite/bin/make_tape_recovery -AvI -a /dev/rmt/0m -x inc_entire=vg00

The errors can be seen in the attached log

I would appreciate some guidance.

Re: IGNITE Backup problems

Mel Burslan — Fri, 14 May 2004 17:39:06 GMT

seems like you have a bad disk in your vg00 which is not a good thing when and if time comes to restore from this image as the data from this bad disk drive is going to be missing.
if you are not using this drive anymore, you need to reduce vg00 and drop out the /dev/dsk/c0t5d0 from vg00 or get it fixed before proceeding with make_recovery command

Re: IGNITE Backup problems

Sundar_7 — Fri, 14 May 2004 17:43:21 GMT

looks like you have a broken disk in your system ?

do an ioscan and find out the status of the disk /dev/dsk/c0t5d0 if the status CLAIMED and DEVICE then try this

# dd if=/dev/rdsk/c0t5d0 of=/dev/null bs-1024k

"save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk"

The above error messages dont sound like a good news.

Re: IGNITE Backup problems

Bill Hassell — Fri, 14 May 2004 20:39:13 GMT

Ignite will never take a backup if your vg00 disks are not clean. This means that reports from vgdisplay and lvlnboot do not havge errors. There is no way around this nor do you want to ignore the problems. You likely have a failed disk and the mirror seems to be working OK. Replacing the bad disk can be quite tricky depending on the exact failure. Be sure to read the docs about replacing a vg00 disk. Mirroring works well (as you're seeing) but swapping a bad disk can end up with a ghost disk and other difficulties.

Re: IGNITE Backup problems

Navid Hussain_1 — Sun, 16 May 2004 00:41:13 GMT

Hi,

Can you send /etc/lvmtab output. Just cross check that disk /dev/dsk/c0t5d0 belongs to vg00 group.
Execute following command to verify physical disk present or not
# dd if=/dev/rdsk/c0t5d0 of=/dev/null bs=2k
you should get some record in and out
#diskinfo -v /dev/rdsk/c0t5d0 and check ioscan -fnC disk output for CLAIMED.

You may copy /etc/lvmtab to /etc/lvmtab.old and execute #vgscan -a to create new lvmtab files and then veify disk at c0t5d0.

Once you are sure that disk is being recognized and accessible , Then start taking taking ignite.

Meanwhile, I have notice, you are excluding entire vg00 .. WHY??

Cheers ..

NAVID

Re: IGNITE Backup problems

Jim Morakeas — Sun, 16 May 2004 19:33:41 GMT

Thanks Navid, I was of the understanding that "inc_entire=vg00" was actually including not excluding
/opt/ignite/bin/make_tape_recovery -AvI -a /dev/rmt/0m -x inc_entire=vg00.

Re: IGNITE Backup problems

Patrick Wallek — Sun, 16 May 2004 20:12:25 GMT

Jim, you are correct. You are including the entire VG00. Actually you are being redundent in your command. You specify both '-A' and '-x inc_entire=vg00'. I would omit the -A and just use the command line:

# /opt/ignite/bin/make_tape_recovery -vI -a /dev/rmt/0m -x inc_entire=vg00

Re: IGNITE Backup problems

Dani Seely — Sun, 16 May 2004 21:34:16 GMT

Have you tried an fsck of vg00? fsck is used to check and repair (if repair option is used) one or more file systems. Give this a try, then use the suggested IGNITE command Patrick lists.

Re: IGNITE Backup problems

Jim Morakeas — Mon, 17 May 2004 17:56:15 GMT

I attempted to run an IGNITE backup on another host and received the following error

ERROR: This is not a no rewind device file.
ERROR: Check tape device failed.
* Creating local directories for configuration files and archive.

The command I used was the following;
/opt/ignite/bin/make_tape_recovery -vI -a /dev/rmt/1m -x inc_entire=vg00

Re: IGNITE Backup problems

Patrick Wallek — Mon, 17 May 2004 18:10:04 GMT

You must specify a no-rewind tape device. In your command you used /dev/rmt/1m You should ALWAYS use the mn device file, so in your command it should be '-a /dev/rmt/1mn'.