Can someone explain to me the difference between HSM Policy settings and HSM age ?
I can see that I have on a mailstore an HSM age of 30d but a HSM policy of 3 days whats gives ?
zimbra@mailstore01:~$ zmprov gs 'zmhostname' | grep -i hsm
zimbraBackupSkipHsmBlobs: FALSE
zimbraHsmAge: 30d
zimbraHsmBatchSize: 10000
zimbraHsmMovePreviousRevisions: FALSE
zimbraHsmPolicy: message,document,task,appointment,contact:before:-3day is:anywhere
zimbraMailboxMoveSkipHsmBlobs: FALSE
HSM Policy vs Age ?
-
pup_seba
- Outstanding Member
- Posts: 687
- Joined: Sat Sep 13, 2014 2:43 am
- Location: Tarragona - Spain
- Contact:
HSM Policy vs Age ?
Hi,
There are 3 basic ways to find out more about any specific attribute.
1) You can use the web admin console. If you leave your cursor moveless on top of a configuration you will be able to see the matching attribute and maybe the button "more" to get more info.
2) Look for documentation. Admin guide is a good place to start.
3) Use zmprov desc -a. In your particular case, this is the result:
[zimbra@zimbra1 ~]$ zmprov desc -a zimbrahsmage
zimbraHsmAge
Deprecated since: 6.0.0_BETA2. deprecated in favor for
zimbraHsmPolicy. Orig desc: Minimum age of mail items whose filesystem
data will be moved to secondary storage.. Must be in valid duration
format: {digits}{time-unit}. digits: 0-9, time-unit: [hmsd]|ms. h -
hours, m - minutes, s - seconds, d - days, ms - milliseconds. If time
unit is not specified, the default is s(seconds).
type : duration
value :
callback :
immutable : false
cardinality : single
requiredIn :
optionalIn : server,globalConfig
flags : serverInherited
defaults : 30d
min : 0
max :
id : 8
requiresRestart :
since :
deprecatedSince : 6.0.0_BETA2
[zimbra@zimbra1 ~]$ zmprov desc -a zimbraHsmPolicy
zimbraHsmPolicy
The policy that determines which mail items get moved to secondary
storage during HSM. Each value specifies a comma-separated list of
item types and the search query used to select items to move. See the
spec for <SearchRequest> for the complete list of item types and
query.txt for the search query spec.
type : string
value :
callback :
immutable : false
cardinality : multi
requiredIn :
optionalIn : server,globalConfig
flags : serverInherited
defaults : message,document:before:-30days
min :
max :
id : 1024
requiresRestart :
since : 6.0.0_BETA2
deprecatedSince :
There are 3 basic ways to find out more about any specific attribute.
1) You can use the web admin console. If you leave your cursor moveless on top of a configuration you will be able to see the matching attribute and maybe the button "more" to get more info.
2) Look for documentation. Admin guide is a good place to start.
3) Use zmprov desc -a. In your particular case, this is the result:
[zimbra@zimbra1 ~]$ zmprov desc -a zimbrahsmage
zimbraHsmAge
Deprecated since: 6.0.0_BETA2. deprecated in favor for
zimbraHsmPolicy. Orig desc: Minimum age of mail items whose filesystem
data will be moved to secondary storage.. Must be in valid duration
format: {digits}{time-unit}. digits: 0-9, time-unit: [hmsd]|ms. h -
hours, m - minutes, s - seconds, d - days, ms - milliseconds. If time
unit is not specified, the default is s(seconds).
type : duration
value :
callback :
immutable : false
cardinality : single
requiredIn :
optionalIn : server,globalConfig
flags : serverInherited
defaults : 30d
min : 0
max :
id : 8
requiresRestart :
since :
deprecatedSince : 6.0.0_BETA2
[zimbra@zimbra1 ~]$ zmprov desc -a zimbraHsmPolicy
zimbraHsmPolicy
The policy that determines which mail items get moved to secondary
storage during HSM. Each value specifies a comma-separated list of
item types and the search query used to select items to move. See the
spec for <SearchRequest> for the complete list of item types and
query.txt for the search query spec.
type : string
value :
callback :
immutable : false
cardinality : multi
requiredIn :
optionalIn : server,globalConfig
flags : serverInherited
defaults : message,document:before:-30days
min :
max :
id : 1024
requiresRestart :
since : 6.0.0_BETA2
deprecatedSince :