Re: Management Class Question?

[Efim]

No. Retain Only Version  - Specifies the number of days to retain the 
last backup version of a file that has been deleted from the client file 
system.
If you have 2 versions of file, in case deletion files from client this 
parameter  (RETONLY) doesn't work.
But if you have only one version after delete file from client it is 
last backup version of file and it will be retain only 60 days.

Usually:
Retain Only Version => Retain Extra Versions
Version Data Exists => Version Data Deleted
In you situation Retain Only Version 60 days and Retain Extra Versions 
NOLIMIT - it is not good situation.


If it is not true tell me about it.

Efim



* Joni Moyer <[EMAIL PROTECTED]> [Wed, 11 Apr 2007 07:32:58 
-0400]:

Hello everyone,

I want to create a management class that always keeps 2 versions of 

the

file for it's backups. Is the following correct in order to meet this
goal? Thanks in advance for any help!

Version Data Exists = 2
Version Data Deleted = 2
Retain Extra Versions = NOLIMIT
Retain Only Version = 60 (This hasn't been defined yet by the 

customer,

so if I left it at 60, would it keep each of the 2 files for 60 days
since
they were backed up?)


Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]

Management Class Question?

[Joni Moyer]

Hello everyone,

I want to create a management class that always keeps 2 versions of the
file for it's backups.  Is the following correct in order to meet this
goal?  Thanks in advance for any help!

Version Data Exists = 2
Version Data Deleted = 2
Retain Extra Versions = NOLIMIT
Retain Only Version = 60  (This hasn't been defined yet by the customer,
so if I left it at 60, would it keep each of the 2 files for 60 days since
they were backed up?)


Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]

Re: Management class question

[Richard Sims]

Geoff - Does 'dsmc q inclexcl' verify the Include?

   Richard Sims

Management class question

[Gill, Geoffrey L.]

I wanted to double check my syntax here. Being that there is a space in the
path I am assuming that this include to bind a specific directory to a
separate management class will work. Please correct me if I'm worng.



   include "E:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\*" 45day_mgt



This should bind all files in E:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP only (not its subdirectories) to management class
"45day_mgt".



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]

Re: management class question???

[Seay, Paul]

In the management class you set the primary storage pool.  To run the first
backup just direct it to the TAPE primary management class that is the
NEXTPOOL for the DISK management class.  After the first backup, change the
storage pool to the DISK management class.

Backups are determined by the node/filespace in the backups table regardless
of the storage pool the reside on.  Remember, data on a server can go to
limitless storage pools (actually TSM does have a limit on the total number
of storage pools).  All you are doing here is directing the data to another
storage pool for the first backup.

Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180


-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 11:19 AM
To: [EMAIL PROTECTED]
Subject: management class question???


Hi everyone!

I am creating a new management class for a user that wants all files backed
up incrementally no matter if it is open or not.  I know that I have to use
the dynamic parameter for copy serialization.  On a normal day I want the
backup to go to the disk pool, but the first time this server backs up it
will back up the entire 202 GB server.  My problem is that the disk pool is
only 34 GB.  I want to direct the first backup directly to tape and all
future backups to disk.  How do I do this?  If I tell the user to first use
a MC that goes directly to tape and then use a MC that goes to disk for all
others, will it not try to do a backup of all files for the second
incremental backup since it is technically using a new MC class or does it
go by files that exist?  Thanks in advance for any help!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: management class question???

[John Naylor]

After you have done the first backup to disk, backup your active policy set.
Then change the destination pool in the backup copygroup of your management
class in your backup policy set..
Validate and Activate your backup policy set
Thats the mechanical side but much more important if you are going to use
dynamic is to
make sure that the backup copies are usable if restored,
Thats after all the pont of backups, and using dynamic  you potentially are
going to get fuzzy backups which may or may not be of any use,






Joni Moyer <[EMAIL PROTECTED]> on 01/31/2003 04:18:35 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  management class question???



Hi everyone!

I am creating a new management class for a user that wants all files backed
up incrementally no matter if it is open or not.  I know that I have to use
the dynamic parameter for copy serialization.  On a normal day I want the
backup to go to the disk pool, but the first time this server backs up it
will back up the entire 202 GB server.  My problem is that the disk pool is
only 34 GB.  I want to direct the first backup directly to tape and all
future backups to disk.  How do I do this?  If I tell the user to first use
a MC that goes directly to tape and then use a MC that goes to disk for all
others, will it not try to do a backup of all files for the second
incremental backup since it is technically using a new MC class or does it
go by files that exist?  Thanks in advance for any help!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338








