ADSM-L

Re: [ADSM-L] Lots and lots of FILLING volumes on Replication Target server

2017-04-24 09:18:40
Subject: Re: [ADSM-L] Lots and lots of FILLING volumes on Replication Target server
From: Sasa Drnjevic <Sasa.Drnjevic AT SRCE DOT HR>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 24 Apr 2017 15:02:55 +0200
Hi Zoltan,
just a few quick ones...

-reclamation won't touch volumes in filling state

-are those volumes R/W ?  if not, check ACTLOG

-check MOUNTLimit for affected devclass(es)

-check MAXSIze for affected stg pool(s)


I'd rather use collocation...

I don't have any ideas on dedupe...

Regards.

--
Sasa Drnjevic
www.srce.unizg.hr



On 24.4.2017. 14:44, Zoltan Forray wrote:
> Server=Linux TSM 7.1.6.3   -  Sole usage is as a Replication Target for
> 5-TSM servers - also at 7.1.6.3.
>
> I am dealing with a situation where I am discovering lots and lots (>700)
> of storage volumes in a filling state and most are <0.5% used. I am running
> out of storage pool space until I manually perform move data's to clear
> them out.  This isn't the first time I had to do this.
>
> Why isn't automatic reclamation handling them (set to 65%). ReuseDelay is
> set to 0. Am I missing some setting or process I need to perform
> regularly?  This is the first time I have dealt with devclass=FILE and the
> various issues that come with it (IMHO, devclass=DISK requires so much less
> maintenance)
>
> This is my first server I am running dedupe on.  Not sure if that is a
> factor.  Also,  collocation is turned off.
>
> The target storage is an ISILON box via NFS.
>
>
>
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>