Re: Bad Shadow set member


Tom Linden wrote:
On Wed, 13 Dec 2006 12:12:26 -0800, AEF <spamsink2001@xxxxxxxxx> wrote:


Tom Linden wrote:
On Wed, 13 Dec 2006 11:12:28 -0800, AEF <spamsink2001@xxxxxxxxx> wrote:

Tom Linden wrote:
On Wed, 13 Dec 2006 05:14:43 -0800, AEF <spamsink2001@xxxxxxxxx>
wrote:


JF Mezei wrote:
Tom Linden wrote:
Thanks. BTW, I am having a new drive overnighted to me.
Anything
in
particular I need to pay attention to when adding it? I
presume I
need
to INIT first?


If not inited, it reduces the chances that the shadowing software
might
decide to use that drive as a source.

Also, when you first include the physical drive into the
shadowset,
eitther
mount it into an existing shadowset, or ensure it is not the first
device
listed in the /SHADOW=(drive1,drive2,drive3,etc)

If he just adds the disk with the system running and uses /CONFIRM,
that should be enough.

But I still need to INIT the drive.

Why? Why do you need to init the drive? It's going to be the target of
a full copy operation so whatever is there will be clobbered, INITed
or
not.

Yes I saw that in the documentation, but what if this drive came off a
non-VMS system?

Hmmm. I think that might confuse /CONFIRM because it would be trying to
read the label, but I think it should still work. A quick INIT wouldn't
hurt, but I'd skip the ERASE because it will be the targete of a full
copy operation anyway, no?



DSA0: Mounted 0 COMMON
84555222
40 5
$42$DKA1300: (HAFNER) ShadowSetMember 0 (member of DSA0:)

$42$DKA1200: (HAFNER) Online 1
$42$DKA1300: (HAFNER) ShadowSetMember 0 (member of DSA0:)

so how does this look
$ INIT/SHADOW=($42$DKA1200:) common

The manual says there is no advantage to INIT/SHADOW when adding a
drive to an already existing shadow set.

I quote from
http://h71000.www7.hp.com/doc/732FINAL/aa-pvxmj-te/aa-pvxmj-te.HTML

Note that the INITIALIZE/SHADOW command should not be used to
initialize a disk to be added to an existing shadow set, since there
is
no benefit to be gained.

$ mount/confirm DSA0:/shadow=($42$DKA1200:) common

Just use the command above and you'll be fine. For startup I think you
want to specify both disks without /INCLUDE and without /NOCOPY, but
with /NOASSIST.

ODIN> mount/confirm DSA0:/shadow=($42$DKA1200:) common
%MOUNT-F-INCOMPAT, qualifiers incompatible with already mounted volume

Maybe it just needed /CLUSTER and/or /SYSTEM; i.e., this would be the
command you'd use to mount a volume privately, so you got the
incompatible error.

The surviving member was mounted manually as (just copied out of startup)
MOUNT DSA0:/CLUSTER/NOASSIST/INCLUDE/NOCOPY/SHADOW=($42$DKA1300:) COMMON


So it looks like I need first to dismount it, then mount it again, why not
do both?

I don't think you need to dismount anything unless you've mounted the
new drive separately for some reason.


MOUNT DSA0:/CLUSTER/NOASSIST/SHADOW=($42$DKA1300:,$42$DKA1200:) COMMON
mindful of JF comment about list the good member first

Try this with /CONFIRM tacked on. It should work with or without the
already mounted member in the command:

$ MOUNT DSA0:/CLUSTER/NOASSIST/SHADOW=($42$DKA1200:) COMMON /CONFIRM

[...]

AEF

.

Relevant Pages

  • Issues with Shadow Copy
    ... was happening I have tried to use the command prompt command ... Volume Shadow Copy Service administrative tool ... if I go to the System Properties box and the System Protection ...
    (microsoft.public.windows.vista.performance_maintenance)
  • Re: My buttons look different since Ive upgraded to 8.4.4 (from 8.0)
    ... > command provided for backward compatability. ... Before Tk 8.3 a bright shadow is always brighter ... chance for a Tcl command to do the switch. ...
    (comp.lang.tcl)
  • Re: Shadow Copy Transport Between Servers
    ... We have been looking for a while for a command line ... interface to the Disk Mirror capability in Windows 2003 that would ... Create a persistent transportable shadow copy of the ... Assign drive letters to the new shadow copy disks. ...
    (microsoft.public.windows.file_system)
  • Re: Bad Shadow set member
    ... But I still need to INIT the drive. ... drive to an already existing shadow set. ... Just use the command above and you'll be fine. ... The drives are identical, so maybe I do need to INIT afterall? ...
    (comp.os.vms)
  • Re: physical drive replacement
    ... >> My first problem is determining which of the 2 physical drives in stripeset ... DELETE the disk, quiesce the bus and perform the physical swap, ... > and mount it into the shadow set, which should trigger a shadow copy ...
    (comp.os.vms)