We have been using "volume move" to shuffle volumes around our cluster, being told that it is a great tool, and will cut-over cleanly.
Well, I've found out that it isn't so clean. When "volume move start" is executed, it appears to create a snapshot for the copy. It then proceeds copying data from that snapshot, and including snapshots which existed prior to the "volume move start" snapshot. Once it is ready to trigger the cutover, it updates, I believe, from the origination snapshot, cuts-over the volume, but does not update files created or modified after the origination snapshot.
This has been wreaking havoc with our moves, with users telling us their data has reverted to a prior time; I now believe the users are correct.
-Unfortunately, I could not find any documentation or TR's which address the issue. So I must assume it is an issue with the volume move command.
-One caveat, is we did not have snapmirror licensed on the entire cluster. Perhaps that would cause "volume move" not to be able to update, however, there should have been a note in the documentation.
If anyone at NetApp can address this, that would be great. I'd like to know if "volume move" can be used in future, or if I need to go back to good old Volume SnapMirror.