Restore shorcut and quota issue

Greetings,

The only two databases that plays role are users mailbox that is requesting the shortcut retrieval and ExShortcut.nsf on the Domino server where users mailbox is hosted.

ExShotcut DB on Domino is meant to be cleaned up on regular intervals. Check out if it has large amount of messages. If that is not the case then look at the quota on users mailbox. After shortcut is viewed by the user it goes to the trash folder of the users mailbox.

I hope this helps.

Thanks,

Rajan

Unfortunately it seems that nobody has a problem like this... .

Waiting for an aswer from some EMC "angel", the only thing I can do is to trap the error

"EMC SourceOne, unable to restore shortcut Note '0000094A'.: Unable to write to database because database would exceed its disk quota." in my Domino log.

Doing this is easy but another matter comes out: the log error does not say in which database SourceOne is working on. So my trapping is useless...

Any idea guys?

Hi Stefano,

What are the chances of exshortcut.nsf having quota issue ? When a replica is created by anything that issues a client type call that will create a lot of shortcut restore calls so that local replica will have full copies of the mail as opposed to shortcutted mail on the mail sever. this in turn might also create large amount of emails in exshortcut db. There is a cache interval to clear up this db but in this situation it might not be helping.

Try to reduce the interval to clear the cache and see if it helps. There is a way by looking at IIS logs on the SourceOne server to see which mailbox created most of the calls but mailbox name will need to be converted to ASCII.

Sorry I am not in front of computer to provide more details. There was shortcut restore logging build into EX shortcut extensions I will have to check if they exist in SourceOne as well.

Regards,

Rajan Katwal

Sent from my iPhone

Please ignore typing mistakes.

Ciao Rajan, thank you for your time spent for me.

ExShortcut.nsf doesn't have any quota setted so it is not the problem, it can grow up how much it likes.

The error arises when, during the creation of the new local replica, the user mail replica on the server reaches its quota due to the restore of the emails.

Once the quota is reached SourceOne is no more able to push the emails down to the mail file on server and then the local mail file will be incomplete (emails not restored will have no body).

Of course we have to prevent this. I think that SourceOne is not able to ignore the quota, so what should I do?

Thanks again,

Stefano

Ciao Rajan,

thank you for the answer, I know that these are the two db affected (ExShortcut.nsf and a mail file) but my problem is to rapidly identify which is the user mail db affected by the quota problem, consider that we have over than 3000 user...

We have implemented a new feature of lotus notes called "Managed Replica", which is a "clever" local replica of the mail file. In particular, if the lotus notes client discovers a problem on the local replica it automatically delete the file and creates a new replica on local. That operation helps our IT all around the world, but creates a new problem caused by SourceOne and the use of quota. The creation of the new replica activates the restore of all emails shortcutted by SourceOne and if the db raises over the quota the above error (EMC SourceOne, unable to restore shortcut Note '0000094A'.: Unable to write to database because database would exceed its disk quota.) is generated by EMC. Note that this error does not indicate which is the mail file involved so I have to check all mails in the server.

I have about 1000 user per server (clustered in pairs of servers for a total of 3000 users), so in my opinion the error written in the log by EMC should explain which is the mail file I should be able to raise up temporarly the quota quickly.

Unfortunately the use of the quota is a must, so what do you suggest?

Thanks in advance,

Stefano