A given file cannot be bound to more than one management class at a time.
If you run a backup and bind the files to a MONTHLY mgmt class, those rules
take effect immediately for that file. Then if you bind the file to a
different management class, those rules take effect immediately. The only
way to bind a file to different management classes is to use two different
nodenames, as Mark suggested.
But, also look at the GENERATE BACKUPSET command on the server.
If the client does daily incrementals, you can use GENERATE BACKUPSET to
create a the once-a-week and once-a-month backup from the data already on
the server, without sending it across the network again.
If you expect to use the weekly/montly backups very seldom for restores, or
if the objective is to send those backups offsite for Disaster Recovery
purposes, then the GENERATE BACKUPSET may be appropriate.
If the client expects to need access to these backups often, then using a
second nodename may be the most appropriate so they can use the GUI
interface they are used to for restores.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
> -----Original Message-----
> From: Remeta, Mark [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, October 09, 2000 10:12 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Scheduling and Management Class
>
> You could create multiple node definitions for the client and install
> multiple schedule services, one for each node you create...
>
>
>
> -----Original Message-----
> From: HK Chng [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 09, 2000 10:08 AM
> To: [EMAIL PROTECTED]
> Subject: Scheduling and Management Class
>
>
> Hello all,
> I have the following request from a user and hoped that someone
> out
> there has gotton passed the limitation of scheduling through TSM
> scheduler( I am running TSM 3.7.3 on AIX 4.3.3 ): the user requested to
> have a incremental backups of their data carried out daily with version
> control set for 14 for both active and inactive files. they would like a
> monthly backup taken on the first Sunday of the month for 6 versions and
> weekly backup thereafter for the rest of the month for 4 versions. I
> have defined new management classes to hold the data rules on retention
> and version control and in teh clients includ-exclude list, I have
> grouped the files under their respective mgmt classes. However, ADSM
> seems to have a primitive scheduler with limited calendar features found
> in common scheduling tools such as Ctrl-M. I intended to use scripts to
> trigger the backup jobs but how can I link the various management
> classes to the respective backup schedules e.g. MONTHLY_BKUP_SCHED to
> bind to MONTHLY_BKUP_MGMTCLASS etc so that the appropriate mgmt rules
> are used for the various backups? Any comments is much appreciated !
>
>
> Regards.
> Hak Kiat, Chng
> Storage Admin
>
> Confidentiality Note: The information transmitted is intended only for the
> person or entity to whom or which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of this information by persons or entities
> other
> than the intended recipient is prohibited. If you receive this in error,
> please delete this material immediately.
