it wasn't that they were growing fast, it was that they were going into 
quarantine  that's why I opened the call to see why they were going into 
quarantine.
 
And I have to take a step back here as I forgot a few keys;
 
At first they wouldn't give me support till CU2 was installed, so they / me / 
we tried installing it 4 times, each time taking almost 2 hours before it would 
bomb on different phases of the CU2-
 
Then after a few more days of no joy, was the "solution" of creating new VM and 
new instance of Exchange, again,
I enjoyed it for the most part, till it was 4 am EST (2 PM IST) and I couldn't 
see the screen anymore. Anyway  I can now install 2013 with my eyes closed , 
and know more troubleshooting and diagnosing than I ever wanted to know.
 
But I just wonder if the "solution" should be considered acceptable

 

 

 

 

 

 

 

 

 

 

Jean-Paul Natola

 

 
Date: Tue, 17 Sep 2013 18:15:25 -0400
Subject: Re: [Exchange] Quarantined MB/Corruption on DB , PSS no solution
From: [email protected]
To: [email protected]

Didn't the original issue have to do with throttling mailboxes that were 
growing too fast, or something like that?  Are the logs showing the same thing?



On Tue, Sep 17, 2013 at 5:35 PM, Jonathan Link <[email protected]> wrote:

I think it's called backup.  It may involve the use of DAGs.  I dunno...

On Tue, Sep 17, 2013 at 4:39 PM, J- P <[email protected]> wrote:





Hi all,
 
Once again I called PSS only to have my case refunded, and no solution.
 
After 5 days, and about 50 hours on the phone, PSS' only resolution was "create 
a new VM install a new exchange and mount the DB".


 
I will say that I did get great insight into exchange , more than any class or 
course would ever give, however, after the "solution" I'm still getting random 
users mailboxes going to quarantine, and now they propose;


 
1. Move the mailbox if that fails
2. Run online repair if that fails
3. Offline repair if that fails
4. Delete and recreate mailbox
 
I'm not that upset because this is after all a small exchange deployment (~60 
users) , what if this happened on a large scale, this is not exactly what "PSS" 
Is supposed to do , it ? 


                                          





                                          

Reply via email to