vgsync problem

[Javier Ortiz Guajardo]

I install the Disk Mirror in HPUX-11.0 64 bits
then i am doing a Ignite tape but in the part of Backing up vg configurations is taking too much time in vg03, with command ps -ef|grep vg
show me this

root 79 78 0 09:10:18 ? 0:15 /sbin/vgsync /dev/vg01

root 24146 23195 0 11:17:40 pts/tc 0:00 sh -c /usr/sbin/vgcfgbackup "vg01" >> /var/opt/ignite/l

root 24147 24146 0 11:17:40 pts/tc 0:00 /usr/sbin/vgcfgbackup vg01

The vg01 have 255 lvols but anyone have mirrored lvols.

What i need to do to correct this problem?

Thanks

[RAC_1]

255 lvols in vg01. Ignite is not really a tool to backup vg01/non-root vgs. It is meant for vg00 recovery.

What if you do vgsync vg01?? How long it takes?? Is it mirrored??

Anil

[Javier Ortiz Guajardo]

the lvols in vg01 are not mirrored i don´t know why the vgsync is taking too much time.

Than

[Sundar_7]

Even if it is executing vgsync of vg01, it should not take long time to complete if the VG is already in synchronized state.

But I must tell you, you dont seem to have the optimal logical volume configuration. 255 LV in a single VG doesnt seem like a very good idea to me.

Try syncing and backing up vg01 from the command.

Are you using -A option with make_(tape_)recovery command? - is your /usr in VG01 ?

[Javier Ortiz Guajardo]

Yes i am using the command
make_recovery -A -v -d /dev/rmt/0m

[Dietmar Konermann]

Hmm...

maybe the vgsync hangs while holding some resource or lock which prevents vgcfgbackup from completing? Or maybe vgsync is hanging for the same reason as vgcfgbackup, which is typically caused by some kind of inaccessible disks (hardware trouble?).

Anything in syslog.log or dmesg?

Best regards...
Dietmar.