Ex2003 w/ 185GB Priv Store - How to break up/maintain?
Exchange Server Forum Index Exchange Server
Discussion forums for Microsoft Exchange Server users.
Microsoft Outlook
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web ExchangeServerHelp.com
Ex2003 w/ 185GB Priv Store - How to break up/maintain?

 
Post new topic   Reply to topic    Exchange Server Forum Index -> Design
Author Message
Bill Oliman
Guest





Posted: Tue Feb 01, 2005 3:27 am    Post subject: Ex2003 w/ 185GB Priv Store - How to break up/maintain? Reply with quote

I have an Exchange 2003 server, recently upgraded from 5.5 with a 185GB
private store, and 5GB public store.

I'm running into issues since it's gone to Exchange 2k3 where some users are
receiving errors "Can't open item" in outlook. Nothing else, just "can't
open item". Preview pane shuts off, they have to reboot, calendar items
aren't popping up correctly, mail stuck in outbox or new mail not appearing
in inbox until they click on various folders. A real headache. At the same
time they are having this problem, another set of users have no problems
whatsoever, and find performance better than the 5.5 server days.

My thinking right now is to get exchange down to do an
isinteg -fix -test -alltests command against the private store, to see if
there are errors in the index pointers for some folks, fix any other
inconsistencies, etc... Seems to make sense from what I've read, haven't
done so in probably 3 years.

However, I'm not thinking this is going to be a one shot solution. Until I
can get an archiving solution in place for the file attachments and bring
the store size down, I'm thinking of ways to perhaps break up the store into
separate storage groups, or perhaps work in a cluster configuration (i'm
running exchange 2k3 enterprise) in order to provide as much uptime as
possible, and at least have some more control of when the system goes down,
specifically for who, and for how long. Everything right now seems so
vague - not being able to tell how long the process will take, having to
bring the entire email world down for this process, etc...and I'm not really
guaranteed this will do anything positive or address my issues...

I know this is really hitting a few different areas, but if you have any
re-design suggestions, i'd appreciate hearing your thoughts
Bill

Back to top
Medalist
Guest





Posted: Tue Feb 01, 2005 8:11 am    Post subject: RE: Ex2003 w/ 185GB Priv Store - How to break up/maintain? Reply with quote

Hi;

First of all, can you make a little test. Create a new storage group and
then move a mailbox which has problems that you have described below;
afterward try to open the mailbox again. And let me know if its happening
again...

Bora Güler

"Bill Oliman" wrote:

Quote:
I have an Exchange 2003 server, recently upgraded from 5.5 with a 185GB
private store, and 5GB public store.

I'm running into issues since it's gone to Exchange 2k3 where some users are
receiving errors "Can't open item" in outlook. Nothing else, just "can't
open item". Preview pane shuts off, they have to reboot, calendar items
aren't popping up correctly, mail stuck in outbox or new mail not appearing
in inbox until they click on various folders. A real headache. At the same
time they are having this problem, another set of users have no problems
whatsoever, and find performance better than the 5.5 server days.

My thinking right now is to get exchange down to do an
isinteg -fix -test -alltests command against the private store, to see if
there are errors in the index pointers for some folks, fix any other
inconsistencies, etc... Seems to make sense from what I've read, haven't
done so in probably 3 years.

However, I'm not thinking this is going to be a one shot solution. Until I
can get an archiving solution in place for the file attachments and bring
the store size down, I'm thinking of ways to perhaps break up the store into
separate storage groups, or perhaps work in a cluster configuration (i'm
running exchange 2k3 enterprise) in order to provide as much uptime as
possible, and at least have some more control of when the system goes down,
specifically for who, and for how long. Everything right now seems so
vague - not being able to tell how long the process will take, having to
bring the entire email world down for this process, etc...and I'm not really
guaranteed this will do anything positive or address my issues...

I know this is really hitting a few different areas, but if you have any
re-design suggestions, i'd appreciate hearing your thoughts
Bill



Back to top
Bill Oliman
Guest





Posted: Wed Feb 02, 2005 2:22 am    Post subject: Re: Ex2003 w/ 185GB Priv Store - How to break up/maintain? Reply with quote

Yes, it still happens...I moved my mailbox and the problem mailbox to a new
store and i still work fine and they still have issues. I dismounted and
ran the isinteg fix and remounted and they had the issue once today as
well...


"Medalist" <medalist@cehennem.com> wrote in message
news:07B99C11-9B6F-49D0-98C2-50F81564ECEA@microsoft.com...
Quote:
Hi;

First of all, can you make a little test. Create a new storage group and
then move a mailbox which has problems that you have described below;
afterward try to open the mailbox again. And let me know if its happening
again...

Bora Güler

"Bill Oliman" wrote:

