When your Exchange data becomes inaccessible due to unfortunate events like Server crashes or disasters, then you will have to rely on the last backup taken. Exchange backups (if not that old) act as a savior for the administrators. So, we will discuss how Exchange mailboxes can be backed up.

How to backup Exchange mailboxes?

Administrators can back up all the Exchange data using manual ways or professional tools. While talking about manual ways, the most popular one is the backup using PowerShell commands (works for Exchange Server versions 2016, 2013 and 2010).

Before writing the steps to execute the process, let us see some of its advantages.

Absolutely free of cost

Allows single/bulk mailbox migration

Availability of data filters

Adept for brick-level backups

The article tells how to export Exchange mailboxes backup to PST file manually using PowerShell commands. It includes all the steps in detail. Also, the users get information about an alternative way for backup (by third-party software).

PowerShell commands to export mailboxes (for Exchange 2016, 2013, 2010)

As we have mentioned, both single and multiple Exchange mailboxes can be backed up with PowerShell commands. So, we are going to discuss them one by one.

But, before that, the necessary prerequisites must be met.

A shared folder must be taken as the destination location exporting mailboxes

The user must have Mailbox Import Export permissions. This can be done by executing following cmdlet – “New-ManagementRoleAssignment -Role “Mailbox Import Export” -User < user name or alias >”

PowerShell cmdlets to export single mailbox

Let us directly see the syntax for exporting a single Exchange mailbox to PST:

“New-MailboxExportRequest -Mailbox < user >” -FilePath \\<server FQDN >\ < shared folder name >\ < PST name >.pst”

In the above syntax, File Path defines network share path of PST file where data is to be exported. And Mailbox refers to the mailbox name.

Filter: Filters allow to export mailbox data with a filter. E.g.: Export items before a specific date (01/05/2018) and emails starting from a particular word or letters (re).

“New-MailboxExportRequest -Mailbox < user > -ContentFilter {(Received -lt ’01/05/2018′) -and (Subject –like ‘re*’)} -FilePath \\< server FQDN >\ < shared folder name >\ < PST name >.pst”

Export specific folder like Inbox, sent items: The syntax to move only specific folders (like Inbox and SentItems) is given below:

“New-MailboxExportRequest -IncludeFolders “#Inbox#/*”,”#SentItems#” -Mailbox < user > -FilePath \\ < server FQDN >\ < shared folder name >\ < PST name >.pst”

PowerShell cmdlets to export multiple mailboxes

As mentioned earlier, pre-requisites for this method are also same as that for exporting single mailbox.

After fulfilling required conditions, execute the following cmdlet.

$AllMailboxes|%{$_|New-MailboxExportRequest -FilePath \\ < server FQDN >\< shared folder name >\$($_.Alias).pst}

As understood, this cmdlet is for exporting all mailboxes to PST file. Just like in single mailbox migration method, you can migrate mailboxes with additional parameters using respective cmdlets.

The manual method seems easy but in actual, it has some minus points as well.

Requires good technical expertise

Lacks Preview facility for users

No guarantee of data security

Not feasible for corrupt files

Chances for manual errors

No scheduling facility available

No easy-to-read reports

So, it is hard to rely singly on this PowerShell method to export Exchange backup files to PST.

Try complete solution – Kernel for Exchange Server

If you face any issues mentioned above and fail to export Exchange mailboxes to PST, do not worry. There is a complete solution for Exchange data backup and recovery – EDB to PST Converter tool. Some plus points of the tool are:

Backs up or recovers corrupt or healthy Exchange data

Simple user-interface for clean backup, recovery & migration

Shows Preview of each mailbox item before migration

Includes filters like date range and item type

Foolproof migration without affecting data integrity

Saves data to PST and other destinations (like Office 365)

Conclusion

The use of PowerShell commands to export, and backup mailbox data to Outlook PST file has many pros and cons. For avoiding the issues related to this cmdlets method, an efficient and simple Exchange Recovery tool is available.