| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 775.1 | | SSDEVO::T_GONZALES | | Sun Feb 23 1997 16:59 | 11 |
| remember if you do not dismount the mirror set/unit, you can't
guarantee that the reduced member will have the latest data from the
operating system. Reducing a member through the hsz command does not
cause of flush any cache data that me be present in the host's cache
buffers.
As far as resyncing, i don't know what you mean, If you mean
when you add the member back into the mirror set, then it can take
anywhere from 20 minutes to an hour depending upon the size of the
mirror set for the new member to get completely updated.
|
| 775.2 | SET NOWRITEBACK before REDUCE works | SSDEVO::JACKSON | Jim Jackson, HSx RAID team | Mon Feb 24 1997 09:21 | 5 |
| Re: .1
Just set the mirrorset NOWRITEBACK before doing the REDUCE, and it will be
synchronized. The SET NOWRITEBACK flushes dirty data before returning the
CLI prompt.
|
| 775.3 | Please help | JULIET::SMITH_P | | Tue Feb 25 1997 13:29 | 11 |
| I do apreciate all the help but I still do not have my question
answered.
What is the exact procedure, that works, to break a controller based
mirror, back it up, put mirror back together. I also need to know the
reconstruction time approx.
I understand the cache issues but an HSZ50 product has some LUN issues
I cannot understand how to make it work.
Paul
|
| 775.4 | HSZ50 Config Guide has a section on this | KERNEL::LOANE | Comfortably numb!! | Tue Feb 25 1997 23:11 | 6 |
| Paul,
There was a good description of a process to do JUST what you
require in the rear of the HSZ50 Config Guide (in one of the
appendices I seem to recall)....obviously this doesn't get round
the issue of flushing Host caches (application heaps etc), but it
ensures that spindle data is sync'd.
|
| 775.5 | How about this procedure | GUIDUK::SOMER | Turgan Somer - SEO06 - DTN 548-6439 | Tue May 06 1997 18:21 | 44 |
| Can someone comment on this procedure?
If your mirror set named M1, and it comprises DISK200 and DISK300:
hszterm> SET M1 NOPOLICY
#!
#! NOPOLICY retires a device from the mirror set without
#! selecting a replacement. This enables the mirrorset to run with less
#! than the nominal number of members until a member is manually
#! replaced in the mirrorset
#!
hszterm> SET M1 REMOVE=DISK200
#!
#! (This will break up the the mirror set M1 on the HSZ)
#!
hszterm> ADD UNIT D400 DISK200
#!
#! This creates an unused /dev/rzXnnY unit for use by the Unix O/S from the
#! removed half of the mirror set M1
#!
#!
#! rz + LUN letter + ((8 * SCSI Bus #) + Controller's Target ID)
#!
#! or
#!
#! rz + a + ((8 * 2) + 4)
#!
csh> /mount /dev/rza20c /backup_mount_point
csh> /backup
csh> /umount /dev/rza20c
hszterm> DELETE D400
#!
#! This deletes the HSZ unit just created for backup purposes
#!
hszterm> SET M1 REPLACE=DISK200
#!
#! This puts the removed disk back in the mirrorset
#!
hszterm> SET M1 POLICY=BEST_PERFORMANCE
#!
#! Let the mirror set synchronize
#!
|