You are on page 1of 4

PM,COPY GP,Serilasation

POLICY MANAGEMENT: - Policy created by administrator and stored in Database.


A) POLICY DOMAIN : - It is a logical way of managing backup & archive policies for a group of Nodes. It
contains one or more policy sets.
A client node can only be associated with one policy Domain, ut one node may be register one or more !"#
"erver.
Policy domain contains a grace period backup and an archive retention Period.
1) BACKUPRETENTION : - "pecify the No. of days to retain a backup version when the server is unable to
rebind the file to an appropriate management class.
2) ARCHIVERETENTION : - "pecify the no. of days to retain a Archive copy when the server is unable to
rebind the file to an appropriate management class.
NOTE:- !hese options are used when default management has no copy group.
B) POLICY SET : - Policy set is a $ollection of #anagement class. !here can be only one Active policy "et per
policy Domain.
After creation the policy set activate this because without activation it will not work. %hen we modify original
Policy set then we have to activate again.
C) MANAGEMENT CLASS : - A #anagement $lass contains only one ackup & Archive $opy group. &ser can
bind his files to a management class through the include'e(clude list.
D) COPYGROUP: - )ach management class can contain up to two copy groups.
1) BACKUP COPYGROUP
2) ARCHIVE COPYGROUP
COPY GROUP PARAMETER: -
VEREXIST= "pecify the ma(imum number of backup version to retain for files that are currently present on the client file
system. y default its value is *.
VERDELETE= "pecify the ma(imum number of backup version retain for files that have been deleted from the client file
system. +,-
Ret et!"= "pecify the number of days to retain a backup version after that has been inactive. y default ./.
Ret #$%&= "pecify the number of days to retain the last backup version of a file that has been deleted from the client file system.
+0/-
%hen we define the ackup copygroup at that time we set these parameter.
%hat us policy management cycle1 )(plain1
Policy domain23policy set23managementclass23assign def mgmtclass23copygroup23validate policyset
23activate policyset
Define domain server description45"erver Nodes5 backretention4./ archretention4.06
ackretention222%hen a backed up file is no longer associated with a backup copy group, it remains in server storage
for ./ days +backup retention grace period-.
Arch retention222%hen an archived file is no longer associated with an archive copy group, it remains in server
storage for .06 days +archive retention grace period-.
Def policyset server workstn description45Policy "et for %orkstation des5
Define mgmtclass server server data migdestination4N7N) description45Default management class for
"erver domain5
Assign defmgmtclass server server data
Define copygroup server server data type4ackup destination4DI"8DA!A fre9uency4, vere(ists4. verdeleted4,
rete(tra4,// retonly4,// mode4modified seriali:ation4shrstatic
Define copygroup server server data type4archive destination4diskdata retver4.06 seriali:ation4shrstatic
;uery copygroup server server type4backup
;uery copygroup server server type4archive
<alidate policyset server server
Activate policyset server server
<alidate policyset
&se this command to verify that a policy set is complete and valid before you activate it. !he command e(amines the
management class and copy group definitions in the policy set and reports on conditions that you need to consider
before activating the policy set.
Activate policyset
&se this command to copy the contents of a policy set to the A$!I<) policy set for the domain. !he server uses the
rules in the A$!I<). !he server uses the rules in the A$!I<) policy set to manage client operations in the domain.
=ou can define multiple policy sets for a policy domain, but only one policy set can be active. !he current A$!I<)
policy set is replaced by the one you specify when you issue this command. =ou can modify the A$!I<) policy set
only by activating another policy set.
Se!'"%'("t'#$: - "pecifies how !"# handles files or directory when they are modified during backup processing.
S)!St"t'*: - "pecifies that !"# back up a file or directory only if it is not being modified during backup. !"#
attempts to perform a backup as many as four times, depending on the value specified for the $>AN?IN?@)!@I)"
client option. If the file or directory is modified during each backup attempt, !ivoli "torage #anager does not back it
up.
St"t'*: - "pecifies that !ivoli "torage #anager backs up a file or directory only if it is not being modified during
backup. !ivoli "torage #anager attempts to perform the backup only once. Platforms that do not support the "!A!I$
option default to ">@"!A!I$
S)!D&$"+'*: - "pecifies that if the file or directory is being modified during a backup attempt, !ivoli "torage
#anager backs up the file or directory during the last attempt even though the file or directory is being modified.
!ivoli "torage #anager attempts to perform a backup as many as four times, depending on the value specified for the
$>AN?IN?@)!@I)" client option.
D&$"+'*: - "pecifies that !ivoli "torage #anager backs up a file or directory on the first attempt, regardless of
whether the file or directory is being modified during backup processing.
EXPIRE INVENTORYA 2It is a command to manually start the inventory e(piration processing. y this command we can
removes the client backup inactive files, which are store in storage pool. y default it is
automatic start but we can run manually.
y default it is start within *B hours. !his option set in CD"#")@<.7P!D in !"# "erver.
#inimum <alue is / it means start manual.
AUTOMATIC DATA MOVEMENT
A- MIGRATION : -Automatic Data #ovement between one "!? Pool to another "!? Pool is called #igration. y this
Process we can balance the Performance and cost of different "torage Devices. Eor each "!? Pool we have to define
Fow & >igh !hreshold.
>Ighmig
"pecifies that the server starts migration for this storage pool when the
amount of data in the pool reaches this percentage of the poolGs estimated
capacity. !his parameter is optional. =ou can specify an integer from / to
,//.
F7wmig
"pecifies that the server stops migration for this storage pool when the
amount of data in the pool reaches this percentage of the poolGs estimated
capacity. !his parameter is optional. =ou can specify an integer from / to
.
#igprocess2222!he number of migration processes is dependent upon the setting of the #I?P@7$)"" parameter and
the number of nodes with data on the migrating storage pool. Eor e(ample, if the #I?P@7$)"" parameter is e9ual
to si(, but there are only two nodes with data on the storage pool, migration processing only consists of two
processes, not si(.
#igdelay222"pecifies the minimum number of days that a file must remain in a storage pool before the file becomes
eligible for migration from the storage pool. Default is /.
#igcontinue222"pecifies whether you allow the server to migrate files that do not satisfy the migration delay time.
Ye, "pecifies that, when necessary to meet the low migration threshold, the server continues to migrate files that do
not satisfy the migration delay time. N# "pecifies that the server stops migration when no eligible files remain to be
migrated, even before reaching the low migration threshold. !he server does not migrate files unless the files satisfy
the migration delay time.
B) RECLAMATION: - It is a process in which fragmented data transfer from one or more volumes to a fewer volume. "o that
we reuse the original volume as a scratch volume. Its advantage is that we can save enough space.
It is depending upon reclaim threshold parameter when the threshold reaches this parameter then
reclamation process start. y default it is 0/H.
%e can set the @eclamation when we define or update the storage pool. !here will be a single
!hreshold value.
!he tape that shows full state , but the pct utili:ation low, then the tape is eligiligible for reclamation based on the reclamation
threshold.
RECLAMABLE -ILES: - A) Eiles e(pire or are deleted form the <olumes.
B) 7bsolete because of aging or limits on the no. of version of a file.
SINGLE DRIVE RECLAMATION: -
At first we have to define the "!? Pool with @eclam"!?pool parameter.
!his @eclam"!?Pool Points to another "!?Pool that can be used as the holding area for the data being
consolidating
!his @eclam"!?Pool may be any primary "!? Pool on the system or a new "!? Pool created for this purpose.
!his @eclam"!?Pool must be a se9uential with D)<!=P)4EIF).
$opy "!?Pool is may not defined as @eclam"!?Pool.
STEPS -OR SINGLE DRIVE RECLAMATION: -
D"#AD#$3 D)EIN) "!? @)$FA#P77F D)<$
D"#AD#$3 &PDA!) "!? !AP)P77F I## @)$FA#40/H @)$FA#"!?4@)$FA#P77F
C) COLLOCATION: - It is a process in which storing the data of single client node in minimal no. of volumes
AdvantagesA 2 Easter @estoration.
8eep client data together
Disadvantage:Migration is slow and collocation increases both the amount of server time needed to
collocate files for storing and the number of volumes required.
%hen you define the stg pool or update stg command we can set the collocation parameter.
$7FF7$A!I7N options areA 2 ?@7&P'N7D)'EIF) "PA$)'N7. +y Default ?@7&P-
?roupA
"pecifies that collocation is enabled at the group level for client nodes. !he server attempts to put data for nodes that
belong to the same collocation group on as few volumes as possible. If the nodes in the collocation group have
multiple file spaces, the server does not attempt to collocate those file spaces.
N7D)
"pecifies that collocation is enabled at the client node level. !he server attempts to put data for one node on as few
volumes as possible. If the node has multiple file spaces, the server does not attempt to collocate those file spaces.
EIlespace
"pecifies that collocation is enabled at the file space level for client nodes. !he server attempts to put data for one
node and file space on as few volumes as possible. If a node has multiple file spaces, the server attempts to put data
for different file spaces on different volumes.
"er 3update stgpool stgpoolname collocate4filesapce
"er3define collocgroup gropupname
"er3define collocmember clientnodename, nodename*222222
"er3update node nodename collocgroup4groupname
Define stg poolname devclassname $ollocate4group'filespace'node'none
BACKUPSET:A backup set is a collection of a clientGs active backed up data, stored and managed as a single obJect,
on specific media, in server storage. %hile the server allows you to create a backup set for any client node, a backup
set can only be used by a backup2archive client.
"er3?enerate backupset nodename backupsetname devclass4devclassname scratch4yes'no retention4noofdays
volumes4volume names datatype4file'image'application toc4yes tocmgmtclass 4 mgmtclassname
"torage Pool NameA A$8&PP77F
"torage Pool !ypeA Primary
Device $lass NameA DI"8
)stimated $apacityA *., ?
"pace !rigger &tilA ,//./
Pct &tilA ,//./
Pct #igrA *0.B
Pct FogicalA ,//./
>igh #ig PctA K/
Fow #ig PctA 6/
#igration DelayA /
#igration $ontinueA =es
#igration ProcessesA .
@eclamation ProcessesA
Ne(t "torage PoolA P@I#A@=LMMB/
@eclaim "torage PoolA
#a(imum "i:e !hresholdA No Fimit
AccessA @ead'%rite
DescriptionA ?eneral 7ffice Data
7verflow FocationA
$ache #igrated Eiles1A =es
$ollocate1A
@eclamation !hresholdA
7ffsite @eclamation FimitA
#a(imum "cratch <olumes AllowedA
Number of "cratch <olumes &sedA
Delay Period for <olume @euseA