**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**

Re: management class question???

[Todd Lundstedt]

Or, just back it up to diskpool.  When the diskpool gets to the high water
mark, it will start migration to the next storage pool (I assume, your
tapepool).  When the diskpool gets completely full, TSM will automatically
send files to the next storage pool (again, assuming your tapepool),
meaning, directly to tape.
This is all good, as long as you have at least two tape drives.

One thing I would suggest is to run this backup outside of your normal
scheduled backups, so you will have this done (and hopefully copied to your
copy stgpool (offsite)) before the main backups for all your other clients
begin.

Hope this helps.
Todd





"Ford, Phillip"
cc:
Sent by: "ADSM:   Fax to:
Dist Stor Subject: Re: management class question???
Manager"
<[EMAIL PROTECTED]
ST.EDU>


01/31/2003
10:41 AM
Please respond
to "ADSM: Dist
Stor Manager"






Just change the destination pool of the given management class to the tape
pool (the one that the disk pool will migrate to).  Make sure you activate
the policy set.  Then do your first backup.  Now go in and change the
destination pool to the disk pool.  Make sure to activate the policy set
again.  That should do it.




--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]





-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 10:19 AM
To: [EMAIL PROTECTED]
Subject: management class question???


Hi everyone!

I am creating a new management class for a user that wants all files backed
up incrementally no matter if it is open or not.  I know that I have to use
the dynamic parameter for copy serialization.  On a normal day I want the
backup to go to the disk pool, but the first time this server backs up it
will back up the entire 202 GB server.  My problem is that the disk pool is
only 34 GB.  I want to direct the first backup directly to tape and all
future backups to disk.  How do I do this?  If I tell the user to first use
a MC that goes directly to tape and then use a MC that goes to disk for all
others, will it not try to do a backup of all files for the second
incremental backup since it is technically using a new MC class or does it
go by files that exist?  Thanks in advance for any help!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338




*
This message and any attachments is solely for the intended recipient. If
you are not the intended recipient, disclosure, copying, use or
distribution of the information included in this message is prohibited --
Please immediately and permanently delete.

Re: management class question???

[Richard Sims]

>I want to direct the first backup directly to tape and all
>future backups to disk.  How do I do this?

If you have the luxury of an exclusive backup window for this client,
you could most simply update the disk stgpool to ACCess=READOnly for
the duration of the backup, or trivialize the MAXSize.

  Richard Sims, BU

Re: management class question???

[Ford, Phillip]

Just change the destination pool of the given management class to the tape
pool (the one that the disk pool will migrate to).  Make sure you activate
the policy set.  Then do your first backup.  Now go in and change the
destination pool to the disk pool.  Make sure to activate the policy set
again.  That should do it.




--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]





-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 10:19 AM
To: [EMAIL PROTECTED]
Subject: management class question???


Hi everyone!

I am creating a new management class for a user that wants all files backed
up incrementally no matter if it is open or not.  I know that I have to use
the dynamic parameter for copy serialization.  On a normal day I want the
backup to go to the disk pool, but the first time this server backs up it
will back up the entire 202 GB server.  My problem is that the disk pool is
only 34 GB.  I want to direct the first backup directly to tape and all
future backups to disk.  How do I do this?  If I tell the user to first use
a MC that goes directly to tape and then use a MC that goes to disk for all
others, will it not try to do a backup of all files for the second
incremental backup since it is technically using a new MC class or does it
go by files that exist?  Thanks in advance for any help!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338




*
This message and any attachments is solely for the intended recipient. If you are not 
the intended recipient, disclosure, copying, use or distribution of the information 
included in this message is prohibited -- Please immediately and permanently delete.

management class question???

[Joni Moyer]

Hi everyone!

