Is she saying that since the server at that site crashed, they decided they no longer need those mailboxes ever again, and just want to clean up all the objects related to that PO and those mailboxes?
Isn't it reasonable to assume that in a scenario where a server has crashed, that one would recover it?
I don't understand what the problems is.
Main Topics
Browse All Topics





by: PsiCopPosted on 2007-10-11 at 04:36:19ID: 20055863
In a nutshell, yes, the limitation exists, and should be quite obvious.
If I have a mailbox on Post Office X, and Post Office X is down, how can my mailbox be changed at Post Office X?
Clearly, Post Office X must be running in order for my mailbox to be deleted or changed.
Now, it is possible to eliminate the Post Office...the whole thing... from the GroupWise System. At least from the perspective of the Domains and other Post Offices in the System. I'm not sure what that would get you. The user mailboxes in the Post Office that was removed would essentially be lost.
The TID you cite is for deleting an entire Secondary Domain, not just a Post Office. If the Post Office that needs to be deleted is the ONLY Post Office in the Secondary Domain, then it'll work fine. But if there are other Post Offices in the Domain, the procedure in that TID is *not* what you want to do.
Any idea as to what is preventing recovery of the down Post Office?
Quick overview of GroupWise structures:
First (Top) Level --> System (the entire GroupWise environment)
Second Level --> Domain (one is a Primary; other Domains, if any, are Secondary)
Third Level --> Post Office (one or more per Domain); Gateway (e.g. GWIA, GWWA; zero or more per Domain)
As you see, the Post Office is the "lowest" unit in the data hierarchy.