• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Jan 112012
 

I’ve blogged about this before, but it’s another topic that appeared over the holidays.  Enterprise Vault can be configured with quota’s on a per archive basis (and inheritance from site settings). 

The things to note are :-

  • You set a size limit on the site settings or per archive in Mb.
  • Notifications can be sent to a user when the limit is reached, or when the limit is approached (either a set number of Mb before the limit, or a percentage).
  • Notifications are repeatable, just like mailbox quota notifications from Exchange.  On the site settings this can be set to the desired number of days.

When a limit is set you will see something like this on the archive:

archivelimit1

(For the purposes of the example I have set the limit on the archive itself)

If you see something like this :

archivelimit2

It normally means that the archiving task has not been run in order to determine whether the archive is within limits.

When the archiving task runs the quota limits are checked against the size of the archive.  If the limits have been exceeded, then Directory Database table called NotificationEntry is checked to see if the limit has already been sent as a notfication to the end-user.  If it hasn’t then it is sent, and the table updated.

The properties of the mailbox in the VAC may then look like this:

archivelimit5

You can also see the status in the Vault Store Usage Report in the VAC.

 

The notification can be customised.  Only one language of the notification can be sent out, meaning if you have some French users, some German, some English, then you need to pick an .msg file that will suit all.  The location of it is shown in the DTRACE of the Archiving Task below:

64189 04:47:46.298 [6048] (ArchiveTask) <3296> EV:L {CStorageArchive::GetVaultStatusEx:#793} Checked Storage information, and the throttle status for archive [1A776CE455996CE45AE38C56B148A3A6A1110000evsite] is still [DV_DS_AS_AVAILABLE (1)].

64190 04:47:46.298 [6048] (ArchiveTask) <3296> EV:L {CStorageArchive::GetVaultStatusEx} (Exit) Status: [Success]

64191 04:47:46.298 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::QuotaNotificationCheck – approaching quota message file name [C:Program FilesEnterprise VaultApproachingArchiveQuotaLimit.msg]

64192 04:47:46.298 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::QuotaNotificationCheck – exceeded quota message file name [C:Program FilesEnterprise VaultArchiveQuotaLimitReached.msg]

64193 04:47:46.298 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::QuotaNotificationCheck – VaultStatus is APPROACHING_LIMIT and Notifications are ENABLED|

64194 04:47:46.298 [6048] (ArchiveTask) <3296> EV:M CQuotaNotificationCache::GetNotificationLastSent – Entry not found in Cache, a Database lookup is required [1A776CE455996CE45AE38C56B148A3A6A1110000evsite] [/o=EV Training/ou=First Administrative Group/cn=Recipients/cn=manoj1]|

64196 04:47:46.298 [6048] (ArchiveTask) <3296> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() – Entry [m_nNumTries = 40]

64197 04:47:46.314 [6048] (ArchiveTask) <3296> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() – Successfully communicated with an EV Directory Service on the local machine

64198 04:47:46.360 [6048] (ArchiveTask) <3296> EV:M CDirectoryVaultObject::GetAttributeListFromType Attribute list for type NotificationEntry : NotificationId,VaultId,MailboxDN,VaultQuotaWarning,VaultQuotaExceeded

64199 04:47:46.360 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::QuotaNotificationCheck – Last Notification time checked, Proceeding to Send APPROACHING_LIMIT notification|

64200 04:47:46.360 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::SendQuotaNotification – Entry MsgFilename[C:Program FilesEnterprise VaultApproachingArchiveQuotaLimit.msg] MailboxDN[/o=EV Training/ou=First Administrative Group/cn=Recipients/cn=manoj1]

You can also see the following later on in the DTRACE:

64241 04:47:46.485 [6048] (ArchiveTask) <3296> EV:M CArchivingAgent::QuotaNotificationCheck – Approaching Limit Notification Not Required as Previous Notification was sent [0] hours ago. The notification frequency is currently set at [96]|

That indicates that the notification isn’t being resent, because it has already been sent recently.  96 is 96 hours, ie 4 days, as defined in my site settings.

 

The fact that the notification was sent is recorded in the Directory Database as shown below:

archivelimit3

Finally, the message in the end-users mailbox looks like this:

 

archivelimit4

Note:

It is worth pointing out that EV 9.0.2 had an issue with the notifications being sent out repeated, and it was addressed by way of the following hotfix :

http://www.symantec.com/business/support/index?page=content&id=TECH164193

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)