I am creating a new management class for a user that wants all files backed
up incrementally no matter if it is open or not.  I know that I have to use
the dynamic parameter for copy serialization.  On a normal day I want the
backup to go to the disk pool, but the first time this server backs up it
will back up the entire 202 GB server.  My problem is that the disk pool is
only 34 GB.  I want to direct the first backup directly to tape and all
future backups to disk.  How do I do this?  If I tell the user to first use
a MC that goes directly to tape and then use a MC that goes to disk for all
others, will it not try to do a backup of all files for the second
incremental backup since it is technically using a new MC class or does it
go by files that exist?  Thanks in advance for any help!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338

Re: IMAP Mail Server Issues - Management Class Question

[Wayne T. Smith]

We have a smaller but similar IMAP situation (about 3M files and 60G in
use, with exactly double those amounts stored in *SM).  I'll comment..

1. If restore of files changed in past "n" days is required to shorten
(initial) major restore times, why not just do this at restore time with
standard DSMC restore parms?

2. One could have a separate process that could duplicate portions of
the mailstore, with *SM backing up only those duplicates.  For example,
before backups, one might tar/zip/whatever each mailbox to a single file
(per mailbox). You'd probably be backing up more data (static would be
in with new data for each mailbox changed), but *SM DB would be
substantially smaller. For example, before backups, one might copy "new"
files to a separate folder and backup only the separate folder. (Yuk to
both!).

3. If backups slow because of the "large" number of DB entries, separate
the mailstore and use *SM's virtualmountpoint facility. Cyrus, if that's
your IMAP program let's you do this quite easily.

4. Look at your *SM retention policy to make sure it matches your need.
You might be surprised to learn how much of your *SM DB is used due to
inactive objects (for my "relatively low" values of retention, 50% of my
IMAP objects are inactive; if you keep discarded stuff for a month or
more, inactives may dominate your *SM DB!).

5. Consider that among all those LLBean ads stored on your mailstore are
mail items critical to your organizations long term and efficient
operation.  Maybe it's efficient to have someone ask mailbox owners why
they have a gigabyte of mail stored yet haven't connected in past 3
months?  Maybe it's efficient just to size your backup and IMAP
resources to match the need? (any of the copy options of point #2 above
have additional costs wrt complexity of operation, reliability of
restore, etc.).  Does your organization consider *SM resources to be
part of the cost of IMAP operations?  Maybe it should.

Hope this helps, wayne

Luke Dahl wrote:
> Hi All,
> TSM Server - 4.2.1.15, Solaris 9
> TSM Client - 4.2.1.0, Solaris 9
>
> We are backing up an IMAP mail server which creates a new file for every
> new mail message received.  The large number of files (new messages)
> created is increasing our database size at an alarming rate.  We'd like
> to specify a management class that will retain only the last 32 days
> worth of NEW messages.  It's my understanding that the Retain Only
> Version parameter applies only to inactive files.  Files (messages) are
> never deleted from the server (our users basically store their mail on
> the server indefinitely) so they never become marked inactive.  So, I'm
> wondering if I can somehow specify to only backup the most recent 32
> days worth of new files?  I do not want to include all of the files that
> reside on the server and I have no way of separating the most recent
> files into a separate area.  Basically, if we lose our mail server we
> want a method of quickly restoring only the last month's worth of new
> mail messages.  The size of the mail server (~400Gb) limits our ability
> to provide a restore of all the files in a reasonable amount of time and
> is burning up our database capacity.  Anyone else backing up IMAP mail
> servers or facing similar issues?  Any thoughts or suggestions are much
> appreciated!
>
> Luke Dahl
> NASA - Jet Propulsion Laboratory
> 818-354-7117

--

Wayne T. Smith -- [EMAIL PROTECTED] -- University of Maine System -- UNET

Re: IMAP Mail Server Issues - Management Class Question

[Prather, Wanda]

I've never had to deal with a situation like this.
But in the past, other people have suggested writing a script that finds all
the day's new files,
creating a tar file of them, backing up the tar file, then deleting it.

Makes it hard for you to find an individual message to restore, but
circumvents the DB growth issue.



