Tuesday, December 20, 2011

New in Exchange 2010 Backup and Restore

What’s New in Exchange 2010 Backup and Restore

Exchange 2010 introduces several important changes that might affect your Exchange-compatible backup and restore applications, including the following:

• The maximum number of databases that can be mounted on a single Exchange 2010 server has been increased to from 50 to 100.
• Configuration settings for Exchange server databases are now stored in Active Directory Domain Services (AD DS).
• Database mobility features, including Database Availability Groups (DAGs), provide more flexible and more reliable database replication. For databases in a DAG that has two or more healthy copies, the database consistency checking step can even be skipped.
• Improved internal database integrity checking reduces the likelihood that any database corruption will be included in backup images. This helps reduce the need to take a database offline to perform consistency checking by using the CHKSGFILES API or the ESEUTIL application.

Backup and Restore Technologies and Features Removed from Exchange 2010

The following Exchange 2007 technologies and features are no longer available or supported in Exchange 2010:

• Streaming database backup and restore.
• Storage Groups. Each Exchange store database is managed separately in Exchange 2010.
• The Exchange Recovery Storage Group. This has been replaced by the Exchange Recovery database.
• Single-Copy Clusters (SCC).
• Local Continuous Replication (LCR).

Development Technologies Removed from Exchange 2010

The following technologies were removed from Exchange 2007:

• Exchange providers for Windows Management Instrumentation (WMI)
• Collaboration Data Objects for Exchange Management (CDOEXM)
• Collaboration Data Objects for Exchange Workflow (CDOWF)
• Exchange Web Forms
• At Functions
• DAPI.DLL

The following technologies were removed from Exchange 2010:

• Exchange OLE DB Provider (ExOLEDB)
• Exchange store Event Sinks
• World Wide Web Distributed Authoring and Versioning (WebDAV)
• CDO 3.0 (CDOEx)
• Item-level permissions
• Exchange Store custom item types

Changes to Backup and Restore in Exchange 2010

Microsoft Exchange Server 2010 introduces new technologies and features in many areas, and removes other important storage features. To implement Exchange 2010–compatible backup and restore applications, you may need to adjust your application to accommodate the changes described in this topic.

Exchange Storage Groups Removed

Exchange 2010 no longer includes the concept of storage groups. In earlier versions of Exchange, one or more Exchange store databases can be grouped into a storage group, which can then be managed as a unit. However, storage groups complicate many high-availability scenarios, and make single-database restores more complex.

Exchange 2010–compatible backup and restore applications that work with the Windows Volume Shadow Copy Service (VSS) no longer provide storage group identifiers in the VSS backup component paths.

Recovery Storage Group Replaced with Recovery Database

Because storage groups were removed from Exchange Server 2010, the recovery storage group no longer exists. Instead, if your application needs to restore, recover, and mount an Exchange database to a different location or server, it will use a recovery database. The recovery database is not tied to any original server or database. Each Exchange 2010 server can have no more than one mounted recovery database. There can be multiple recovery databases, but only one can be mounted at a time.

Streaming Backups Not Supported

Exchange 2010 does not support streaming-style backups. In versions of Exchange earlier than Exchange 2010, backup applications use the ESEBCLI2 interface to perform streaming backups.
Number of Databases per Server Increased

In Exchange 2007, each server can mount 50 databases configured in up to 50 storage groups. In Exchange 2010, each Exchange server can connect to a maximum of 100 Exchange databases, and storage groups do not exist. Although each Exchange server can have a maximum of 100 databases mounted at one time, that limit does not apply to the total number of database objects that are stored in Active Directory Domain Services (AD DS). Each Exchange organization can have any number of database objects in AD DS.

For backup and restore applications, the maximum of 100 mounted databases for an Exchange organization includes up to one mounted recovery database. There is no distinction between normal and recovery databases in this maximum number.

Database Mobility and Availability Groups Added

Exchange 2010 servers can be configured to perform even more flexible database replication than Exchange 2007 servers. Each Exchange 2010 database can be replicated to up to 16 Exchange servers, which can be geographically distributed to improve availability and resilience. The group of servers that replicate an Exchange database is called a Database Availability Group (DAG).

Exchange 2010 DAGs can also improve the reliability and performance of backup applications. Backing up a replicated, inactive copy of the database prevents the active Master database from being affected during the VSS snapshot.

Because all the servers in a DAG have copies of the database log files, applications can restore and recover databases by using backup components taken from different servers. When restoring a DAG database from backups, all active and passive copies must be restored using the same data.

Storage Configuration in Active Directory Changed

The arrangement of organization-level Exchange server and storage configuration information, which is stored in AD DS, has changed.

In versions of Exchange earlier than Exchange 2010, database and storage group configuration data is stored as children of the server object.

Because Exchange 2010 databases are no longer tied to a particular server, database configuration information is stored at the same hierarchy level as the Exchange server configuration objects. Similarly, DAG configuration is stored at the same level as the organization’s Exchange server configuration objects. Both forward links and back links exist between the database copies, the DAG they are a part of, and servers that participate in the DAG.

Storage Configuration Commands Changed

To accommodate the many storage architecture changes in Exchange 2010, the Windows PowerShell commands for setting and retrieving storage configuration have changed significantly.

CHKSGFILES DLL Now 64-bit only

Exchange 2010 is only available in 64-bit implementation. 32-bit implementations of the server are not available. Similarly, the CHKSGFILES DLL is available only as a 64-bit unmanaged DLL.

Single Copy Clustering Is Not Available

Exchange 2010 does not include support for Single Copy Clustering (SCC). If your Exchange 2007–compatible backup and restore application relies on SCC, you will need to modify the application to be compatible with Exchange 2010.

Log File Size Standardized

Exchange database log files are now each 1 MB in size. In earlier versions of Exchange, log files varied in size.





4 comments:

  1. Good share,you article very great, very usefull for us…thank you

    domain service

    ReplyDelete
    Replies
    1. Checkout one of the best Exchange Server EDB Recovery software, which i ever used :

      http://www.recoverydeletedfiles.com/exchange-server-edb-recovery.html

      Thanks

      Delete
  2. Thanks Dinesh for sharing this helpful post!

    Taking regular backup of Exchange server data is essential for data security. A backup is the best method against data loss, it allows the users to restore original data. Sometime, when data corruption occurs in Exchange server backup file, the file containing that data may become useless, and when you try to restore it the Exchange server will generate an error. Unfortunately there is no built-in utility to repair corrupt Exchange backup file. In this case, only a third party Exchange BKF recovery software may help to recover damaged data. One such tool is Stellar Phoenix Exchange BKF recovery that effectively repairs the damaged Exchange .bkf file and recovers all data (.edb, .stm, and .log files) stored in it.

    Regards
    Brown Wise

    ReplyDelete