reconstruct post mailstore move
Is there a recommended procedure for the use of the reconstruct command after moving a large number of users from one msg system to a new one, eg an imsbackup > imsrestore to a completely new backend mailstore egiMS5.2 > JES 6.3 ?
reconstruct -r -p primary
or
reconstruct -p primary -m
I am not clear what the fundamental difference between these two options are.
Likewise can I run the reconstruct while the system is "live" and mail is being inserted into the mailboxes?
Thanks -john
[530 byte] By [
goubeauxa] at [2007-11-27 10:27:49]
# 1
Hi,
> Is there a recommended procedure for the use of the
> reconstruct command after moving a large number of
> users from one msg system to a new one, eg an
> imsbackup > imsrestore to a completely new backend
> mailstore egiMS5.2 > JES 6.3 ?
If you are using imsbackup/imsrestore you shouldn't need to run reconstruct.
> reconstruct -r -p primary
> or
> reconstruct -p primary -m
>
> I am not clear what the fundamental difference
> between these two options are.
The first command works at the user folder level - so it cross-checks the *.msg files (size/permissions & what not) in the account with the store.idx contents etc. It does a few other things but it operates at this level.
The second command works at the store database level (mailbox database). So basically makes sure that the cache mailbox folder information (store.idx files/folders exist/accounts exist) and that sort of thing.
I suggest you read the manuals which explain the structure of the message store etc.
> Likewise can I run the reconstruct while the system
> is "live" and mail is being inserted into the
> mailboxes?
Yes. Although if you are going to run these commands do them out-of-hours as they can be I/O intensive and also lock the database whilst changes are made which can slow down response times.
Regards,
Shane.
