Restore Mailbox Scenarios

Restore Mailbox Scenarios
In this tip we will examine the different restore mailbox scenarios E12 will support.


General Assumptions on Restore-Mailbox Scenarios:

Servers are in a highly connected network.
Servers are part of a Single Forest or Resource Forests: Mailbox content can only be exported to mailboxes within the same forest. The NT accounts associated with the mailbox can be in an external forest (as in a Resource Forest Scenario), but mailbox content will not be able to be exported to servers in different forests.
These are the supported Source Servers:
1. Exchange 2000 SP3 (or later)
2. Exchange 2003 SP2 (or later)
3. Exchange 2007
These are the supported Target Servers:
1. Exchange 2007
Recipient Admin rights are required
Restore-Mailbox can only use disconnected mailboxes as source of content and connected mailboxes as the target

Recovering old mailbox of an existing employee

Customer Setting:

Restore-Mailbox can also recover data of users that have an active mailbox in the Exchange Organization. The way to do this is to recover the backup to the RSG database, and from there restore the user’s mailbox (or part of it using filtering) by simply specifying the ID for the mailbox to be restored. In this case, source and target should be the same so there is no need to use RSGMailbox.


Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.


Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics


Scenario 1: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:
MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'

Scenario 2: Restore mailbox content to active mailbox based on User ID and date rangeAn administrator wants to restore email content sent between 02/02/05 and 02/05/05 from a RSG mailbox into a currently active mailbox:


MONAD Syntax – restore all RSG content sent between 02/02/05 and 02/05/05 of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:
MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database' -StartDate ‘02/02/05’ –EndDate ‘02/05/05’


Scenario 3: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:


MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox


Scenario 4: Restore mailbox content to folder based on active User ID
An administrator wants to restore email content from a RSG mailbox into a folder inside a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:

MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’

Scenario 5: Restore mailbox content to folder based on active User ID and date range
An administrator wants to restore email content sent between 02/02/05 and 02/05/05 from a RSG mailbox into a folder inside a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:
MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’ -StartDate ‘02/02/05’ –EndDate ‘02/05/05’

Customer Setting:

After an employee leaves a company, even though his active mailbox might be disabled or deleted, admins can still recover data from previous backups through the RSG. The way to do this is to recover the backup to the RSG database, and from there restore the user’s mailbox (or part of it using filtering) by specifying the RSGMailbox (points to ex-employee’s mailbox) and a target folder in an admin mailbox.


Customer Goal:
Ability to recover data from RSG mailboxes that do not have an active mailbox counterpart. Data is to be recovered to a folder inside another user’s active mailbox.

Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics


Scenario 6: Restore mailbox content to folder inside an active mailbox based on RSG User ID
An administrator wants to restore email content from a RSG mailbox into a folder inside a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:

MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’

Scenario 7: Restore mailbox content to folder inside an active mailbox based on RSG User ID and date range
An administrator wants to restore email content sent between 02/02/05 and 02/05/05from a RSG mailbox into a folder inside a currently active mailbox:


MONAD Syntax – restore all RSG content sent between 02/02/05 and 02/05/05 of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox
MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’ -StartDate ‘02/02/05’ –EndDate ‘02/05/05’

Scenario 8: Restore mailbox content from all mailboxes in a Database to a folder inside an active mailbox
An administrator wants to restore email content from all mailboxes in the RSG to a folder inside an active mailbox:

MONAD Syntax – restore all RSG mailboxes to a folder called DatabaseBackup inside mailbox testE12mbx2:


MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox -id 'testE12mbx2' -TargetFolder ‘DatabaseBackup’

Customer Setting:

Hardware malfunction resulted in corrupt databases which cannot be brought online in their current state. End users rely on timely email communication for business continuity. Need to enable email functionality ASAP.
If the current server and disk is available and functioning properly, Exchange administrator can enable dial tone services to all the users by moving the corrupt files to a different location and mounting an empty database online in its original location.
While the dial tone is in production, admin will recover original database from backup in a separate location. After this is complete, the production server switches to the backup database and the dial tone database is copied to the RSG. Then, the dial tone content is merged back into the new production database by using restore-mailbox so users do not lose any content.


Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.


Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics


