Showing posts with label database. Show all posts
Showing posts with label database. Show all posts

Monday, July 4, 2016

Where is the Outlook 2016 for Mac Database?

Outlook 2016 for Mac stores its database in:

~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/

If the application does a database rebuild, it will make a backup copy of the database and place it into the above folder.

Despite what Microsoft says, Office 2016 is just as prone to database problems as Outlook 2011.  The difference is that in Outlook 2016 there is no manual way to do a database backup- the app does them automatically. 

We have found that many users that have been moved from Office 2011 to 2016 are prompted to repair the Outlook database.  In some cases it happened so often that we had to move them back to Office 2011.

In fact, just as I was writing this my Outlook 2016 did a rebuild.  This was after a completely fresh install two days ago.  Thankfully I kept Outlook 2011; it is solid as a rock.

Wednesday, March 10, 2010

Entourage database and Time Machine

Time Machine and the Entourage database don’t play well together.  The problem most people have is that their Entourage profile is a massive, monolithic database and even opening Entourage causes Time Machine to back up the entire database not just the changes.  Normally the advice is to manually copy the user profile every once and a while and not let Time Machine back it up unless you have an infinite amount of disk space.

You can also have problems because even if all your Office apps are closed the database daemon is still running and this can lead to corrupt database backups.  Before you backup the Office database you can run this command:

tell application "Microsoft Database Daemon" to quit

And after you are done you can do restart or run this command:

tell application "Microsoft Database Daemon" to launch

Saturday, March 7, 2009

BEUTILITY (BackupExec Utility)

To migrate the BackupExec databases after the server has been migrated to a new domain:

Make sure you change all the BackupExc services so that they launch using a local service account not a domain or local admin account.  DO THIS FIRST and then run the beutility.exe app.

The beutility.exe file is located in the in the same folder as the main BE application. 

Launch beutility.exe.  The option is not so easy to find.. You click on the List of servers, right click on the server name and select "update configuration to reflect new media server name", then fill in the new domain and server name and the old domain and server name.