ADSM-L

Re: client session stopps with 'no space available in storage... and all successor pools'

2006-09-11 05:49:31
Subject: Re: client session stopps with 'no space available in storage... and all successor pools'
From: Rainer Wolf <rainer.wolf AT UNI-ULM DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 11 Sep 2006 11:48:25 +0200
Hi all,

since changing some things as pointed out (thanks again to all hints) the error
now has luckily disappeared :-) . Although it may happen again
I just want to give a short feedback on what we've changed:
- increased the mountlimit from default 20 -> 200 on the devclass of the 
file-pool
- increased the random-acces backuppool
- decreased the migration thresholds for both random-access ( 90/50 -> 60/20 )
        and the sequential file-pool ( 90/70 -> 90/50 )
- moving from 'random migration by thresholds' to 'schedulded migration by time'
        with the 'duration=xx' option, running through admin-schedules
        at times with not much activity.

So until now everything is fine and the overall throughput-rate is much better 
now;
things wanted to do anyway to not weigh down the nightly backups with 
migrations.

the stages now appear something like ...
Storage        Device         Estimated      Pct      Pct    High    Low    
Next Stora-
Pool Name      Class Name      Capacity     Util     Migr     Mig    Mig    ge 
Pool
                                                              Pct    Pct
-----------    ----------    ----------    -----    -----    ----    ---    
-----------
BACKUPPOOL2    DISK               200 G     19.4     19.4      60     20    
FILEPOOL2
FILEPOOL2      FILE2              502 G     48.0     53.2      90     50    
TAPEPOOL2
TAPEPOOL2      3592            24,620 G      8.0     25.0     100     70


Cheers
Rainer

<Prev in Thread] Current Thread [Next in Thread>
  • Re: client session stopps with 'no space available in storage... and all successor pools', Rainer Wolf <=