Re: [ADSM-L] Nodes with different drive list under One Scheduler.

2011-07-11 08:07:03
Subject: Re: [ADSM-L] Nodes with different drive list under One Scheduler.
From: Bill Boyer <bjdboyer AT COMCAST DOT NET>
Date: Mon, 11 Jul 2011 07:57:03 -0400
If you have need to do a FULL backup occasionally, then you could:

1. Put those 10 nodes in a separate domain
2. In that domain you have 2 policy sets: 1 that is your normal daily
incremental backup, and the 2nd one is a copy of the first but changing the
MODE=ABSOLUTE in all the backup copygroups.
3. Use your DOMain client option on each node to specify the drives you want
if they are different than ALL-LOCAL
4. Set up a schedule that activates your FULL MODE=ABSOLUTE policy set when
you want the FULL backups to run. And another to re-activate the standard
MODE=MODIFIED incremental policy set.

Just don't forget that if you're doing retention by versions, that this full
is going to be another version whether the file has changed or not. You
could end up with a lot of your backup files having the active and the most
recent inactive version being the same copy of the file.

Bill Boyer

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lakshminarayanan, Rajesh
Sent: Monday, July 11, 2011 6:41 AM
Subject: [ADSM-L] Nodes with different drive list under One Scheduler.

Hi Guys,

    I have a scenario where I need to schedule a full backup for 10 client
nodes(windows server) under one schedule in the TSM server.  All the client
nodes have different drive list in it.  If I group them under once scheduler
with  drive list specified in the object parameter of the scheduler, I get
backup failure messages from the client nodes as all the drives specified in
the scheduler is not available in the client
node.    I don;t want to schedule 10 separate schedulers for each client
node in the TSM server.    I have constrains to run the backup on the
same day and time.

   Can you some one help me with a work around with this..

Scenario's example:

Client Node 1 has C: D :  drives
Client Node 2 has C: D : F: drives
Client Node 3 has C: D : E: drives
Client Node 4 has C: D : S: drives
Client node 10 has C: F:S: drives....

Scheduler details

 Policy Domain Name: Domain
                 Schedule Name: GRP1_FULL
                   Description: Schedule To Backup windows Servers
                        Action: Selective
                       Options: -subdir=yes -domain="All-local"
                       Objects: c: d: e: f: g:h:J;