It's likely that if you've been using Outlook to archive your emails, by the time you get to the point where you're ready to  use a dedicated email archiving product such as MailStore, you'll have a number of PST archive files knocking about, and quite possibly in a variety of locations. There are a long list of reasons why we recommend against archiving to PST (which you can read all about in another post), but in this article I'm going to focus on what to do if you have gone down that route, and show you how to upload and centralise multiple PST archives in one go rather than one at a time.

If you've used Achab's Archive Server (ASM) software in the past and upgraded to MailStore, it's highly likely you'll be wanting to bring across that historic archived data to the new platform. There are two ways you can go about importing an external ASM archive to MailStore - either directly as files, or, via your MDaemon email server. One of the limitations of importing directly into MailStore is that mail can't be sorted on a per-user basis and instead the archive will have to reside under a single MailStore user account which you delegate access to via MailStore's permissions system. It's for this reason that we tend to recommend the second option and utilise the MDaemon server as an intermediary for MailStore to collect the old archive data from.

Our Aussie friends over at BackupAssist developers Cortex IT have recently released two excellent short videos showing the best practices for configuring the BackupAssist user identity. I often come across issues relating to rights associated with BackupAssist jobs. The BackupAssist user identity is key to correctly assigning these rights, so if you are using BackupAssist to back up a Windows Server we these are definitely worth a watch.

Creating Backup User Identities with BackupAssist

[youtube http://www.youtube.com/watch?v=-gcVOHF6tZY?feature=player_embedded&w=640&h=360]