PalmStrike
Technical User
Hi,
I have a little problem here. I was about to compact or compress the priv.edb file, as ours is twice the size it should be, yet it has filled up our server. I understand that as long as we spring clean the mailboxes, microsoft exchange will use space first and the information store will not grow anymore. I also understand that Microsoft Exchange defrags itself as one of it's daily system maintainence tasks.
Unfortunately, as i am new to this sort of thing, I was unaware that the information store can grow. I thought it was capped at specified size as defaultwhich then either deletes old emails or letts the user know that he/she must empty the rubbish. This will only have to be done the once, as I have now learnt that you can just limit the size of the mailboxes.
So now; we have a server with a 15GB mirrored hard disc, and the IS has filled this to the brim and I have no space on any server in order to use the ESEUTIL tool to reduce the it.
I can think of only 3 things to do:
1. Upgrade the server, This would now be too costly, as it makes our backup also redundent. (I don't think money will let this happen)
2. Break the mirror on the server, thus freeing up 15GB. I would consider this only if the hard disk could be re-mirrored afterwards. (I am surprised I even thought of entertaining this idea, I feel we would never get a fine state of the art server back to what it was)
3. Use my computer (it is brand new, and has 18GB of free space) to build the new Priv.edb file over the network.
The third one is the one I am thinking of if it is possible. We do have a reliable back up now, of that i am quite convinced, so if it did go wrong, I could throw the tape in and restore it all again. But when using the ESEUTIL tool, won't it then mean that Microsoft exchange is then having to look at my pc for it's information store from that point on? or is there an easy way to then put it back in it's original place once done.
By the way i am aware that this becomes probably a 2 day job.
Sorry for this being so long, but I would relish some opinions on options 2 and 3, as I don't want to go down the upgrade version purely to create some space we already have.
Kind regards
Rob
I have a little problem here. I was about to compact or compress the priv.edb file, as ours is twice the size it should be, yet it has filled up our server. I understand that as long as we spring clean the mailboxes, microsoft exchange will use space first and the information store will not grow anymore. I also understand that Microsoft Exchange defrags itself as one of it's daily system maintainence tasks.
Unfortunately, as i am new to this sort of thing, I was unaware that the information store can grow. I thought it was capped at specified size as defaultwhich then either deletes old emails or letts the user know that he/she must empty the rubbish. This will only have to be done the once, as I have now learnt that you can just limit the size of the mailboxes.
So now; we have a server with a 15GB mirrored hard disc, and the IS has filled this to the brim and I have no space on any server in order to use the ESEUTIL tool to reduce the it.
I can think of only 3 things to do:
1. Upgrade the server, This would now be too costly, as it makes our backup also redundent. (I don't think money will let this happen)
2. Break the mirror on the server, thus freeing up 15GB. I would consider this only if the hard disk could be re-mirrored afterwards. (I am surprised I even thought of entertaining this idea, I feel we would never get a fine state of the art server back to what it was)
3. Use my computer (it is brand new, and has 18GB of free space) to build the new Priv.edb file over the network.
The third one is the one I am thinking of if it is possible. We do have a reliable back up now, of that i am quite convinced, so if it did go wrong, I could throw the tape in and restore it all again. But when using the ESEUTIL tool, won't it then mean that Microsoft exchange is then having to look at my pc for it's information store from that point on? or is there an easy way to then put it back in it's original place once done.
By the way i am aware that this becomes probably a 2 day job.
Sorry for this being so long, but I would relish some opinions on options 2 and 3, as I don't want to go down the upgrade version purely to create some space we already have.
Kind regards
Rob