-Original Message-
From: Luke Dahl [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 1:50 PM
To: [EMAIL PROTECTED]
Subject: IMAP Mail Server Issues - Management Class Question


Hi All,
TSM Server - 4.2.1.15, Solaris 9
TSM Client - 4.2.1.0, Solaris 9

We are backing up an IMAP mail server which creates a new file for every
new mail message received.  The large number of files (new messages)
created is increasing our database size at an alarming rate.  We'd like
to specify a management class that will retain only the last 32 days
worth of NEW messages.  It's my understanding that the Retain Only
Version parameter applies only to inactive files.  Files (messages) are
never deleted from the server (our users basically store their mail on
the server indefinitely) so they never become marked inactive.  So, I'm
wondering if I can somehow specify to only backup the most recent 32
days worth of new files?  I do not want to include all of the files that
reside on the server and I have no way of separating the most recent
files into a separate area.  Basically, if we lose our mail server we
want a method of quickly restoring only the last month's worth of new
mail messages.  The size of the mail server (~400Gb) limits our ability
to provide a restore of all the files in a reasonable amount of time and
is burning up our database capacity.  Anyone else backing up IMAP mail
servers or facing similar issues?  Any thoughts or suggestions are much
appreciated!

Luke Dahl
NASA - Jet Propulsion Laboratory
818-354-7117

IMAP Mail Server Issues - Management Class Question

[Luke Dahl]

Hi All,
TSM Server - 4.2.1.15, Solaris 9
TSM Client - 4.2.1.0, Solaris 9

We are backing up an IMAP mail server which creates a new file for every
new mail message received.  The large number of files (new messages)
created is increasing our database size at an alarming rate.  We'd like
to specify a management class that will retain only the last 32 days
worth of NEW messages.  It's my understanding that the Retain Only
Version parameter applies only to inactive files.  Files (messages) are
never deleted from the server (our users basically store their mail on
the server indefinitely) so they never become marked inactive.  So, I'm
wondering if I can somehow specify to only backup the most recent 32
days worth of new files?  I do not want to include all of the files that
reside on the server and I have no way of separating the most recent
files into a separate area.  Basically, if we lose our mail server we
want a method of quickly restoring only the last month's worth of new
mail messages.  The size of the mail server (~400Gb) limits our ability
to provide a restore of all the files in a reasonable amount of time and
is burning up our database capacity.  Anyone else backing up IMAP mail
servers or facing similar issues?  Any thoughts or suggestions are much
appreciated!

Luke Dahl
NASA - Jet Propulsion Laboratory
818-354-7117

Re: IMAP Mail Server Issues - Management Class Question

[asr]

=> On Wed, 28 Aug 2002 10:50:27 -0700, Luke Dahl <[EMAIL PROTECTED]> said:


> We are backing up an IMAP mail server which creates a new file for every new
> mail message received.

Cyrus? We do that here at UF, We've got about the same amount of mailbox
space, 450G.

> The large number of files (new messages) created is increasing our database
> size at an alarming rate.

Yes, that happens. :)

> We'd like to specify a management class that will retain only the last 32
> days worth of NEW messages.  It's my understanding that the Retain Only
> Version parameter applies only to inactive files.  Files (messages) are
> never deleted from the server (our users basically store their mail on the
> server indefinitely) so they never become marked inactive.

My money is on enlarging your database.  You're going to pay less for the disk
than you will for the gyrations you'll need to actually accomplish the goal
you set out.

To accomplish that goal, you're going to have to convince TSM that the files
are gone.  TSM really isn't constituted to forget about files that you've
still got present.  So:

1) You want things to dissapear after one day from
   the-place-that-gets-backed-up.  So you have two parallel heirarchies of
   folders.  You move mail messages from the backed-up heirarchy to the non.

Ugh, already.

2) You do want everything to get backed up, so it's not enough to e.g. move
   everything once a day.  What you want to do is e.g. post-process the TSM
   schedule log, and move each file that's been successfully backed up.

Ouch, even more.

3) This results in two separate folder heirarchies in your users' mailboxes.
   Expect questions and irritation at the answers.

Probably a deal-breaker, once you have to start explaining it to VIPs.


You may have more luck controlling grows-without-bounds by setting mailbox
quotae;  if management gets a choice of

a) kick some backups off the dock
b) Pay lots of money for more backup-server resources
c) promulgate policy to save resources

then you may get the spurs to enforce quota.


- Allen S. Rout

Re: Management class question

[Prather, Wanda]

That property only applies if you are using the HSM client.  It means that a
backup version must exist in a TSM backup storage pool before the file is
even eligible to be pushed out to an HSM storage pool due to x days of
non-use.  (The reason for the property has to do with how you would recover
a damaged HSM pool, disater recovery, etc)

