Hi,
The usage of _recent on creation would clash with the usage of SnapVault updates, since CDOT SnapVault does not rename Snapshots that have already been transferred, so the name becomes a duplicate to an existing one.
To implement _recent capability would require the choice between either SnapVault or Tape Backup, since both will not be possible (although SnapMirror 1:1 could be).
A workaround for the current missing functionality would be to script complementary pre- and postscripts for
any plugin that supports this, where the postscript saves the original date/time snapshot name
(on the plugin host in a hidden file), and renames the date/time Snapshot to _recent.
Note that SnapVault cannot be triggered, due to the name change - so the same limitation is present in this case.
The prescript would check the file, check for the _recent snapshot, and rename it back to the original name.
Note that this may be problematic on restores from primary, since the _recent will have to
be renamed before the restore when using that Snapshot (i.e. run the same pre-script).
So, you'd essentially be implementing the change through some scripting, but this only works for those plugins
that have pre- and postscripting support on the plugin Host.
And, if you are planning to SnapVault and use the destination for tape backup, why not access the live filesystem ?
It will always contain the last Snapshot (vault, not vault+mirror), except it's read-only.
If you need r/w access, you use destination cloning per scripting as well, but I think you cannot use postscripting,
since that isn't run after SnapVault, but before. Note that all file bits will be reset (i.e. archive bit usage won't use for deltas).
Hope this helps,
Olaf.