Scenario 9: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:

MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'


Scenario 10: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:


MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox


Customer Setting:

Hardware failures or some corruption resulted in Exchange server not functioning properly. While OS/Exchange Administrators investigate the issue, end users need access to email.
Exchange does not allow moving mailboxes to a different server if the original server is not available since move is associated with moving a mailbox with its associated full content. In order to provide dial tone functionality in this case, Admin would use a clean database in a separate server, and use the move-mailbox configuration only option to change the AD settings so the mailboxes would point to this new database. While the dial tone is in production, admin will recover original database from backup in a separate location (if the original server was fixed, that can be used as the location for the backup). After this is complete, the production server switches to the backup database and the dial tone database is copied to the RSG. Then, the dial tone content is merged back into the new production database by using restore-mailbox so users do not lose any content.


Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.


Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics


Scenario 11: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:


MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:

MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'


Scenario 12: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:


MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox

Microsoft Exchange Server 2007 Service Pack 2 Help

Brief Description
This download contains a standalone version of Microsoft Exchange Server 2007 SP2 Help.

Overview
The Exchange Server 2007 SP2 Help can help you in the day-to-day administration of Exchange. Use this information to guide you through Exchange Server 2007 SP2 features, tasks, and administration procedures.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=85c5ef71-6a1f-4eb0-9ff3-3feee6057e96

Using Exchange Server Database Utilities (eseutil.exe) in Exchange 2003 / 2007 (Part 2)

Eseutil work with ESE db files and logs. You can use to verify, modify and repair Exch db files.
When db is corrupt you must restore from backup first because Eseutil repair can result in data loss. Eseutil is located in
:\Program Files\Microsoft\Exchange server\Bin

You can use in Mailbox, Edge and Hub roles
You mustt use the same version of eseutil as version of Exch you are working. The Exch07 version does not support working with *.stm files.
You can only run one instance for eseutil. Eseutil modes:
- Defrag /D
Defrag offline but leaves the new db in temp location and reduces the size
- Repair /P
Repair a corrupt offline db discarding pages that cannot be fixed
- Restore /C
Displays restore log files (restore.env) and control hard recovery after restoration from
online backups
- Recovery /R
Replay logs or rolls them forward to restore a db to internall consistency or to bring
an older copy of a db up to date
- Integrity /G
Verifies the page level and ESE level logical integrity of db.
- File Dump /M
Displays headers of database files, transaction log files and checkpoints. Also display
database pagre header information and db space allocation
- Checksum /K
Verifies checksum on all pages in he db, logs and checkpoints
- Copy File /Y
Perform a fast copy of very large files

Como usar esutil.exe en Exchange 2003 / 2007 (Parte 1)

Vamos a ver los diferentes usos de Eseutil.exe y a dar información al respecto:


- Uso del switch /K para detectar daños en las cabezeras de ficheros.

File header damage puede ocurrir in databases, log files, patch files, o ficheros de checkpoint.

C:\Program Files\ExchSrvr\Bin\eseutil /k "c:\program files\exchsrvr\mdbdata\priv1.edb"


Verificar la integridad checksum de los transaction logs.
Todas las bases de datos del Storage Group deben estár desmontadas:

c:\Exchsrvr\bin>eseutil /k c:\exchsrvr\mdbdata\e00.log

How To: Use the Eseutil Utility to Detect File Header Damage in Exchange 2003
http://support.microsoft.com/kb/825088/en-us

Comprobar que todos los logs de una secuencia son correctos.

c:\Exchsrvr\bin>eseutil /ml Enn

Comprobar Estado de Cierre (Clean Shutdown o Dirty Shutdown) y Log_required (Log requerido para arrancar)

c:\Exchsrvr\bin>eseutil /MH D:/msdbdata/priv1.edb

En caso que uno de los ficheros esté corrupto:

1) Usar siempre un backup para restaurar
2) En caso de no disponer de backup ejecutar:
2.1) Primero hacer un backup de las bases de datos publicas y privadas y logs
copiandolos a otra carpeta con los servicios de exchange parados

