Agreed.
Most of my customers set that to between 5 and 15 days.
When would you ever restore your TSM data base back 60 days?

Only reason to recover a TSM DB backup other than the most recent one:  

a) to try and recover something that you incorrectly let expire; and that is 
only guaranteed to work if you have reusedelay set (to 60 in this case) on at 
least one of your storage pools where the data resides
b) your TSM DB got corrupted and nobody noticed until xx (in this case 60) days 
later
c) your TSM DB got corrupted, you tried the most recent DB backup, and the 
media is bad

60 seems unreasonable for any of those cases.

W

 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Michael malitz
Sent: Wednesday, June 18, 2014 2:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] AW: SET DRMDBBACKUPEXPIREDAYS

Hallo Ricky,

each TSM installation/environment is different, but assuming, that you do a TSM 
backup every day, for me, 60 days seem to be too much. 

I would suggest, that 7 days would be "enough". But that's also depending of 
course on your company's SLA prereqs/dependencies.

Rgds Michael

Michael.Malitz @tsmpoweradmin.com



-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
von Plair, Ricky
Gesendet: Mittwoch, 18. Juni 2014 18:32
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: SET DRMDBBACKUPEXPIREDAYS

Question, I am running TSM 6.3 and running out of database space with nowhere 
to get more at the moment.

My DRMDBBACKUPEXPIREDAYS is set to 60 days. I really don't think I need 60 
days. I would like to change this number to 30 days and get some space back.
What is a norm or an expected amount of days for this parameter?

Ricky M. Plair
Storage Engineer
HealthPlan Services
Office: 813 289 1000 Ext 2273
Mobile: 757 232 7258


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
CONFIDENTIALITY NOTICE: This email message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information and/or Protected Health Information (PHI) subject to 
protection under the law, including the Health Insurance Portability and 
Accountability Act of 1996, as amended (HIPAA). If you are not the intended 
recipient or the person responsible for delivering the email to the intended 
recipient, be advised that you have received this email in error and that any 
use, disclosure, distribution, forwarding, printing, or copying of this email 
is strictly prohibited. If you have received this email in error, please notify 
the sender immediately and destroy all copies of the original message.