sepusa.com | ONE network-wide backup solution

(C)SEP AG

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

1 Introduction
2 System Requirements
3 Configuration of a MS Exchange Online Backup
- 3.1 Configuring the Exchange Server Backup
  - 3.1.1 User and rights management for single maibox backup / Troubleshooting
    - 3.1.1.1 Defaults after installation
    - 3.1.1.2 Manually granting Access
  - 3.1.2 General Task definition
- 3.2 Configuring an Exchange Server DAG Backup
4 Exchange 2010 Restore
5 Exchange 2007 Restore
6 Other Links and Information

Introduction

Beginning with Exchange Server 2007, the VSS Writer "Microsoft Exchange Writer" was incorporated into Exchange and is recommended for use as the backup methodology for all Exchange backup tasks. After Exchange 2010 the ESE API will no longer be supported (see Supported Backup Technologies), this means, of course, that using the VSS Writer "Microsoft Exchange Writer" is required.

System Requirements

SEP sesam Server and SEP sesam Client from Version 4.0.3
Microsoft Exchange Server 2007 or 2010

Configuration of a MS Exchange Online Backup

Beginning with Exchange 2007 there are two types of backups available:

Exchange Server
Exchange Server DAG

The Database Availability Group backup (DAG) makes it possible to replicate from one Exchange Server Database to another server running Exchange 2010.

For an Exchange Backup the following backup types are possible: FULL, DIFF, INC and COPY.
The following content was assigned from "http://technet.microsoft.com/en-us/library/aa996125(EXCHG.65).aspx © 2011 Microsoft. All rights reserved."

Normal (or Full): The normal backup process backs up the directory or Exchange store in its entirety, as well as the log files. To restore from a normal backup, only one normal backup is needed. A normal backup marks the objects it has backed up so that incremental and differential backups have context. This is accomplished by backing up the entire database and all the log files, and then purging the log files.
Copy: The copy backup is the same as a normal backup except no marking takes place to give incremental and differential context. This means that performing an incremental backup after a copy backup is equivalent to performing it before a copy backup. Use a copy backup to get a full backup of the directory or Exchange store without disturbing the state of ongoing incremental or differential backups.
Incremental: An incremental backup backs up the subset of the component that has changed since the last normal or incremental backup. Then it marks these objects as backed up. To restore from incremental backups, each incremental backup since the last normal backup and the normal backup are needed. An incremental backup backs up only the log files, and then purges them.
Differential: A differential backup backs up changes in the directory or Exchange store that have occurred since the last normal backup. To restore from differential backups, one differential backup and one normal backup is required. A differential backup backs up only the log files but does not purge them.

Circular logging

If "circular logging" is activated for exchange databases, backups with type "INC" should not be performed. This leads to damaged VSS Writers!

Configuring the Exchange Server Backup

User and rights management for single maibox backup / Troubleshooting

Defaults after installation

In order to be able to perform an Exchange 2010 or Exchange 2007 single mailbox backup, the SEP sesam Client needs access to the users mailboxes during backup.

This happens by connecting to the Exchange Web Service (EWS).

For this, a special sesam user within the Active Directory is created. This screen shot shows the created user in the Active Directory:

If the default password is changed (recommended) it has to be specified in the Exchange 2010 task options under the additional tab "Exchange Access":

The short handle of the sesam user (<domain>\SS_<random_id>) needs access to each users mailbox. You can check this by opening the Exchange Management Console and opening the users full access:

Manually granting Access

In case the installation routine was not able to succesfully add the rights or the sesam user, there exists a command line tool for doing so.

Connect to your Exchange System as Domain Administrator and open an Command box. Switch to the sesam installation directory like shown in this screenshot:

Granting the access is done with the tool "sbc_es.exe". To get a clean state remove eventually created permissions with the command "sbc_es.exe -permission:remove all":

After cleanup, re-add the permissions with the command "sbc_es.exe -permission:add all"

General Task definition

For the Exchange Client a new Backup Task, using the SEP sesam GUI with the 'Backup Type' - Exchange Server, is created.

This action will backup all local MS-Exchange Information Stores.

Configuring an Exchange Server DAG Backup

For the Exchange Client a new Backup Task, using the SEP sesam GUI with the 'Backup Type' Exchange Server DAG, is created.

Using the Exchange Server DAG backup, all DAG replicated databases, currently existing on the client, will be backed up. It is then possible to move or replicate the data to the corresponding DAG server already running the replicate or mirrored data from the other Exchange Server.

Exchange 2010 Restore

The following restore options are available for Exchange Server:

Exchange Database Restore (Information Store)
Exchange Single Mailbox Restore
Exchange Single Mail Restore
Exchange Database Availability Group Restore

Attention!

For all restore options the whole database is temporarely restored, the corresponding disk capacity must be available.

Exchange Database Restore (Information Store)

Select the desired Restore Task and then select ”complete restore of selected task”.

In the event a data restore is needed, the following options are available:

Restore to a generated RDB, where applicable, and Import into the original Database.

SEP automatically generates a Restore database and from this restore location all information will be reimported into the original database.

Restore to specified RDBs and Import into original database

Pre-defined restore databases can be selected and data will be subsequently restored to the original database.

Restore to RDB’s

Pre-defined restore databases can be selected without subsequent import/restore to the original database.

Exchange Single Mailbox Restore

To perform a Mailbox restore the backup task is selected and the relevant mailbox is selected.

To restore the mailbox, there are four different restore options available:

Restore into a previously created RDB and Import to original database

SEP sesam automatically generates a Restore Database and subsequently restores everything to the original database.

Restore to pre-defined RDBs and Import in original Database

Previously defined Restore Database can be selected and afterwards be restored to the original database.

Restore in RDBs

Previously defined Restore Databases can be selected without subsequent restore to the original Database.

Exchange Single Mail Restore

To restore a single mail to an Exchange Mailbox, setup a restore task and then select the desired mailbox.

For restore, the following options are available:

Restore to a generated RDB and Import to the original Database

SEP sesam automatically creates a restore database and from a restore can be directed to the original Database.

Restore to pre-defined/selected RDBs and Import to the original Database

Previously defined Restore Databases can be selected and subsequently data can be restored to the original Database.

Restore in RDBs

Previously defined Restore Databases can be selected without restoring the data to the original Database.

Exchange 2007 Restore