ADSM-L

Re: [ADSM-L] permanent retention

2012-12-12 17:17:32
Subject: Re: [ADSM-L] permanent retention
From: Bob Levad <blevad AT WINNEBAGOIND DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 12 Dec 2012 22:05:22 +0000
Gary,

Since you're using backup for archiving, you can route these backups to your 
disk/tape archive pools, then you'll avoid having to move the data around much 
once it's been saved.

Bob.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ron Delaware
Sent: Wednesday, December 12, 2012 2:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] permanent retention

Gary,

The problem you will run into is that the backup data will be mixed in
with all of the other backup data, unless you have a management class that
sends the data to a separate storage pool and tape pool.  If you need to
have this data isolated, archives or a separate storage pool is the only
way to go.
_________________________________________________________
Ronald C. Delaware
IBM IT Plus Certified Specialist- Expert
IBM Corporation | Tivoli Software
IBM Certified Solutions Advisor - Tivoli Storage
IBM Certified Deployment Professional
916-458-5726 (Office)
925-457-9221 (cell phone)
email: ron.delaware AT us.ibm DOT com
Storage Services Offerings



From:   "Lee, Gary" <GLEE AT BSU DOT EDU>
To:     ADSM-L AT vm.marist DOT edu
Date:   12/12/2012 01:53 PM
Subject:        Re: [ADSM-L] permanent retention
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>



Ron:

I understand that archive is preferable, but there is sufficient data
there as to interfere with daily backups.  Therefore, I want to do it with
backups so as not to re-move data.

I have a management class "permanent-retain" with a backup copygroup
defined as follows:

                    Copy Group Type: Backup
               Versions Data Exists: 1
              Versions Data Deleted: 1
              Retain Extra Versions: No Limit
                Retain Only Version: No Limit


in dsm.opt I have:

INCLUDE.BACKUP "*:\Keep\...\*" permanent-retain
INCLUDE.BACKUP "*:\Keep\...\*.*" permanent-retain

Will this do the job and not retain too much data?

Thanks for the help.

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Ron Delaware
Sent: Wednesday, December 12, 2012 12:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] permanent retention

Gary,

You really don't want to use backup's for long term retention, that is an
archive function.  But if you must, you set everything to NOLIMIT NOLIMIT
NOLIMIT NOLIMIT that way the data will hang around forever, but as I
stated, Archives are the way to go
_________________________________________________________
Ronald C. Delaware
IBM IT Plus Certified Specialist- Expert
IBM Corporation | Tivoli Software
IBM Certified Solutions Advisor - Tivoli Storage
IBM Certified Deployment Professional
916-458-5726 (Office)
925-457-9221 (cell phone)
email: ron.delaware AT us.ibm DOT com
Storage Services Offerings



From:   "Lee, Gary" <GLEE AT BSU DOT EDU>
To:     ADSM-L AT vm.marist DOT edu
Date:   12/12/2012 10:46 AM
Subject:        [ADSM-L] permanent retention
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>



Just received a request to have a few files stored in tsm essentially
forever.

I am trying to figure out the best way to accomplish this with minimal
administrative overhead.

So far,
1. create a management class with an archive group set for 9999 days, then
archive the files.

2. create a management class and use backup, but I am unclear how to
accomplish permanent retention there?

Any ideas well be appreciated.



Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
This electronic transmission and any documents accompanying this electronic 
transmission contain confidential information belonging to the sender. This 
information may be legally privileged. The information is intended only for the 
use of the individual or entity named above. If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or the taking of any action in reliance on or regarding the contents of this 
electronically transmitted information is strictly prohibited.