-----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
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
To report this email as spam click https://www.mailcontrol.com/sr/2uyPRc+RlX3TndxI!oX7UkjnxLIPhzY69il!kXCBqWv!L... .
Nick
I've done this kind of thing, but using NetBackup rather than TSM via a script (this was on an AIX server). The steps I used were:
-Create a profile in SMO which would only be used to take snapshot backups that would be dumped to tape (called say BACKUP) and only keep the minimum number. -In the script, have the previous nights BACKUP snapshot deleted and then have another snap taken using this profile. -Once the snap is taken, use SSH to get a list of snapshots on the Oracle volumes, and look for the snapshot name which contains the name of my profile BACKUP (SMO snaps at least have the name of the profile used in them) -Once the snapname has been gathered, then manipulated the backup policies in NetBackup to add the volume names with the snap names above -Kicked off a manual backup of the policy
Assuming you can manipulate the backup specification in TSM from the command line, I'm sure you could apply this method to TSM as well.
HTH
Chris
-------------------------------------------------------------------------- Christopher Holloway Lead Consultant Professional Services Main: +44 1423 519000 Direct: +44 1423 519099 Mobile: +44 7867 783584 Fax: +44 1423 504415 Come to our next Virtualisation event on Servers, Desktops, Apps and Beyond…hear from our key directors and vendors at Hellidon Lakes on 25th November 2008. To register your attendance, visit http://www.dnsarrow.co.uk/virtualregister or for more information please visit http://www.dnsarrow.co.uk/virtualisation
Our Terms and Conditions have changed. To view our new Terms and Conditions and for more information about the changes, please visit http://www.dnsarrow.co.uk/Ts&Cs
DNS Arrow Nidderdale House Beckwith Knowle Harrogate HG3 1SA http://www.dnsarrow.co.uk/ Email Confidentiality Notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. "DNS Arrow" means Digital Network Services (UK) Limited, a company registered in England. Company Registration Number 3952678. Registered Office: Nidderdale House, Otley Road, Beckwith Knowle, Harrogate HG3 1SA, UK. -----Original Message-----
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nick Silkey Sent: 17 November 2008 17:39 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
-
Darren Sykes -
Holloway, Chris -
Nick Silkey