2.2) Para un EDB corrupto

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.edb

2.3 Para un STM corrupto:

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.stm

2.4 Para reparar en una localización temporal (problemas de espacio en el disco (110%)):

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.edb /t z:/eseutiltemporal.edb


Bibliografia:

Exchange Command-Line Parameters for the Isinteg.exe Tool
http://support.microsoft.com/default.aspx?scid=kb;en-us;301460

How to re-create STM File in Exchange 2000/2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;555146

XADM: Exchange 2000 Server Eseutil Command Line Switches
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317014

How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;248122

XADM: Exchange and Antivirus Software
http://support.microsoft.com/default.aspx?scid=kb;[LN];328841

XADM: Ramifications of Running the ESEUTIL /P or EDBUTIL /D /R Command
http://support.microsoft.com/?id=259851

Preview: Exchange Server 2003 Disaster Recovery Planning Guide
http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBEA2-28DD-409A-8368-F9914E993B28&displaylang=en

Como restaurar un item individual de Exchange 2007 con DPM

DPM 2007 SP1 -- how to do individual item restore for Exchange

Lectura Obligada para esta semana (21-11-2008)

Extraido del artículo de Chris Avis , os dejo estos interesantes artículos.


Infrastructure Development, Operations & Maintenance

Active Directory Migration Tool v3.0

Brief Description

The Active Directory Migration Tool version 3 (ADMT v3) provides an integrated toolset to facilitate migration and restructuring tasks in an Active Directory infrastructure.
Overview
The Active Directory Migration Tool version 3 (ADMT v3) simplifies the process of restructuring your operating environment to meet the needs of your organization. You can use ADMT v3 to migrate users, groups, and computers from Microsoft® Windows NT® 4.0 domains to Active Directory® directory service domains; between Active Directory domains in different forests (interforest migration); and between Active Directory domains in the same forest (intraforest migration). ADMT v3 also performs security translation from Windows NT 4.0 domains to Active Directory domains and between Active Directory domains in different forests.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6f86937b-533a-466d-a8e8-aff85ad3d212&DisplayLang=en

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467)

Brief Description

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467)

Overview

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers. For a list of changes that are included in this update rollup, see KB953467. This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM). For a list of update rollups applicable to Exchange Server 2007 RTM, refer to the section Update rollups for Exchange Server 2007 RTM in the Knowledge Base article KB937052. This is a cumulative update rollup and replaces the following:
KB945684 Update Rollup 1 for Exchange Server 2007 Service Pack 1 (KB945684)
KB948016 Update Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016)
KB949870 Update Rollup 3 for Exchange Server 2007 Service Pack 1 (KB949870)
KB952580 Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580)
http://www.microsoft.com/downloads/details.aspx?FamilyID=652ed33a-11a1-459c-8ffe-90b9cbfe7903&DisplayLang=en

Microsoft .NET Framework 3.5 Service Pack 1

Brief Description

