Can't backup my Database in Entourage

[mike]

Has anyone ever run into this problem:

I can't backup my Database in Entourage. When I run a backup script
with Retrospect I get this error message...

Can't read file "Database", error -54 (file is busy/locked), path:
"Documents/Microsoft User Data/Office 2004 Identities/Main
Identity/Database".

But it's not actually busy or locked!

I can't copy it to another hard drive either, even by just trying to
drag it to another hard drive. The only way I can get a copy of it to
another hard drive is to make a copy of it on the same hard drive it
resides on, copying it outside of the Main Identity folder, then I can
save that copy of it to another hard drive. This is a pain in the butt
since it isn't possible to make this automated in Retrospect.

Any solutions?!!

Thanks in advance.

Art

 

[deathdruid]

Has anyone ever run into this problem:

I can't backup my Database in Entourage. When I run a backup script
with Retrospect I get this error message...

Can't read file "Database", error -54 (file is busy/locked), path:
"Documents/Microsoft User Data/Office 2004 Identities/Main
Identity/Database".

But it's not actually busy or locked!

How do you know for sure? Did you try using:

# lsof | grep Identity

in the Terminal to find out what application has the file open?

-Rahul

 

[H Beinert]

Has anyone ever run into this problem:

I can't backup my Database in Entourage. When I run a backup script
with Retrospect I get this error message...

Can't read file "Database", error -54 (file is busy/locked), path:
"Documents/Microsoft User Data/Office 2004 Identities/Main
Identity/Database".

You may find that there are other processes which still have the database
open, specifically the "Microsoft Database Daemon". Entourage uses the
Daemon as a centralized DB engine. If you use Retrospect's facility to run
an Applescript prior to a backup, both Entourage and the Daemon can be
shutdown, albeit with some annoying caveats.

You might search this newsgroup for references to the "Database Daemon".
This reference should get you started, however:
http://groups.google.com/group/micr...read/thread/d768658d13c7d73e/62d16988e230d0aa

HTH,
HB.

 

[Barry Wainwright [MVP]]

You may find that there are other processes which still have the database
open, specifically the "Microsoft Database Daemon". Entourage uses the
Daemon as a centralized DB engine. If you use Retrospect's facility to run
an Applescript prior to a backup, both Entourage and the Daemon can be
shutdown, albeit with some annoying caveats.

You might search this newsgroup for references to the "Database Daemon".
This reference should get you started, however:
http://groups.google.com/group/microsoft.public.mac.office.entourage/browse_th
read/thread/d768658d13c7d73e/62d16988e230d0aa

HTH,
HB.

If you are going to shut down the daemon, you also need to shut down word,
excel, powerpoint and messenger - all office apps access the database
through the daemon.

 

[H Beinert]

If you are going to shut down the daemon, you also need to shut down word,
excel, powerpoint and messenger - all office apps access the database
through the daemon.

Thank you for the clarification, Barry. Is there a better way to ensure an
uncorrupted backup than taking shutting down all MS Office apps? Is
there some procedure for taking reliable backups which is less intrusive?

Thanks,
HB.

 

[Barry Wainwright [MVP]]

Thank you for the clarification, Barry. Is there a better way to ensure an
uncorrupted backup than taking shutting down all MS Office apps? Is
there some procedure for taking reliable backups which is less intrusive?

Thanks,
HB.

No. If you want to be certain, you need to close the daemon, which means you
must close the other office apps (they are likely to freeze or crash if the
daemon is quit while they are still running).

If the daemon has not written out it's file buffers when you copy the
database, you may copy it in an ambiguous condition, leading to corruption.
Quitting the daemon makes sure all buffers are written out and the database
is in a good condition for copying.