Gestione delle Quote nei Database

A partire dalla R6 è stato inserito un nuovo sistema di gestione delle quote. Non esiste più il concetto di quota Assoluta e quota relativa (tipico della R5). ora se una quota viene impostata, essa continuerà ha permettere la ricezione e l'invio di posta a meno che l'amministratore non intervenga sulle configurazioni all'interno del documento di configurazione del server:

Spostarsi nel documento di Configurazione del server, quindi sotto "Router/SMTP" - "restrictions and Controls" - "Delivery Controls".

Nei campi (vedi immagine) è possibile impostare avvertimenti sia per eventi di tipo Warning che eventi di tipo Over Quota. Per entrambe è possibile inviare e-mail di notifica ad intervalli specifici o ad ogni e-mail in arrivo.




Calcola Dimensione del File di posta in consegna

In Aggiunta a quanto sopra, è possibile impostare il router perchè verifichi prima di consegnare la posta in un Database quotato non solo la dimensione del database ma anche la percentuale utilizzata. In questo modo considera sempre i database sulla base effettiva di dati (in attesa che il task compact schedulato riadatterà la dimensione effettiva del database) al suo interno.

Per impostare questo controllo andare nel documento del server sotto la linguetta "Transictional Logging". (questo parametro funziona anche se il transictional logging non è abilitato)



Questi parametri possono essere utilizzati anche per configurazioni dove non è attivo il Transictional log e corrispondono ai parametri notes.ini seguenti:

NSF_Quota_Method

Syntax: NSF_Quota_Method=n

Description:  This variable reflects the mail file database quota enforcement method enabled in the Server document, where n indicates the specific method.  If quota enforcement methods are enabled, whenever the Router delivers mail, it compares the current size of the destination mail file against its configured database quota or threshold. If the size exceeds one of these, the Router takes appropriate action.

1 - check space used in file when adding a note

2 - check file size when extending the file

3 - check file size when adding a note

Applies to:  Servers

Default:  None

UI equivalent:  None, although you can specify this setting  in the Quota enforcement field on the Transactional Logging tab of the Server document.

NSF_Quota_Method=1

The Router calculates the current size of a mail file from the amount of space that messages occupy in the database and determines whether mail files are in compliance with configured warning thresholds or quotas based on this calculation. White space in the database is discounted. If the user is over quota and quota enforcement is enabled, no new messages are delivered. If the mail file is close to its quota, the Router continues to deliver messages only until their cumulative size exceeds the quota; thereafter, messages are held or rejected, depending on the enforcement setting.

When a user deletes a message, the space occupied by that message is immediately removed from the calculated size of the mail file. There is no need to run the Compact task to recover space. Users who cannot receive mail because of a quota violation can reduce the current size of the mail file immediately by archiving or deleting messages.

If transaction logging is enabled on the server, select this method of enforcement, because it does not require administrative intervention to compact mail files.

Check filesize when extending the file
NSF_Quota_Method=2

(Default) The Router calculates the current size of a mail file from its actual physical size. The calculated physical size includes the unused "white space" in a file that results when a user deletes or archives a message. Domino does not immediately recover this white space. As a result, accumulated white space may account for a large portion of the file size, so that the actual mail file size is considerably larger than the combined size of its stored messages.

The size check occurs only if adding a message requires an increase in the size of the mail file. When quota enforcement is enabled and this option is selected, if a message delivered to the mail file requires an increase in the file size that would result in a quota violation, delivery fails. However, a message is always delivered if there is sufficient white space to accommodate it.

On servers that do not use transaction logging, users can run the Compact task to remove white space and decrease the file size. However, when transaction logging is in effect, users cannot compact their own mail files. An administrator must run Compact with the -B option to reduce the size of the file.

Check filesize when adding a note
NSF_Quota_Method=3

The Router calculates the current size of a mail file from its actual file size. Both the space occupied by messages and white space in the database count toward the total size.

This option is more restrictive than the preceding option, because the Router checks the quota every time it adds a message to the mail file, regardless of whether this results in an increase in file size.

On servers that do not use transaction logging, when quota enforcement is enabled, select this option to eliminate inconsistent behavior during delivery to the mail files of users who exceed their quotas. Because the Router always checks the current file size when delivering a message, after a mail file reaches quota, no new messages are delivered, even if a particular message is small enough to fit within the available white space in the mail file.

Note On servers where transaction logging is enabled, selecting this option can prevent a user from recovering from a quota violation, since compacting the mail file does not reduce its size, preventing the user from getting back under quota. An administrator must run Compact with the -B option to reduce the size of the file.