Running natively on Windows Server 2008 R2 is now supported with the release of Service Pack 3 for Exchange Server 2003 (link). In addition, SP3 adds support for running the Exchange Management Tools on Windows 7. The version of SP3 is 8.03.0083.006 and is available for x86 as well as x64 bits.
To have the ability to recover individual files and folders in a guest virtual machine hosted on Hyper-V RTM / R2, the protection group must specify Disk as the backup media (short term).
The DPM agent only needs to be installed on the physical Hyper-V host. It is not a prerequisite to setup the DPM Agent in each and every VM. Doing so, however, enables the administrator to define separate and complementary backup schedules with added flexibility in recovery, both at the VM (as seen from Hyper-V) and application (child partition’s viewpoint) levels.
Additionally, the Hyper-V server role must be installed on the DPM 2010 Server. This requires Windows Server 2008 RTM / R2, which in any case is the only supported x64 operating system for DPM 2010. It is not sufficient to just install the Hyper-V Manager.
If you deploy SCVMM to manage your virtual infrastructure, navigating to DPM / Protection Group and expanding the <clusterName> on the “Select Group Members” page will present you with the opportunity to pick from a list of virtual machines prefixed with <SCVMM> for backup.
Assuming that you have a clustered VM resource named Exchange, it will read “SCVMM Exchange Resources” below “<clusterName> (Cluster)”. Drill down to “HyperV” and put a check against “Backup Using Child Partition Snapshot\Exchange”. Complete the remaining steps to finalize your backup requirements (backup media, goals, schedule, etc.).
For the reverse procedure (data restore), click on the Recovery tab and move to the Browse tab. On the left hand pane, expand “Recoverable data” and choose the node representing the Active Directory domain name. Instead of the <clusterName> name, you will find “SCVMM Exchange Resources (<clusterNameFQDN>)” along with other protected servers and resources (SQL, SharePoint, etc.).
In order to recover the entire VM - virtual hard disks (vhd), Virtual Machines folders, XML/bin/vsv files, etc. - it is imperative to first select “All Protected HyperV Data” in the tree view (Protected Data) on the left hand side. Be aware that these files do not show up as individual items for selection.
On the list pane to the right, highlight “Backup Using Child Partition Snapshot\Exchange” and locate the desired recovery point, date, time and backup media using the calendar. Click on Recover where you have a choice on the “Recovery Type” page to perform restore using one of the options:
Recover to original instance
Recover as virtual machine to any host
Copy to a network folder
Copy to tape
For restoration of just the associated vhd files of the VM, double click “Backup Using Child Partition Snapshot\Exchange”. You can only pick a single vhd for recovery one at a time. The recovery target in this case is limited to “Copy to a network folder”. Should you attempt to replace the vhds using this approach, VMM may fail to start the VM and complain with the error:
VMM cannot complete the WMI operation on server <clusterNodeNameFQDN> because of error: [MSCluster_Resource.Name=”SCVMM Exchange”] The group or resource is not in the correct state to perform the requested operation.
(The group or resource is not in the correct state to perform the requested operation (0×139F))
To learn more about a cluster and its nodes under DPM, simply hover and pause the mouse over the entity to see the corresponding tool tip:
<clusterName> consists of multiple servers, which may have unclustered resources. Unclustered resources are listed separately under server names. Since this list is sorted alphabetically, server names may appear somewhere else in this tree view.
<clusterNodeName> is part of a cluster. Unclustered resources on this server are listed here. Clustered resources belonging to the same cluster are listed under cluster name separately. Since this list is sorted alphabetically, cluster name may appear somewhere else in this tree view.
Hyper-V R2 in a 2-node Fail-over Cluster with Cluster Shared Volume, CSV*
System Center Virtual Machine Manager 2008 R2, v2.0.4273.0
Data Protection Manager 2010 RTM*
* Windows Server 2008 R2
Es gibt nur wenigen Platz für den Windows Server 2008 R2 Basics Kurs bei EB Zürich, den nächste Woche in Zürich am Montag 31.5.2010 (für 4x) stattfinden wird. Interessern bitte melden Sie sich unverzüglich hier an.
Various network settings on local and remote machines can be configured using the netsh utility shipped in Windows. Run it interactively at the command line or deploy it together with scripts and batch files, netsh provides functionality that are typically exposed in Microsoft Management Console (mmc) snap-in and more!
Certain network functionality and client technologies can only be accessed through netsh. Some examples include IPv6, remote procedure call (RPC), network bridge to Network Access Protection (NAP) client and Wirelesss Hosted Network. With no native graphical user interface to configure network settings in Windows Server 2008 R2: Server Core, netsh knowledge can save you hours of potential frustration.
You can consult the Windows Server 2008 R2 and Windows Server 2008 Netsh Technical Reference to learn more about netsh. The acquired skills are applicable to Windows XP and above.
Mark your calendars for the next Swiss IT Pro User Group events. Taking place on the first Tuesday of every month in Zurich, you are invited to join the PowerShell Script Club on 4 May and 1 Jun 2010. This is moderated by our very own PowerShell MVP.
Registration for this free event and more information here.
The word is out! Official statements on the topic of deploying Office Communications Server 2007 R2 in an environment with Windows Server 2008 R2 are now publicly available.
Whether you are using Windows Server 2008 R2 as a member server (to run OCS 2007 R2) or have deployed the OS running the AD Directory Services (domain controller / global catalog server roles) in a R2 Active Directory forest and domain, you should consult the knowledge base listed here:
The KB articles comprehensively list the known supportability issues and remedy actions. The steps detail the roles, features, hotfixes, updates and changes to security settings that are necessary to enable OCS R2 server roles* to work correctly with the R2 version of Windows Server 2008. Enjoy!
Thanks to Rick for sharing with us this piece of good news.
* except roles like Group Chat Server
To resolve the error encountered below when moving the log folder path in Exchange Server 2010, make sure that sufficient disk space exists on the target disk location.
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:18:47
Mailbox Database 1111111111
Failed to connect to target server “hostname”. Error: WMI exception occurred on server ‘hostname_fqdn’: Call cancelled
Exchange Management Shell command attempted:
move-DatabasePath -Identity ‘Mailbox Database 1111111111′ -EdbFilePath ‘E:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 1111111111\Mailbox Database 1111111111.edb’ -LogFolderPath ‘L:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 1111111111′
Elapsed Time: 00:18:47
To speed things up further on Windows Server 2008 and R2, you can run a backup of Exchange using the built-in Windows Server Backup VSS snap-in (WSB). You must separately install the Windows Server Backup Feature, start WSB, click on the Backup Once link (on right hand Action pane) then use the settings here:
- Backup option - Different options
- Backup Configuration - Custom
- Items for backup - On Windows Server 2008 R2, you must explicitly select items to backup, contrary to the Note described in the TechNet article here*. This should include the System state, the system partition (normally C:) and all volumes containing Exchange data. The logs should automatically be truncated if you choose the option Advanced Settings / VSS Settings / VSS full Backup.
The only visual Q that Exchange 2010 is detected on the system comes after you start the actual backup process:
Status: Running consistency check for application Exchange …
Depending on the size of the data, this can take several minutes to complete. Pass this check will kick start the actual process:
Status: Backup in progress…
* TechNet article reads “Note: By default, volumes that contain operating system components or applications are included in the backup and can’t be excluded.”
- Risk and Health Assessment Program for Active Directory - Scoping Tool v1.3
- Infrastructure Planning and Design v1.0
- Forefront Unified Access Gateway (UAG) 2010 Evaluation Version
- Forefront Threat Management Gateway (TMG) Documentation
- Getting to Know Hyper-V: A Walkthrough from Initial Setup to Common Scenarios v1.0
- Code Name Dublin Tutorials (November 2009)