Thank you kindly.
I prefer CLEAN URL's.
No TIME to muck about looking for a message.
It's just proper form and Good Manners to post a CLEAN URL -- sans
shilly-shallying or importuning.
All you had to do was quote Peter R. as follows:
Peter.R In: microsoft.public.windows.live.mail.desktop
Michael is correct Noel.
Since the database for WLMail and WMail does not contain the messages, it
only references their meta-data and indexes their location.
But does it BACKUP all the STORAGE files as well -- for example a storage
file that contains 10,000 emails IMPORTED from OE6? -- DSH
Additionally, the Extensible Storage Engine (ESENT or ESE, the same Exchange
uses) keeps a backup of all transactions (initially through log files).
Whilst the full backup of the database is deleted during database
compaction, it is recreated shortly afterward and periodically updated.
If the database is corrupted, WLMail first tries to restore it from the
backup. Often though, new messages have been received since the database was
backed up. Such messages don't have entries in the database and are
therefore 'recovered' during the restoration of the database.
Thus, manually replacing the database with an older version will likely
cause the 'recovery' of all non-indexed messages. However, messages that
were previously indexed but no longer exist (since deleted), may remain
referenced in the database, and so appear in WLMail's message list. Such
non-existent messages will obviously produce an error when one attempts to
open them from the message list.
A very detailed explanation of the ESE database can be found at: http://en.wikipedia.org/wiki/Extensible_Storage_Engine
ESENT provides its own utility called Esentutl (see attached screenshot),
that, whilst it cannot reconstruct deleted messages, can be used for certain
database file management functions, namely defragmentation (compaction),
recovery, integrity check, checksum, repair, file dump, and copy.
Esentutl.exe is located in the Windows\System32 folder, but is run from an
elevated command prompt.
Note: If there are spaces in the file *path*, you need to enclose the file
path in quotation marks ("")
To test the integrity of the database:
Vista: esentutl /g "%localappdata%\Microsoft\Windows Live
XP: esentutl /g "%userprofile%\Local Settings\Application
Data\Microsoft\Windows Live Mail\Mail.MSMessageStore"
Whilst Esentutl can be useful, and interesting to experiment with, I don't
recommend using it to compact WLMail's database, as it is much safer to do
it through WLMail itself.
(Windows Vista Home Premium with Windows Live Mail 12.0.1606)
"There are more things in Heaven and earth, Horatio, than are dreamt of in
your philosophy." - Shakespeare
That's one of my favorites from _Hamlet_ too.
No one couth ever shouts in Mory's -- nor am I shouting here.
It's called EMPHASIS.
Lux et Veritas et Libertas
"Ildhund" <jnllb@xxxxxx> wrote in message
> "D. Spencer Hines" <panther@xxxxxx> wrote in message
>> Ildhund's response doesn't deal with the AUTOMATIC Backup WLM makes each
>> time it compacts on its own and how to USE it...
> [Please don't SHOUT - this isn't Mory's.]
> It didn't actually deal with anything else. WLMail's message about
> automatic backup refers to copying Mail.MSMessageStore. *You* can't use
> this copy unless you know the ins and outs of ESE; the program uses it
> when something goes wrong. It should not be regarded as a substitute for
> performing regular backups of your messages etc. as described in winston's
>> And his LINK doesn't WORK.
> It will if you have msnews.microsoft.com as your default news server,
> which is the default setting for WLMail. You won't find Peter's post at
> Google Groups, probably because he's still using base64 encoding, but you
> will at
> or http://tinyurl.com/54wbwe
> Alternatively, you could have used the search and sort mechanisms in
> WLMail to locate the post in just a few seconds.
>> "...winston" <winstonmvp@xxxxxx> wrote in message
>>> You don't, It's not OE's Oldsmobile...see Ildhund's response.
>>> "D. Spencer Hines" <panther@xxxxxx> wrote in message
>>>> Thank you kindly.
>>>> I was also interested in the BACKUP that is made every time WLM
>>>> compacts and how we use that to RESTORE.