NG HSM does not move all expected blobfiles

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
User avatar
gabrieles
Advanced member
Advanced member
Posts: 124
Joined: Tue Feb 14, 2017 9:40 am

NG HSM does not move all expected blobfiles

Postby gabrieles » Wed Oct 16, 2019 9:11 am

Problem:
We found on some customer that NG HSM doMoveBlobs does not seems to move all expected blobs. We suspect that it does not select correctly the messages to be moved to the secondary store.
We found blobs on primary volume that are definitely older than the given policy, but have been not moved.
In a particular installation we have a mailstore with approximately 450 GB of mail.
It is a Centos 7 with ZCS 8.8.15 P2 NETWORK with latest (Oct 2019) zimbra-network-modules-ng-6.0.3.1570446218-1.r7.x86_64 package.
We set up a secondary volume, local, not compressed, and a policy "appointment,message:before:-6months".
Some accounts are older than 2016, so we expect to move a large part to secondary volume.
After launching a doMoveBlobs we found moved only 150 GB, much less than expected.

Action taken:
- We took an account created in 2016 and searched for messages "before 01/01/2018", widely over the policy limit. No 2018 messages are exepected to stay on the primary volume.
- We took a random message and did a zmmetadump and we found this:

[Database Columns]
mailbox_id: 35
id: 548804
type: 5 >> it's a message
...
date: 1540382283 (Wed 2018/10/24 13:58:03 CEST) >> it's from 2018
...
sender: user1@mydomail.com
recipients: user2@mydomail.com
subject: bla bla bla
...
mod_metadata: 2209752
change_date: 1540908843 (Tue 2018/10/30 15:14:03 CET) >> last modify was on 2018
mod_content: 2186951
...
[Blob Path]
/opt/zimbra/store/0/35/msg/133/548804-2186951.msg


- Opening the blobfile, we have the Date header that confirms October 2018.
Date: Wed, 24 Oct 2018 13:58:03 +0200 (CEST)

- The only attribute that gives a less than six months result, is the blob file date
$stat /opt/zimbra/store/0/35/msg/133/548804-2186951.msg
...
Access: 2019-10-16 10:12:02.413676619 +0200
Modify: 2019-09-10 14:02:42.601457411 +0200
Change: 2019-09-10 14:02:42.603457411 +0200
...


That could be possibile: the account had a restore on that date and the blobfiles are new.
The same survey was done for other accounts and other messages with the same results.

Why are those messages still on primary volume?
Does the brand new and modern NG HSM moves the messages selecting on the date of the blobfile???


sheepei
Posts: 13
Joined: Thu May 04, 2017 9:07 am

Re: NG HSM does not move all expected blobfiles

Postby sheepei » Thu Dec 26, 2019 2:07 am

any answer for this? I have faced the same situation too.

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 7 guests