UpdateVV on snapshots of Remote Copy Volumes

[felonious_caper]

Ok there isn't much on the forums regarding updatevv in the manor in which I'm trying to use it so I figured I'd start with this.

1.) We have two 3par systems, one in location a and one in location b.
2.) Location A replicates volumes through remote copy to VV's in Location B.
3.) A read only and a read write snapshot of this replicated VV needs to be updated daily at location b
4.) During a sync. A temporary read only snap shot is created and becomes the read only child of the replicated VV, and makes the old Read only snapshot a child of the temporary one. After replication completes, the parent-child hierarchy are reordered.

Before Sync:
1. base replicated volume Parent: _ R/O child: 2 R/W child: _
2. read only snap Parent: 1 R/O child: _ R/W child: 3
3. read/write snap Parent: 2 R/O child: _ R/W child: _

During Sync:
1. base replicated volume Parent: _ R/O child: 4 R/W child: _
2. read only snap Parent: 4 R/O child: _ R/W child: 3
3. read/write snap Parent: 2 R/O child: _ R/W child: _
4. rcpy.temp r/o snap Parent: 1 R/O child: 2 R/W child: _


So now, if i run updatevv -ro read/write snap, it should update volume 3 and volume 2. The question is, if I run it while syncing, will volume 2 update from the base, or should it in fact update from the temporary snap since it is technically its parent for the time being? When I run updatevv the later is not the case (which i think it should be). It seems to still try and update the volume off of the base which has corrupt data because it is constantly changing from the sync. If i manually snap off of the temporary r/o snap shot, the data is not corrupt. Or if i wait for syncing to complete and updatevv the data is not corrupt.

After updatevv during a sync:
1. base replicated volume Parent: _ R/O child: 2 R/W child: _
4. rcpy.temp r/o snap Parent: 2 R/O child: _ R/W child: _
2. read only snap Parent: 1 R/O child: 4 R/W child: 3
3. read/write snap Parent: 2 R/O child: _ R/W child: _

The temporary volume now becomes a r/o child of the r/o snapshot



In short, is updatevv "smart" enough to know to use the temporary r/o snapshot while it is currently syncing?