Zimbra Forums

Good morning (here anyway),

We recently setup HSM on our Zimbra server and while it did move data on the initial run it has not moved anything since. My question concerns how the age parameter is used.

Currently we have the following.
zimbra@Zimbra:~$ zmcontrol -v
Release 8.0.7.GA.6021.UBUNTU12.64 UBUNTU12_64 NETWORK edition.

zimbra@Zimbra:~$ zmprov gs `zmhostname` zimbraHSMPolicy
# name zimbra.greenfieldin.org
zimbraHsmPolicy: message,document,appointment,task:before:-2year is:anywhere -in:junk

When I look at disk use I see that in the past month, no files have been moved to the HSM volume since the initial run.
July 23rd -------------------------------------------------------------------------------
administrator@Zimbra:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 15349744 3334600 11212380 23% /
udev 4078464 12 4078452 1% /dev
tmpfs 1635212 264 1634948 1% /run
none 5120 0 5120 0% /run/lock
none 4088028 0 4088028 0% /run/shm
/dev/sdc1 3170678184 1727439760 1282177256 58% /backup
/dev/sdb1 2097272832 564561756 1426188760 29% /opt
/dev/sdd1 1056893108 172735844 830470224 18% /hsm

June 26th -------------------------------------------------------------------------------
administrator@Zimbra:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 15349744 3327188 11219792 23% /
udev 4078464 12 4078452 1% /dev
tmpfs 1635212 264 1634948 1% /run
none 5120 0 5120 0% /run/lock
none 4088028 0 4088028 0% /run/shm
/dev/sdc1 3170678184 1705607592 1304009424 57% /backup
/dev/sdb1 2097272832 551560208 1439190308 28% /opt
/dev/sdd1 1056893108 172735844 830470224 18% /hsm

Looking at the mailbox log, I see that hsm is running and is checking the blobs.
zimbra@Zimbra:~/log$ cat mailbox.log.2018-07-22 | grep dgoodrich | grep hsm
2018-07-22 12:02:09,687 INFO [BlobMover] [name=dgoodrich@greenfieldin.org;mid=354;] hsm - Found no blobs that need to be moved.

So my question is, is HSM checking only the year portion of the date and moving data based on that alone? If so, will we I get no HSM movement until 2019? I had considered changing the policy from 'before: -2year' to 'before: -24month' but thought I should ask if there is something about HSM policies I do not understand.

Thanks,

DAve

Hey Dave,

Since HSM is a network edition feature , why dont you open a case with Z support! We would be happy to help you

Raun wrote:Hey Dave,

Since HSM is a network edition feature , why dont you open a case with Z support! We would be happy to help you

Well, I just thought it was an easy answer and didn't want to bother the support staff. I will open a ticket.

Thanks for the response.

DAve

you have paid for that support and we are always there for our clients . It does not matter if it is a small query or a Disaster recovery , we got your back .

Cheers,
R

Our version is no longer under support, so no help is coming. We have several other projects underway and an upgrade to Zimbra will not be done for a few months.

Anyone want to take a stab at this now?

DAve

Changing the schedule from 'before: -2year' to 'before: -24month' caused HSM to begin moving messages. My thought is that HSM was only looking at the year of the message date, so it would have moved a year's worth of messages on Jan 1 2019. Changing the schedule to 'before: -24month' causes HSM to look at both the year and the month of the message.

Or so I think, it worked anyway.

July 27 ------------------------------------------
administrator@Zimbra:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 15G 3.2G 11G 23% /
/dev/sdc1 3.0T 1.7T 1.2T 58% /backup
/dev/sdb1 2.0T 542G 1.4T 29% /opt
/dev/sdd1 1008G 165G 792G 18% /hsm

August 11, changed policy to before:-24months

August 13 ----------------------------------------
administrator@Zimbra:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 15349744 3302064 11244916 23% /
/dev/sdc1 3170678184 1744933648 1264683368 58% /backup
/dev/sdb1 2097272832 544165072 1446585444 28% /opt
/dev/sdd1 1056893108 200836516 802369552 21% /hsm

DAve