I seems highly unlikely you would lose 4 disk at the same time. There
must be another problem....adapter...loose cabling. Are these SCSI or
SSA. I would try to determine why the disk are not available before
planning a TSM DB restore.
>>> PURDYM AT FIPD.GC DOT CA 08/14/03 03:39PM >>>
I don't know what they are not in the VG. The filesystems are not
mounted and the VG would not vary on because quorum is set. Of course I
could disable the quorum, but I don't think that will get me any further
to solving the real problem. I have thought about exporting and
importing it. Because, the error appears to be in the ODM. (an ODM get
on CuAt shows only four disks.) (I thought about sycnlvodm, but it must
be varyed on first.)
The varyon message is misleading too:
root@unxr:/usr/tivoli/tsm/server/bin>varyonvg TSMdbvg1024
PV Status: hdisk8 000d9f7fdabbdc5c PVINVG
hdisk9 000d9f7fdabbe670 PVINVG
hdisk10 000d9f7fdabbe852 PVINVG
hdisk11 000d9f7fdabbee59 PVINVG
0516-052 varyonvg: Volume group cannot be varied on without a
quorum. More physical volumes in the group must be active.
Run diagnostics on inactive PVs.
It should say that the other four are missing.
Are my steps to reload the TSM database complete?
Miles
>>> KauffmanT AT NIBCO DOT COM 14-Aug-03 2:34:09 PM >>>
Miles --
Why are the disks not in the VG? Anything in diagnostics or errpt?
My first shot would be to unmount any mounted filesystems in the VG and
vary
the VG offline. Then exportvg TSMdbvg1024. Then, take a shot at
importvg -y
TSMdbvg1024 hdisk8 and see if it all comes back. If not, it's probably
delete/define/reload time.
Tom Kauffman
NIBCO, Inc
-----Original Message-----
From: Miles Purdy [mailto:PURDYM AT FIPD.GC DOT CA]
Sent: Thursday, August 14, 2003 2:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: HELP! My lost TSM DB
Hi folks,
TSM server 5.1 on AIX 5.1
(This may a little more of an AIX question, but I've lost my TSM
database...)
I rebooted my Unix server today and four disks that belong to a volume
for
my TSM database, were not in the volume group any more! I know that I
can't
add them back in to the VG because the disks will be wiped. Ex:
The last four disks used to be in the volume group:
hdisk8 000d9f7fdabbdc5c TSMdbvg1024
hdisk9 000d9f7fdabbe670 TSMdbvg1024
hdisk10 000d9f7fdabbe852 TSMdbvg1024
hdisk11 000d9f7fdabbee59 TSMdbvg1024
hdisk13 000d9f7fe2b49302 None
hdisk14 000d9f7fe2b50726 None
hdisk15 000d9f7fe2c74aee None
hdisk16 000d9f7fe2c76f92 None
I'm hoping to get the disks back into the VG by hacking the ODM.
Unless
someone knows another way?
My plan B is just to restore the database. Does this plan make sense:
Delete the LVs first?
rmlv TSMdbB
rmlv TSMdbC
rmlv TSMlogB
rmlv TSMlogC
Delete the VG?
exportvg TSMdbvg1024
Add the VG and add the disks to the VG:
Use smit.
Create the LVs:
/usr/sbin/mklv *S 4k -y 'TSMdbB' TSMdbvg1024 8 hdisk8 hdisk9
/usr/sbin/mklv *S 4k -y 'TSMdbC' TSMdbvg1024 8 hdisk8 hdisk9
/usr/sbin/mklv *S 4k -y 'TSMlogB' TSMdbvg1024 2 hdisk10 hdisk11
/usr/sbin/mklv *S 4k -y 'TSMlogC' TSMdbvg1024 2 hdisk10 hdisk11
Format LVs for TSM:
dsmserv format 2 /dev/TSMlogB /dev/TSMlogC 2 /dev/TSMdbB /dev/TSMdbC
dsmserv restore db
Any help is greatly appreciated!
Thanx Miles
----------------------------------------------------------------------------
------------------
Miles Purdy
System Manager
Information Systems Team (IST),
Farm Income Programs Directorate (FIPD),
Agriculture and Agri-Food Canada (AAFC)
Winnipeg, MB, CA
Office contact: Mobile
contact:
purdym AT fipd.gc DOT ca
purdym AT rogers.blackberry DOT net
ph: (204) 984-1602 fax: (204) 983-7557 Cell: (204) 291-8758
"If you hold a UNIX shell up to your ear, can you hear the C?"
----------------------------------------------------------------------------
---------------------
CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the
exclusive and confidential use of the intended recipient. If you are
not the intended recipient, please do not read, distribute or take
action in reliance upon this message. If you have received this in
error, please notify us immediately by return e-mail and promptly delete
this message and its attachments from your computer system. We do not
waive attorney-client or work product privilege by the transmission of
this message.
|