Unfortuately there are places where the manuals use the term "migration" for
two different things 1) using the HSM client for disk grooming, which
actually MOVES seldom-used files off the client machine to a TSM-HSM pool,
and  2) relocating backup versions from a primary disk pool to a sequential
(usually tape) pool.  It's confusing.

I think it may be explained in the old old redbook that described how the
HSM client works, if that book still exists...



-Original Message-
From: Jolliff, Dale [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 8:19 PM
To: [EMAIL PROTECTED]
Subject: Re: Management class question


For the MIGRATIONREQUIRESBACKUP property, the Admin Reference guide says
"Specifies whether a backup version of a file must exist before the file can
be migrated"

doh.

Is there a better explanation of this property somewhere?

Re: Management class question

[Jolliff, Dale]

For the MIGRATIONREQUIRESBACKUP property, the Admin Reference guide says
"Specifies whether a backup version of a file must exist before the file can
be migrated"

doh.

Is there a better explanation of this property somewhere?

Re: management class question?

[Justin Bleistein]

I already looked there sometimes people use the archive option: "-archmc="
and I don't know what management class they used from the server side.
Thanks!

--Justin Richard Bleistein




"Cook, Dwight
E"To: [EMAIL PROTECTED]
Subject: Re: management class question?
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


06/05/2002
11:40 AM
Please respond
to "ADSM: Dist
Stor Manager"






filespaces as a whole, aren't bound to a managmement class...

I would check the include/exclude file and see how it is coded.
Also remember, if you change the include/exclude list, that will apply it
to
all files previously backed up so the include/exclude list would be the
place to look.

an example could be

...
include /home/.../* some_default_mgmt_class (or nothing here at all)
exclude /home/Idontlikethisuser/.../*
include /home/mysubdir/.../*  some_special_mgmt_class
include /home/someotherdirpath/.../* some_minimal_mgmt_class
...


Dwight


-Original Message-
From: Justin Bleistein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 05, 2002 10:01 AM
To: [EMAIL PROTECTED]
Subject: management class question?


Does anyone know how to tell what management class a filespace belongs too
from the server side? Is there a select or a query command?

--Justin Richard Bleistein

Re: management class question?

[David Longo]

select node_name,filespace_name,class_name from backups
where node_name='NODE' and filespace_name='FSNAME'.

Node has to be all UPPER CASE and filespace_name may be all
UPPER or mixed depending on platform etc.

This can give long display if lot of files in  filespace, I think
there is a SQL way to shorten but this will give you the basics.

David Longo

>>> [EMAIL PROTECTED] 06/05/02 11:00AM >>>
Does anyone know how to tell what management class a filespace belongs too
from the server side? Is there a select or a query command?

--Justin Richard Bleistein



"MMS " made the following
 annotations on 06/05/02 11:33:59
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: management class question?

[Wayne T. Smith]

On 5 Jun 2002 at 11:18, David Longo replied, in part:
> select node_name,filespace_name,class_name from backups
> where node_name='NODE' and filespace_name='FSNAME'.

You might want to change /class_name/distinct(class_name)/.

But then, while there is a default (and perhaps other) management
class(es) for files in a file space, a file space does not "belong" to
a management class.  Do you want to know the default management class
for a file in a file space or the management class for a particular
backed up object?cheers, wayne

Wayne T. Smith  [EMAIL PROTECTED]
ADSM Technical Coordinator - UNET   University of Maine System

Re: management class question?

[Cook, Dwight E]

filespaces as a whole, aren't bound to a managmement class...

I would check the include/exclude file and see how it is coded.
Also remember, if you change the include/exclude list, that will apply it to
all files previously backed up so the include/exclude list would be the
place to look.

an example could be

...
include /home/.../* some_default_mgmt_class (or nothing here at all)
exclude /home/Idontlikethisuser/.../*
include /home/mysubdir/.../*  some_special_mgmt_class
include /home/someotherdirpath/.../* some_minimal_mgmt_class
...


Dwight


-Original Message-
From: Justin Bleistein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 05, 2002 10:01 AM
To: [EMAIL PROTECTED]
Subject: management class question?


Does anyone know how to tell what management class a filespace belongs too
from the server side? Is there a select or a query command?

--Justin Richard Bleistein

management class question?

[Justin Bleistein]

Does anyone know how to tell what management class a filespace belongs too
from the server side? Is there a select or a query command?

--Justin Richard Bleistein

Re: Management Class Question

[George Lesho]

Jeff, I think what will happen if you zap the management classes within a policy
domain, data that was backed up or archived under the zapped managment classes
will be expired per the rules for the policy domain default management class
first for backups and archives. If you do not have a default management class,
then it would go by the policy domain grace period.

George Lesho
Storage/System Admin
AFC Enterprises






Jeff Rankin <[EMAIL PROTECTED]> on 03/08/2001 09:43:15 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Management Class Question



We are looking at doing a massive reorganization of our naming
standards within our TSM servers.  During this reorganization, some
management class we have will go away and new ones will be created.
Others will just be renamed.

I know that in order to bind data to a specific management class I can
just use the include statement for the clients and that will start
backing up or archive files to the new management class assignments,
but my question is what happens to the old data that is already backed
up to the TSM server?  Will it be rebound to the new management classes
or will it fall into the grace period retention of the policy domains?
If the policy domain is what controls the data retention in this case,
would it just be safer to leave all of the existing management classes
in place and just start backing up with the new management classes and
let the old data expire off?

We are running TSM 4.1.2. Any help would be greatly appreciated.

--
Jeff Rankin
Associate Technical Analyst, Excel Corporation
Phone:   316-291-2903
Fax: 316-266-4415
Email:   [EMAIL PROTECTED]

Re: Management Class Question

[James Thompson]

If the management class no longer exists, data will be expired based on the
default management class for the domain.

During your next full incremental on a given machine the following will
happen.

If the file or directory exists on both machine and the tsm server, then
that file or directory will get bound to the management class specified in
the include/exclude list or to the default management class.

There are a few scenarios you should consider.  Version that is inactive
with no actives, api data, etc... I would suggest creating some temporary
nodenames and testing this out yourself.  Backup some data using your
existing policies.  Then move these nodes over to a different domain.
Re-run the backups.  You can check the management class for the objects
using select queries.
select * from backups where node_name='testnode'
select * from archives where node_name='testnode'

James Thompson


>From: Jeff Rankin <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Management Class Question
>Date: Thu, 8 Mar 2001 09:43:15 -0600
>
>We are looking at doing a massive reorganization of our naming
>standards within our TSM servers.  During this reorganization, some
>management class we have will go away and new ones will be created.
>Others will just be renamed.
>
>I know that in order to bind data to a specific management class I can
>just use the include statement for the clients and that will start
>backing up or archive files to the new management class assignments,
>but my question is what happens to the old data that is already backed
>up to the TSM server?  Will it be rebound to the new management classes
>or will it fall into the grace period retention of the policy domains?
>If the policy domain is what controls the data retention in this case,
>would it just be safer to leave all of the existing management classes
>in place and just start backing up with the new management classes and
>let the old data expire off?
>
>We are running TSM 4.1.2. Any help would be greatly appreciated.
>
>--
>Jeff Rankin
>Associate Technical Analyst, Excel Corporation
>Phone:   316-291-2903
>Fax: 316-266-4415
>Email:   [EMAIL PROTECTED]

_
Get your FREE download of MSN Explorer at http://explorer.msn.com

Management Class Question

[Jeff Rankin]

We are looking at doing a massive reorganization of our naming
standards within our TSM servers.  During this reorganization, some
management class we have will go away and new ones will be created.
Others will just be renamed.

I know that in order to bind data to a specific management class I can
just use the include statement for the clients and that will start
backing up or archive files to the new management class assignments,
but my question is what happens to the old data that is already backed
up to the TSM server?  Will it be rebound to the new management classes
or will it fall into the grace period retention of the policy domains?
If the policy domain is what controls the data retention in this case,
would it just be safer to leave all of the existing management classes
in place and just start backing up with the new management classes and
let the old data expire off?

We are running TSM 4.1.2. Any help would be greatly appreciated.

--
Jeff Rankin
Associate Technical Analyst, Excel Corporation
Phone:   316-291-2903
Fax: 316-266-4415
Email:   [EMAIL PROTECTED]