Hi Dave,

We use the EMC Timefinder/SNAP and EMC/SRDF.  I believe we have experienced
the 'issue' you have
described based on a couple of assumptions.  I am assuming that when you
say: "SRDF comes along
to replicate to our DR site", you are indicating that you issue a EMC/SRDF
"Createpair" command and
that SRDF command fails because the SRDF Source volume ( the R1 volume )
which is the Timefinder/SNAP
Target volume, is in Timefinder HELD status.  Also, I am assuming that to
remove the Timefinder HELD status,
you have to issue the Timerfinder/SNAP CONFIG command with RELEASE(YES)
specified.  If my assumptions
above are accurate, then yes, we have experienced this situation.

We have had dialogs with EMC regarding this issue because the RELEASE
requirement was not documented
in the SRDF nor Timefinder/SNAP manuals ( i.e. in the SRDF manual,
Createpair command, there should be
a usage note that indicates if you are using Timefinder/SNAP, you may need
to issue CONFIG RELEASE
prior to issuing the Createpair command ) .  Also, we asked EMC what
benefit do we receive from the HELD status
if we are allowed to reset it at any time.  Lastly we asked, if the HELD
status is to prevent data overlay, what
data integrity exposure might be created when we reset it.

Our solution to the problem was to issue the Timefinder/SNAP CONFIG RELEASE
command via our D/R replication
software we wrote in-house to support the SRDF & Timefinder/MIRROR ( the
BCV's on the D/R DASD unit ).


Hope this helps.


Glenn Miller

---------------------------------------------------------------------------
This message (including any attachments) is confidential and may be
privileged. If you have received it by mistake please notify the sender by
return e-mail and delete this message from your system. Any unauthorised
use or dissemination of this message in whole or in part is strictly
prohibited. Please note that e-mails are susceptible to change. ABN AMRO
Bank N.V, which has its seat at Amsterdam, the Netherlands, and is
registered in the Commercial Register under number 33002587, including its
group companies, shall not be liable for the improper or incomplete
transmission of the information contained in this communication nor for any
delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its
group companies) does not guarantee that the integrity of this
communication has been maintained nor that this communication is free of
viruses, interceptions or interference.
---------------------------------------------------------------------------

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to