-----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
************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************