>Tue, 15 Aug 2006 11:04:11 -0500, Dave Mussulman <mussulma (AT) uiuc (DOT) edusaid:
Any opinion on archives vs. backupsets for a monthly snapshot kept for 6
months?
Yes; E) None of the above.
If you want a monthly snapshot, define a new devclass, with different
retention parameters; perhaps:
verexists: 8
verdeleted: 8
retextra: 300
retonly: 300
This is slightly paranoid, with a little extra in each category.
Then define a FMNTHLY node as an echo of each node F in your
normal management class. Run the incrs for the -MNTHLY nodes,
monthly. ;)
You'll accumulate 8 versions with these settings, and since you're
only cutting new versions (at a maximum) monthly, you'll have 8
months.
I used 8 instead of 6 Just In Case someone runs an incr out of school,
so you don't the oldest version off the end of the queue.
For a more detailed level of "snapshot", you could set FREQUENCY=30,
and run incrementals against the -MNTHLY nodes every day.
This way you still keep 95% of the advantages of incremental-forever
processing, and still leverage the TSM database.
Resort to backupsets if your needs include restore operations
independant of a running TSM server, or independant of good network.
- Allen S. Rout

All,

I want to set up TSM configuration manager. I have several AIX 5.1
TSM servers 5.3.2.

I have defined a profile on one server, and defined a profile
association to this configuration profile for domains, using our
"STANDARD" domain as a test to propagate additions and changes to
subscribers. Configuration manager is set "" to this server:

tsm: DSMSERV1>q profile f=d

Configuration manager: DSMSERV1
Profile name: TSM SERVER PRFILE
Locked?: No
Description: TSM Master
Server administrators:
Policy domains: STANDARD
Administrative command schedules:
Server Command Scripts:
Client Sets:
Servers:
Server Groups:

a second server I have defined subscription to the master:

tsm: DSMSERV2>q subscription f=d

Configuration Profile name Last update
manager date/time
DSMSERV1 TSM SERVER 08/16/06 11:59:40
PRFILE

This server has "Allow Replace" yes.

configuration manager I run:

notify subscribers

and it fails at the subscriber end:

08/17/06 08:21:53 ANR0408I Session 75279 started for server DSMSERV1
(AIX-RS/6000) (Tcp/Ip) for configuration
management.
(SESSIN:
75279)
08/17/06 08:21:54 ANR0409I Session 75279 ended for server DSMSERV1
(AIX-RS/6000). (SESSIN:
75279)
08/17/06 08:21:54 ANR0408I Session 75280 started for server DSMSERV1
(AIX-RS/6000) (Tcp/Ip) for configuration
management.
(SESSIN:
73099)
08/17/06 08:21:54 ANR3152I Configuration refresh started with configuration
manager DSMSERV1. (SESSIN:
73099)
08/17/06 08:21:54 ANR3350W Locally defined domain STANDARD contains at least
one node and cannot be replaced with a
definition from
the configuration manager. (SESSIN:
73099)
08/17/06 08:21:54 ANR3171E Configuration refresh with configuration manager
DSMSERV1 had to skip processing for one or
more objects.
(SESSIN:
73099)
08/17/06 08:21:54 ANR0409I Session 75280 ended for server DSMSERV1
(AIX-RS/6000). (SESSIN:
73099)
08/17/06 08:21:54 ANR3151E Configuration refresh failed with configuration
manager DSMSERV1. (SESSIN:
73099)

Stupid question, but should I not expect the configuration manager to
be able to update existing domains, etc. across my complex?

Does anyone have any idea what I am doing wrong, or if I have the
wrong expectations?

Thank you.

John Bremer

You can not manage existing objects with configuration management. You must
delete STANDART policy domain from subscribers or create another name from
manager server. Configuration manager distribute objects and changes to
subscribers. Also you can not change managed objects from subscribers.
Message
From: "John Bremer" <jbremer (AT) LANL (DOT) GV>
To: <ADSM-L (AT) VM (DOT) MARIST.EDU>
Sent: Thursday, August 17, 2006 5:26 PM
Subject: [ADSM-L] TSM configuration manager

All,

I want to set up TSM configuration manager. I have several AIX 5.1
TSM servers 5.3.2.

I have defined a profile on one server, and defined a profile
association to this configuration profile for domains, using our
"STANDARD" domain as a test to propagate additions and changes to
subscribers. Configuration manager is set "" to this server:

tsm: DSMSERV1>q profile f=d

Configuration manager: DSMSERV1
Profile name: TSM SERVER PRFILE
Locked?: No
Description: TSM Master
Server administrators:
Policy domains: STANDARD
Administrative command schedules:
Server Command Scripts:
Client Sets:
Servers:
Server Groups:

a second server I have defined subscription to the master:

tsm: DSMSERV2>q subscription f=d

Configuration Profile name Last update
manager date/time
DSMSERV1 TSM SERVER 08/16/06 11:59:40
PRFILE

This server has "Allow Replace" yes.

configuration manager I run:

notify subscribers

and it fails at the subscriber end:

08/17/06 08:21:53 ANR0408I Session 75279 started for server DSMSERV1
(AIX-RS/6000) (Tcp/Ip) for configuration
management.
(SESSIN:
75279)
08/17/06 08:21:54 ANR0409I Session 75279 ended for server DSMSERV1
(AIX-RS/6000). (SESSIN:
75279)
08/17/06 08:21:54 ANR0408I Session 75280 started for server DSMSERV1
(AIX-RS/6000) (Tcp/Ip) for configuration
management.
(SESSIN:
73099)
08/17/06 08:21:54 ANR3152I Configuration refresh started with
configuration
manager DSMSERV1. (SESSIN:
73099)
08/17/06 08:21:54 ANR3350W Locally defined domain STANDARD contains at
least
one node and cannot be replaced with a
definition from
the configuration manager. (SESSIN:
73099)
08/17/06 08:21:54 ANR3171E Configuration refresh with configuration
manager
DSMSERV1 had to skip processing for one or
more objects.
(SESSIN:
73099)
08/17/06 08:21:54 ANR0409I Session 75280 ended for server DSMSERV1
(AIX-RS/6000). (SESSIN:
73099)
08/17/06 08:21:54 ANR3151E Configuration refresh failed with
configuration
manager DSMSERV1. (SESSIN:
73099)
--
Stupid question, but should I not expect the configuration manager to
be able to update existing domains, etc. across my complex?

Does anyone have any idea what I am doing wrong, or if I have the
wrong expectations?

Thank you.

John Bremer