On Mon, Oct 20, 2008 at 10:41 PM, Bassett, Oliver oliver.bassett@nz.fujitsu.com wrote:
Nathan,
Easiest solution at this point is to delete the really large/old snapshot in the volume on FilerA. This will replicate the snapshot to filer b and filer c, without damaging the existing snapmirror relationships (as long as everything is up to date with low lag times).
Ah, that's a problem I'd forgotten to mention and why I'm hesitant to just go and release things. On FilerA, although the master, the snapshot is still locked by snapmirror:
5% ( 4%) 4% ( 3%) Aug 20 08:05 filerA(0101195225)_perforce.7 (snapmirror)
To my surprise the snapshot is in the *same* state on filerB and filerC, so unfortunately as things stand right now, I can't just go and delete the snapshot.