(e-mail address removed), Kerry at
(e-mail address removed) wrote on 1/23/09 1:17 AM:
FWIW, the main reason I exclude the database from my Time Machine backupsis
simply that since the database typically is about 2 GB, if I allowed TM to
back it up throughout the day, I'd "waste" a lot of drive space for perhaps
only a few emails.
I find that
<
http://blog.entourage.mvps.org/2008/01/alternative_method_to_use_ento...
and_time_machine.html>, coupled with the use of the free TimeMachineEditor
(<
http://timemachineeditor.en.softonic.com/mac>) provide a very flexible and
effective way to deal with Microsoft's ridiculous "monolithic database"
design approach to Entourage.
--
Version: 2008
Operating System: Mac OS X 10.5.4 (Leopard)
Processor: Intel Core 2 Duo
Email Client: POP
Yes, well I totally agree with why you're not using Time Machine for
backups. 2 gigs would not only use an excessive amount of disk space
if it backed up every hour but also it would take a while even using a
Firewire 800 drive which I use. However, I keep my database fairly
lean (under 200 megs) by archiving my data to an archive file for two
reasons. One, I feel a database of this size is dangerous. If it
corrupts and my guess is it will, you are reliant on rebuild to
restore it to a functional database. Rebuild isn't working properly
and will often create an issue in the rebuilt database. This is a
known issue to Microsoft and although they are aware of the issue the
are not sure what's wrong and hence have no time-frame on a fix (to
test this, if your database ever fails after a rebuild, call Microsoft
tech support and ask them what to do. They won't be able to tell you
and if you are supposed to pay for the incident as you've used your
two free incidents you won't be charged as there is no solution so the
incident will be closed as unsolved but you can still call back on the
SRX number later to see if the issue is resolved and it will just be
reactivated. If they have a resolution, let us know as I would sure
love this). So now, you are completely reliant on your latest backup
and you have to hope that isn't corrupt. If it is, you will have to
move back to your most recent database, say two or three days old that
isn't corrupt. I am just moving back an hour or so to find an
uncorrupted DB. The second reason is that since this is a monolithic
database, any change to it will cause any of my backup systems and I
use four daily to spend a lot of time and use a lot of disk space to
back this up. Since I keep a robust archive database that stores data
that I might need to view but doesn't need to on the spot linked other
items or parts of projects this database only backs up when
information is added to the archive. This information though can be
found rapidly doing a Spotlight search and if Spotlight finds what I'm
looking for and its in the archive it just tells me and so I switch
identities.
There are programmers who are not so impressed with Microsoft's
monolithic database. It was actually the fellow that builds
SuperDuper! Who alerted me to this architectural schema of Entourage
ages ago and the downsides of it and this is why I implemented the
above approach which has served me well both in ENT04 and especially
08 (simply because 08 has a number of issues but for me primarily
around sync services which leads to too many problems and eventually
corruption).
Thanks for the reference. I see no reason, should you implement a
strategy wherein if you reduce the size of your DB that you can't
effectively use Time Machine and in fact if you use any other type of
backup system such as Retrospect or Data Backup these will work more
efficiently if you keep a smaller DB. Further, DB's of this size are
just generally more prone to corruption (again, if you phone Microsoft
tech support and tell them you are wondering whether its safe to have
a DB of this size, depending on the level of experience of the rep
they will definitely recommend against this (I am finding Microsoft is
being, at least with me, more candid around the issues with Entourage
and thus more forthcoming which doesn't resolve the problems but at
least I'm not sitting here wondering what's going on)). Finally, the
mvps knowledge base is useful but bear in mind this is not supported
by Microsoft. I referenced this at least once and was clearly told
they support nothing referenced to this but that also goes with
anything say at Macfixit etc. So, one of the things I have expressed,
on many occasions, to Microsoft is they really need a good online
support system on Mactopia in terms of both a proper Knowledge Base
and a moderated forum similar to the method almost all software
vendors use e.g. Apple, MacFixit, Markspace etc etc. They have
actually told me that I can always use
www.microsoft.com/support and I
then said there's nothing Mac there (OH!). So to be a bit political,
no wonder Microsoft, for the first time, is being hit financially and
I don't think its all to do with the financial crisis but that they
don't listen (they, I would say, are really desparate to get Windows 7
out the door and are happy the tech reviewers are spending a lot of
time discussing their next version of Windows and not so much on Vista
(a slight disaster) ((see CNET etc)))). So I feel sorry for the poor
people who are being layed off due to management's blunders and you
don't have to look far to see how management can ruin a company (e.g.
Nortel (bankruptcy), Palm (almost defunct) etc.)).