Reset the archive bit on DVS files that are now in a CAB

[jgillfeather]

Hello all,

we've noticed recently that a bunch of our Pending Exchange items are not processing into shortcuts (we use the archive bit trigger), and further investigation showed that the relevant DVS file is now in a CAB, but the DVS listed in the CAB is still showing the archive bit.

The vault is being backed up (BE 12.5 sp4) but this does not appear to be removing the archive bit from the DVS if its in a CAB (the ones not collected yet work aok).

Any clues? - should we expect BE to be resetting the archive bit in the compressed file?

regards,

Justin

[JesusWept3]

Ok so couple of things, firstly when an item is put in to a CAB file, it cannot be modified at all, you can't delete individual items from a CAB, the same way you can't edit it and save the changes in to the CAB file.

The other thing is that in order for a DVS to be collected, that item has to be backed up before it will be put in a CAB file, otherwise the item will remain as a DVS and not put in a DVS file.

My suspicion is that when you are going to the property of the DVS file, it is actually extracting the item to a temp directory first and it is that item that has the archive bit set (you could easily prove this with a procmon, by setting procmon to only filter on that particular file name)

Also i have a feeling what you might be seeing is Item Secured vs Backup, so when a large item with an attachment is created it creates three parts, a DVS file (the email and user information) a DVSSP (the attachment) and a DVSCC (The Text or HTML converted contents of the attachment that the index builds off of)

In order for an item to be "secured" all three of those items, the DVS, DVSSP and the DVSCC need to be backed up before the whole is considered "secured" (read: backed up) and then and only then will the pending items be changed from Pending to a fully archived item.

[jgillfeather]

Hi JesusWept2,

so you're suggesting that until the DVS has had the archive bit removed, the collector will ignore it?

You may well be right about the extracted file, will get that tested.

I don't think attachment's are the issue - we're seeing weeks worth of email remaining as pending, small and large emails.

Could the index's be the issue? We were testing whether or not BE reset archives if the job was flagged as incomplete (as it couldn't backup and open index files) so we removed them from the backup job.

cheers,

Justin

[MichelZ]

Justin

Are you using Backup mode when doing the backups?

Can you try to put EV in backup mode manually, and then remove it immediately?

If this does not help, can you restart the storage service?

It might be the case that EV is just "hanging" on those items...

Cheers