Microsoft .NET Framework 3.5 Service Pack 1 is a full cumulative update that contains many new features building incrementally upon .NET Framework 2.0, 3.0, 3.5, and includes cumulative servicing updates to the .NET Framework 2.0 and .NET Framework 3.0 subcomponents.
Overview
.NET Framework version 3.5 Service Pack 1 provides the following new features and improvements:
ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data driven development without writing code, and a new addition to ASP.NET AJAX that provides support for managing browser history (back button support). For more information, see What’s New in ASP.NET and Web Development.
Core improvements to the CLR (common language runtime) that include better layout of .NET Framework native images, opting out of strong-name verification for fully trusted assemblies, improved application startup performance, better generated code that improves end-to-end application execution time, and opting managed code to run in ASLR (Address Space Layout Randomization) mode if supported by the operating system. Additionally, managed applications that are opened from network shares have the same behavior as native applications by running with full trust.
Performance improvements to WPF (Windows Presentation Foundation), including a faster startup time and improved performance for Bitmap effects. Additional functionality for WPF includes better support for line of business applications, native splash screen support, DirectX pixel shader support, and the new WebBrowser control.
ClickOnce application publishers can decide to opt out of signing and hashing as appropriate for their scenarios, developers can programmatically install ClickOnce applications that display a customized branding, and ClickOnce error dialog boxes support links to application-specific support sites on the Web.
The Entity Framework is an evolution of the existing suite of ADO.NET data access technologies. The Entity Framework enables developers to program against relational databases in according to application-specific domain models instead of the underlying database models. For more information, see Getting Started with the Entity Framework. The Entity Framework introduces some additional features, including support for new SQL Server 2008 types, default graph serialization of Entities, and the Entity Data Source. This release of the Entity Framework supports the new date and file stream capabilities in SQL Server 2008. The graph serialization work helps developers who want to build Windows Communication Foundation (WCF) services that model full graphs as data contracts. The Entity Data Source provides a traditional data source experience for ASP.NET Web application builders who want to work with the Entity Framework.
LINQ to SQL includes new support for the new date and file stream capabilities in SQL Server 2008.
The ADO.NET Data Services Framework consists of a combination of patterns and libraries, which enable data to be exposed as a flexible REST (Representational State Transfer)-based data service that can be consumed by Web clients in a corporate network or across the Internet. The ADO.NET Data Services Framework makes data service creation over any data source. A conceptual view model of the underlying storage schema can easily be exposed through rich integration with the ADO.NET Entity Framework. Services created by using the ADO.NET Data Services Framework, and also compatible Windows Live (dev.live.com) services, can be easily accessed from any platform. For client applications that are running on Microsoft platforms, a set of client libraries are provided to make interaction with data services simple. For example, .NET Framework-based clients can use LINQ to query data services and a simple .NET Framework object layer to update data in the service.
Windows Communication Foundation now makes the DataContract Serializer easier to use by providing improved interoperability support, enhancing the debugging experience in partial trust scenarios, and extending syndication protocol support for wider usage in Web 2.0 applications.
The .NET Framework Data Provider for SQL Server (SqlClient) adds new support for file stream and sparse column capabilities in SQL Server 2008.
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&DisplayLang=en

Visual Round Trip Analyzer

Brief Description

Tool to view web page performance Web page performance visualizer and analyzer

Overview

The Visual Round Trip Analyzer tool helps web developers and testers visualize the download of their page, identify best practices and changes that improve web performance. The network Round-Trip between the client and server(s) is the single biggest impact to web page performance – much greater than server response time. VRTA examines the communications protocol, identifying the causes of excessive round-trips, and recommending solutions. Performance engineers, testers, developers, operations personnel should use VRTA to conduct their web performance analysis.
http://www.microsoft.com/downloads/details.aspx?FamilyID=119f3477-dced-41e3-a0e7-d8b5cae893a3&DisplayLang=en

Security, Policy & Compliance

Microsoft® Forefront™ codename "Stirling" Beta

Brief Description

An integrated security system that is easier to manage and control Microsoft® Forefront™ codename "Stirling" is an integrated security system that delivers comprehensive, coordinated protection across endpoints, messaging and collaboration servers and the network edge that is easier to manage and control.
Overview
Microsoft® Forefront™ codename “Stirling” is an integrated security system that delivers comprehensive, coordinated protection across endpoints, messaging and collaboration servers and the network edge that is easier to manage and control. By delivering simplified management and providing critical visibility into threats, vulnerabilities, and configuration risks, Forefront codename "Stirling" helps reduce costs and achieve greater insight into the enterprise security state. At release, “Stirling” will include:
 A central management console and dashboard for security configuration and enterprisewide visibility.
 The next-generation versions of Forefront products: the next generation of Forefront Client Security, Forefront Security for Exchange Server, Forefront Security for SharePoint and the Internet Security & Acceleration Server (to be renamed the Forefront Threat Management Gateway).
 Dynamic Response, an innovative Microsoft technology built into each component of "Stirling" that allows the entire system to share and use security information to dynamically respond to threats across multiple layers of the organization.
http://www.microsoft.com/downloads/details.aspx?FamilyID=65bd5f8a-d94c-457a-9f88-2046597130e1&DisplayLang=en