I have an Exchange 2003 server, recently upgraded from 5.5 with a 185GB
private store, and 5GB public store.

I'm running into issues since it's gone to Exchange 2k3 where some users
are
receiving errors "Can't open item" in outlook. Nothing else, just
"can't
open item". Preview pane shuts off, they have to reboot, calendar items
aren't popping up correctly, mail stuck in outbox or new mail not
appearing
in inbox until they click on various folders. A real headache. At the
same
time they are having this problem, another set of users have no problems
whatsoever, and find performance better than the 5.5 server days.

My thinking right now is to get exchange down to do an
isinteg -fix -test -alltests command against the private store, to see
if
there are errors in the index pointers for some folks, fix any other
inconsistencies, etc... Seems to make sense from what I've read,
haven't
done so in probably 3 years.

However, I'm not thinking this is going to be a one shot solution.
Until I
can get an archiving solution in place for the file attachments and
bring
the store size down, I'm thinking of ways to perhaps break up the store
into
separate storage groups, or perhaps work in a cluster configuration (i'm
running exchange 2k3 enterprise) in order to provide as much uptime as
possible, and at least have some more control of when the system goes
down,
specifically for who, and for how long. Everything right now seems so
vague - not being able to tell how long the process will take, having to
bring the entire email world down for this process, etc...and I'm not
really
guaranteed this will do anything positive or address my issues...

I know this is really hitting a few different areas, but if you have any
re-design suggestions, i'd appreciate hearing your thoughts
Bill





Back to top
Medalist
Guest





Posted: Wed Feb 02, 2005 3:37 am    Post subject: Re: Ex2003 w/ 185GB Priv Store - How to break up/maintain? Reply with quote

So it shows that the problem is not at the database. The problem is in the
items at the users mailbox i think.

1. Back up all mailbox information by downloading messages to a PST.
2. In the Outlook client, select Import and Export from the File menu.
3. Follow the Import and Export Wizard and select Export to a File.
4. Select a file name and select Calendar as the file to Export from.
5. Delete the Calendar folder; to do this, start an Exchange Client from the
command line by typing exchng32. The calendar folder can be deleted from the
Exchange Client because it is viewed as a standard folder and not a required
Calendar folder.
6. Recreate the Calendar folder by starting Outlook from the command line
using "Outlook /resetfolders".
7. Move all messages back from the PST to the mailbox. From the File menu,
choose Import and Export and follow the Import and Export Wizard to import
the Calendar data from the file created in steps 3 and 4 above.


again,let me know the result...


"Bill Oliman" wrote:

Quote:
Yes, it still happens...I moved my mailbox and the problem mailbox to a new
store and i still work fine and they still have issues. I dismounted and
ran the isinteg fix and remounted and they had the issue once today as
well...


"Medalist" <medalist@cehennem.com> wrote in message
news:07B99C11-9B6F-49D0-98C2-50F81564ECEA@microsoft.com...
Hi;

First of all, can you make a little test. Create a new storage group and
then move a mailbox which has problems that you have described below;
afterward try to open the mailbox again. And let me know if its happening
again...

Bora Güler

"Bill Oliman" wrote:

I have an Exchange 2003 server, recently upgraded from 5.5 with a 185GB
private store, and 5GB public store.

I'm running into issues since it's gone to Exchange 2k3 where some users
are
receiving errors "Can't open item" in outlook. Nothing else, just
"can't
open item". Preview pane shuts off, they have to reboot, calendar items
aren't popping up correctly, mail stuck in outbox or new mail not
appearing
in inbox until they click on various folders. A real headache. At the
same
time they are having this problem, another set of users have no problems
whatsoever, and find performance better than the 5.5 server days.

My thinking right now is to get exchange down to do an
isinteg -fix -test -alltests command against the private store, to see
if
there are errors in the index pointers for some folks, fix any other
inconsistencies, etc... Seems to make sense from what I've read,
haven't
done so in probably 3 years.

However, I'm not thinking this is going to be a one shot solution.
Until I
can get an archiving solution in place for the file attachments and
bring
the store size down, I'm thinking of ways to perhaps break up the store
into
separate storage groups, or perhaps work in a cluster configuration (i'm
running exchange 2k3 enterprise) in order to provide as much uptime as
possible, and at least have some more control of when the system goes
down,
specifically for who, and for how long. Everything right now seems so
vague - not being able to tell how long the process will take, having to
bring the entire email world down for this process, etc...and I'm not
really
guaranteed this will do anything positive or address my issues...

I know this is really hitting a few different areas, but if you have any
re-design suggestions, i'd appreciate hearing your thoughts
Bill






Back to top
 
Post new topic   Reply to topic    Exchange Server Forum Index -> Design All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server Dedicated Servers
New Topics Powered by phpBB