"Thanks for taking the time to respond.  I'm thinking that if I want to do
this, I'll probably abandon the TSM Scheduler in favor of home-grown
scripting.  But I may just wait to see if snapdiff gets supported on
vFilers, at which point this issue becomes moot for me."

Support for vFiler volumes with be in the TSM 6.40 client. Note that this
support will require ONTAP version 8.1.1 or greater.

Regards,

Pete Tanenhaus
Tivoli Storage Manager Client Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"



From:   Paul Zarnowski <psz1 AT CORNELL DOT EDU>
To:     ADSM-L AT vm.marist DOT edu,
Date:   08/08/2012 11:57 AM
Subject:        Re: snapshotroot for scheduled backups
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>



Thanks Allen.

At 10:05 AM 8/8/2012, Allen S. Rout wrote:
>You're in the position that the snapshot you want to use has a stable
>name.  There are folks who have snapshots named related to the date of
>consistency-point.

As it turns out, NetApp / nSeries snapshots do have predictable/static
names.

>If you're already preschedcmding, you might use that step to calculate
>the command lines to run the per-filespace "dsmc incr" lines, drop
>them in a temporary script, and then run that as a COMMAND schedule
>instead of an INCREMENTAL sched.

At that point, I'm not sure what the value would be of using the TSM
scheduler, as opposed to (e.g.) cron.

Thanks for taking the time to respond.  I'm thinking that if I want to do
this, I'll probably abandon the TSM Scheduler in favor of home-grown
scripting.  But I may just wait to see if snapdiff gets supported on
vFilers, at which point this issue becomes moot for me.

..Paul

--
Paul Zarnowski                            Ph: 607-255-4757
CIT Infrastructure / Storage Services     Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu