ADSM-L

Recovery of mirrored db and log volumes

2005-06-20 05:47:05
Subject: Recovery of mirrored db and log volumes
From: Farren Minns <fminns AT WILEY.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 20 Jun 2005 10:46:35 +0100
Hi TSMers

Running TSM 5.1.6.2 on Solaris.

Two of the internal disks in our sun E250 server are used to house the
database and log volumes and copies (using TSM's internal mirroring). This
morning one of the disks failed and we are now awaiting a replacement. I
have had a look at the documentation for recovering mirrored volumes and
all I have found is this.

1) Query the database and log volumes
2) Place failed volumes off-line (TSM already did this for me)
3) Fix device
4) Allocate space for new copies with DSMFMT
5) Bring new volumes on-line.

Now, at the moment, the off-line copies are still defined within TSM, so
what I want to know is this. Once I have got the new disk in place and
created the necessary file systems, can I just recreate the required log
and DB volumes using the dsmfmt command and give them the exact same
location,name and size? I am assuming that if this is the case I can then
just vary the off-line copy back on-line? Is this correct or am I missing
something?

Many thanks in advance

Farren Minns
Solaris System Admin / Oracle DBA
IT - Hosting Services

John Wiley & Sons, Ltd


######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s).  If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it.  If you
have received the e-mail in error, please notify the sender and delete
the e-mail.

Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated.  Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################

<Prev in Thread] Current Thread [Next in Thread>