ACRONIS RECOVERY - FOR MICROSOFT EXCHANGE Instalační příručka stáhnout pdf (Strana 21)

5.2 What data items can be backed up and what backup

types are used?

While creating a backup plan, you can select either the Microsoft Exchange Information Store or the

Microsoft Exchange Mailboxes backup type.

Microsoft Exchange Information store

This data type lets you select the following items to back up:

 The entire information store.

 Individual databases (for Exchange 2010 only).

 Individual storage groups (for Exchange 2003/2007 only).

When you select any of the above mentioned items, the software will perform a database backup.

The dismounted databases are skipped during backup. The backup task gets the "Succeeded with

warning" result, if the task backed up at least one database but skipped others because they were

dismounted. The backup task gets the "Failed" result, if the task was completed but skipped all of the

databases because they were all dismounted.

During database backups, Agent for Exchange automatically performs consistency check of database

files. It verifies the page-level integrity of the databases being backed up and validates the checksums

of all database pages and log files. Databases with a checksum mismatch or file header damage are

skipped during the backup.

Database backup types

 Full. A regular full database backup stores the selected storage groups or databases along with

transaction log files and Exchange-related information from Active Directory. After a full backup

is created, transaction log files are truncated (p. 58). A full backup is self-sufficient; that is, you do

not need access to any other backup to recover the data from a full backup. The database

backups are the basis for disaster recovery scenarios when it is necessary to recover lost or

corrupted databases, storage groups, or entire information store. Granular recovery from

database backups allows for restoring mailboxes, public folders, e-mails, contacts, calendar

events, journal entries, notes and more.

Additionally, full backups can be created by using one of the following methods:

 Express full backup (p. 26). This method allows creating creating full database backups in

deduplicating vaults. Although regular data deduplication can be used full database backups,

we recommend using the Express full backup method to achieve maximum deduplication

effect.

 Copy-only backup (p. 30). This method allows creating full database backups without

truncating the transaction log files.

 Transaction log. A transaction log backup stores the transaction log files along with checkpoint

files and other files required for recovery. After a backup is created, transaction log files are

truncated. At first, a regular full backup is created. By having full and transaction log backups,

you can recover the data to a custom point in time. From a recovery perspective, transaction log

backups are similar to incremental backups. To recover from a transaction log backup, each

transaction log backup since the last full backup and the full backup is required. A long chain of

transaction log files may significantly increase recovery time.

1 2 ... 16 17 18 19 20 21 22 23 24 25 26 ... 58 59

Žádné komentáře

ACRONIS RECOVERY - FOR MICROSOFT EXCHANGE Instalační příručka Strana 21