Have you considered scripting something to work around this?
 
We're using SMO in a dev environment but we're anticipating having the same issue. We were considering flexcloning the most recent snapshot/backup so we had a consistent volume name.
 
 
From: owner-toasters@mathworks.com on behalf of Nick Silkey
Sent: Mon 11/17/2008 17:38
To: toasters@mathworks.com
Subject: pointing a tsm ndmp mover at smo-fired snapshots

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(NB: Resent from $oldjob.  Newly-subscribed identity is having issues
posting.)

Toasters --

We are currently looking for a means to point a TSM NDMP mover at
SMO-initiated snapshots.  The TSM maintainers are currently defining
'virtual filesystem mappings' to point the TSM NDMP mover at WAFL snaps
on non-Oracle volumes.  This works like a champ due to consistent naming
with scheduled WAFL snaps (nightly.0, etc).  Since introducing SMO, we
now have quiesced, consistent Oracle data in snapshots.  Unfortunately
the naming of these SMO snaps is nowhere near as graceful as
'nightly.0', to the chagrin of TSM.

Has anyone here dealt with reconciling SMO snap name spew along with
pointing a TSM NDMP mover at a consistently-named SMO snap space?

Insight appreciated.  Thanks.

- --
Nick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkhrCkACgkQrDQjhjXrMeJ5ewCgp6+BqV9MNOC4iqCkNNKJFACJ
tWYAnivf2p3j5pgup9SryVQaWhkQWTDt
=3twI
-----END PGP SIGNATURE-----


 To report this email as spam click https://www.mailcontrol.com/sr/2uyPRc+RlX3TndxI!oX7UkjnxLIPhzY69il!kXCBqWv!LSfGYAkSTwZDAbbmh9L9xCDb+qF6xF45ky06sDJQ0Q== .