thanks for the reply. I still have problems, surely, for lack of use of the tool. for now, I'm just doing backups of virtual machines to disk. I have in mind to handle archives. Initially, I backup all virtual disk with the following definitions:
define domain rm
define policy rm rmvms
define mgmt rm rmvms rmvms_daily
define devclass rmvms_daily devtype=file format=drive maxcapacity=100G
define stgpool rmvms_daily rmvms_daily pooltype=primary maxscratch=200 deduplicate=yes collocate=no
define vol rmvms_daily /tsm-data/data/rmvms_daily_v01 F=102400 N=10
define copygroup rm rmvms rmvms_daily type=backup dest=rmvms_daily verexists=nolimit verdeleted=nolimit retextra=90 retonly=90
assign defmgmtclass rm rmvms rmvms_daily
validate policy rm rmvms
activate policy rm rmvms
this definition went perfectly, but the problem is that I finished the disk space.
then, we decided to separate backups of vm's with no user data (eg, terminal servers or application servers) of vm's with user data (eg fileservers).
and give a "small" retention to vm's without user data and a "long" retention to vm's with user data.
for this, I did the following configurations:
define policy rm rmvmcfg_pol # for vm's without user data
define policy rm rmvmdat_pol # for vm's with user data
define mgmt rm rmvmcfg_pol rmvmcfg_mc
define mgmt rm rmvmdat_pol rmvmdat_mc
define copygroup rm rmvmcfg_pol rmvmcfg_mc type=backup dest=rmvms_daily verexists=nolimit verdeleted=nolimit retextra=14 retonly=14
define copygroup rm rmvmdat_pol rmvmdat_mc type=backup dest=rmvms_daily verexists=nolimit verdeleted=nolimit retextra=14 retonly=14
assign defmgmtclass rm rmvmcfg_pol rmvmcfg_mc
assign defmgmtclass rm rmvmdat_pol rmvmdat_mc
the destination of all copygroups will be my actual storage
i'd like, when i executed the next backup, tsm will apply the news retentions
then:
validate policy rm rmvmcfg_pol
I'm getting this message:
ANR1150W Management class RMVMS_DAILY is not defined in policy set RMVMCFG_POL but is defined
in the active policy set for domain rm: files bound to this management class will be redound to the default management class if/when this set is activated
What is the problem?
I don't like a UNIQUE management class, because the mc well define the copygroup, and the copygroup define the retention.
You can aclarme or correct me this idea?