I was going through the timefinder/Clone pdf and found this text under "Understanding copy session limits" of timefinder/Clone
For example, if you have a standard device with two paired BCV devices, you can
only create up to 14 copy sessions for that standard device. In addition,
if you are running in emulation mode, this number is decremented an additional two sessions per single BCV relationship.
With clone operations, two copy sessions are used if 'incremental resynchs' are desired.
This is to be able to maintain changed track count in between resynchs.
Since -as previously noted- Emulation mode uses clone behind the curtain, I hope you now have a better answer
I was going to answer this as soon as I got back to my desk, but fortunately I hit refresh before I started typing. What's the deal? Not enough work to keep you busy ???
Allen .. you should know (from another post) that I'm a form of artificial stupidity (since artificial intelligence is now widely available) ..
Can you please write an email to me ?? Unfortunatly I can't dig in the forums to find your email address, however I'd like to talk to you .. Can yoi please guess my email address ?
If you use "real" BCV (either mirrored or unprotected) you use "good old" Time Finder (AKA TF/Mirror). If you have RAID5 BCV you use so called "Emulation mode" .. You still issue symmir commands but Solution Enabler will silently translate commands in TF/Clone actions. That's why you have to account also for Emulated relations when counting TF/Clone sessions
Unfortunatly I don't know all the details behind "Emulation" mode .. I'll try to find an answer .. However maybe someone else may shade a better light on this topic
xe2sdc
6 Operator
•
2831 Posts
302
0
Posted August 5th, 2008 09:00
Since -as previously noted- Emulation mode uses clone behind the curtain, I hope you now have a better answer
Message was edited by:
Stefano Del Corno