Greetings again,
We use EMC's SNAP copy on a couple very large datasets. This offloads
the
copy to the array, frees up the initiator and lets our JOB stream move
on once
the SNAP command is issued to the array. The difference being a couple
seconds
vs. a couple hours. The physical copy is not complete in a couple
seconds, but
the software on the array hides that fact.
Since we started using it, we've had issues with our SRDF process.
There are
always several dozen volumes in HELD status when SRDF comes along to
replicate
to our DR site. It turns out SNAP copies of datasets require a manual
RELEASE
command be issued for each of the target volumes. A SNAP copy of an
entire volume
automatically releases the target volume once the SNAP completes. I
don't know
why there is a difference, but there is.
Has anyone else used this feature ??? Do you experience the same
issues ???
Have you come up with a way around it ???
Thanks,
Dave K.
------------------------------------------------------------------------------
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
whom it is addressed. Any use, copying, retention or disclosure by any person
other than the intended recipient or the intended recipient's designees is
strictly prohibited. If you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and delete all copies.
OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or
disclose the content of all email communications.
==============================================================================
----------------------------------------------------------------------
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
