Hello Robert,

the stgpool of ppoltype=activedata will keep only  the most actual version 
of client data on it., i.g. this is the active version of any file. there 
are two ways to fill up that "active data pool":
1st, the data is written simultanously during backup process. - if you 
like this, update the primary stgpool parameter activedata=...
2nd, - and this is not mutally exclusive - during server maintenance run 
command "copy activedata..."

if there is noc performance issue, I recommend to to both: define an 
active data destination on the primary pool and(!) run the copy command 
later on on all stgpools the data from last backup sessions may reside.
You need to run recalim stgpool on an actve data pool very often and you 
should define small volumes (i.e. 8GB), if this is a pool of devclass 
file.

best regards

Ullrich Mänz
Data Center Services

FRITZ & MACZIOL Software und Computervertrieb GmbH
Ludwig Str. 180D, 63067 Offenbach, Germany

Mobil   +49 170 7678 434
Fax:   +49 69 3801 3500 10
Web:   http://www.fum.de

Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936
Geschäftsführer: Heribert Fritz, Frank Haines
Inhaber: Imtech N.V., Gouda, Niederlande



Von:    Robert Ouzen <rouzen AT UNIV.HAIFA.AC DOT IL>
An:     ADSM-L AT VM.MARIST DOT EDU
Datum:  25.08.2012 11:27
Betreff:        [ADSM-L] question about copy activedata and 
pooltype=activedata
Gesendet von:   "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Hi to all

Anybody use the function poolltype=activedata in the def stg command , and 
the the command copy activedata.

I don’t quiet understand the logic of the process.
If I define a new storage pool with pooltype=activedata , the backup 
clients on it will keep all the versions defined on the copygroup  as on a 
regular stg definition?

This parameter allow just the process of a copy activedata to run 
correctly ?

Any input will be great

Thanks Robert