Each of these 'TotalItemSize' is the size of that users mailbox only.
I had enough mailboxes (~300) that the output ran off the screen. I don't know if you actually have a mailbox database called 'disabled'.
So, I didn't get a SUM of all the mailboxes running this command, so if you have LOTS of mailboxes, you need to pipe the out the output to a text file...

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

What I need is, we have Users who quit the company and have Active Directory accounts disabled, but the mailbox is not disabled, I will have to find each AD disabled account and then search for equivalent mailbox then move it to the database that has a lot of white space.

You are correct that the log files generated will be the same size as the mailboxes being moved. If you have a very large amount of data to move, you should move it in groups and do backups between the groups to clear the transaction logs.

You should only move mailboxes into the database with a ton of whitespace if you can balance you databases such that each one doesn't have an excess of whitespace after the moves. If you can't do that, I would recommend moving the mailboxes out of the database with a ton of space, dismount the database, delete the database and logs from the disk, then remount the database. This will create a new database will no whitespace. You can then move mailboxes back to that database to balance things out.

That's a matter of opinion. With so much 'wasted' space in your database I think a defrag is a reasonable recommendation.

I think it would be helpful to know what your aims are, as your initial question was askinh what the unexplained space was in the DB, then your query changed to an unexplained need to move mailboxes into the DB with space in.

knowing what are you trying to achieve will help us answer your question......

EG:
Do you still need to know what the unexplained space is for?
Do you need help moving mailboxes?
Why are you moving them?

Have you thought of creating a new DB and moving the active users to the new DB and decommission the old wasted space DB

0

jskfanAuthor Commented: 2013-12-07

Totallytonto

My databases are all over 100GBs and they go to different drives.
Log files of all my databases go to one Drive named X: drive

Now I need either to create a new blank database and start moving from each database few mailboxes to the newly created database.

OR

I will move from each database few mailboxes to the exiting database that I previously mentioned and that has a huge amount of white space.

I have not done that before, I wonder if the wizard will ask me to the location of the log files that will be created?
we do full backup of our databases on week ends, so do you think it would be preferable to do the move of mailboxes on Friday ?

0

jskfanAuthor Commented: 2013-12-07

That been said… AFter moving few mailboxes from each database to the new database, then I need to balance between the existing databases…..I mean if DB1 is larger thane DB2 , then I will move few mailboxes from DB1 to DB2 , the same will apply for the rest of the databases .

So you intend to balance out the mailboxes between various DBs? Sounds good to me.

If you have a DB containing loads of white space it is perfectly safe to reuse it. Just make sure your old mailboxes were deleted for longer than the retention periods set for the DB, or they will still be there and there wont actually be any space.
Once the retention periods have been satisfied, the old data would be removed during the next maint operation (usually overnight)

If you would prefer to create a new, clean DB there's no reason not to as such. when creating a new DB you can specify the log file location but you can move them anytime if necessary.

With regard to backups, I always recommend taking backups before and after any major work so you have as many options as possible in the event of an issue.

If you intend to move a lot of mailboxes, keep an eye on the log file size and consider moving a limited number of mailboxes per day so the backups clear the logs for you before moving more.

0

jskfanAuthor Commented: 2013-12-08

i did not get this:

<<<Just make sure your old mailboxes were deleted for longer than the retention periods set for the DB, or they will still be there and there wont actually be any space.
Once the retention periods have been satisfied, the old data would be removed during the next maint operation (usually overnight) >>>>

0

jskfanAuthor Commented: 2013-12-08

when I move mailboxes from one database to another… then i should go back and delete manual the mailboxes that have been moved from their original database or they get deleted automatically after the move is done.??

Whitespace is data that has already been purged. Since he is moving mailboxes, and not deleting them, he doesn't need to worry about the dumpster.

-JJ

0

jskfanAuthor Commented: 2013-12-10

What I meant is:

l need to move mailboxes from DB1 to DB2 then:
-- Would the wizard ask me where to put the log files that will be created in the destination drive, assuming DB1 and DB2 are in different drives

--- when I move mailboxes from DB1 to DB2 , then if I check DB1, would I still see the mailboxes that I moved ?…if the answers is Yes..the operations needs to be called COPY mailboxes…if the answer is No then it can be called MOVE mailboxes.

when I move mailboxes from DB1 to DB2 , then if I check DB1, would I still see the mailboxes that I moved ?…if the answers is Yes..the operations needs to be called COPY mailboxes…if the answer is No then it can be called MOVE mailboxes.

The answer is no. It is a move mailbox process. The mailbox cannot exist in more than one database.