ADSM-L

Re: [ADSM-L] SET DRMDBBACKUPEXPIREDAYS

2014-06-19 08:04:01
Subject: Re: [ADSM-L] SET DRMDBBACKUPEXPIREDAYS
From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 19 Jun 2014 11:59:59 +0000
We have our DRMDBBACKUPEXPIREDAYS set to 7.  We do a backup daily.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Karel Bos
Sent: Thursday, June 19, 2014 7:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] SET DRMDBBACKUPEXPIREDAYS

Running out of database space and drm retention. Seems I am the only one that 
is missing the relation between those 2.
Op 18 jun. 2014 18:35 schreef "Plair, Ricky" <rplair AT healthplan DOT com>:

> 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.
>
<Prev in Thread] Current Thread [Next in Thread>