You are browsing the archive for issues.

From the Forums: Could not enumerate Exchange

8:50 am in Uncategorized by mikeresseler

Here’s a strange case that has been discussed on the great DPM forums.

A user reported that he could not enumerate the Exchange server when he was creating a protection group for Exchange Server using the DPM wizard.

These are the errors he got:

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e\File on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e\Logs on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

We let him do all the usual stuff but it didn’t solved anything.

Until today, nothing was found to solve this case, and there were many more reporting this issue.  But today, a user named Frans Molenaar found a solution.  Although it sounds like a very strange solution which has nothing to do with the issue, I decided to test it out in my sandbox and come to the conclusion that it actually indeed solved the case.

So here goes:

First: Check on the exchange server if the following powershell scripts exist:

In  %ExchangeInstallPath%\bin you need to find the following scripts:

  • CommonConnectFunctions.ps1
  • CommonConnectFunctions.strings.psd1
  • Connect-ExchangeServer-help.xml
  • ConnectFunctions.ps1
  • ConnectFunctions.strings.psd1
  • RemoteExchange.ps1
  • RemoteExchange.strings.psd1

Second: Check the following registry keys if they exist:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns]
@=””

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.E2010]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn”
“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Admin Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.Configuration.dll”
“PowerShellVersion”=”1.0″
“Vendor”=”Microsoft Corporation”
“Version”=”14.0.0.0″

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.Setup]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn”
“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Setup Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.configuration.dll”
“PowerShellVersion”=”1.0″
“Vendor”=”Microsoft”
“Version”=”14.0.0.0″

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.Powershell.Support]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.Powershell.Support.SupportPSSnapIn”
“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.Management.Powershell.Support, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Support Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.Management.Powershell.Support.dll”
“PowerShellVersion”=”1.0″
“Vendor”=”Microsoft Corporation”
“Version”=”14.0.0.0″

If this is not the case, then copy the registry keys from another exchange server and after that, it works.

To test this, I exported some of the registry keys, removed them and tried the DPM wizard.  I got exactly the error as described in the thread.  After imorting the keys again, everything worked as a charm.

If you have this similar issue, then check these things out

For the complete thread: http://social.technet.microsoft.com/Forums/en-US/dpmexchbackup/thread/25ef304c-b9b5-47b6-a65d-17967ab0ad62/

And thank you Frans Molenaar for finding this solution

Cheers,

Mike

DPM 2010 QFE Rollup available

10:55 am in Uncategorized by mikeresseler

Microsoft has just released a DPM 2010 QFE Rollup.

This, much awaited hotfix rollup, fixes the following issues:

  • You cannot protect the Microsoft Exchange Database Availability Group (DAG) on a secondary DPM 2010 server.
  • You are prompted to restart a client computer after you install an agent on the client.
  • DPM services crash, and you receive the error, “Unable to connect to the database because of a fatal database error.”
  • MSDPM crashes, and event ID 945 is logged in the event log.
  • When you change a Protection Group, add a very large database, change the disk allocation, and then commit the Protection Group, DPM 2010 does not honor the user intent, and instead, DPM 2010 sets the sizes of replica and shadow copy volumes to the default sizes.
  • The Management tab does not link to information about the latest Microsoft Knowledge Base article for DPM 2010.
  • You receive the message, “Computers not synchronized,” when you try to replicate DPM 2010 databases to a System Center Operations Manager. 

The information for the KB can be found here: http://support.microsoft.com/kb/2250444

The download can be found here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f399fbfa-5c8b-4eb6-bda2-ea997745919a

Enjoy

Mike

From the forums: End-user Recovery when file server is down

2:19 pm in Uncategorized by mikeresseler

Just read a very interesting topic on the forums (link)

A user reported that when the file server is down, the users in his company were still able to get to their files (read-only) through the DPM server.

So basically, when the file server is down, end-users were still able to contact the last backup data through the DPM server through a share named “protectedServerName_protectedServerShare".

He wondered if this was by design, or a bug.

The answer came quickly.  This is by design.  So if your file server is down, and the uses had access to the end-user recovery on the file server, then he or she will still be able to access the data through the DPM server.

Cheers,

Mike

Another fine new blog?

7:54 am in Uncategorized by mikeresseler

Hey All,

Just discovered (by accident) a new blog about DPM.  The name of the blog is DPMCallBack and can be found here: http://blogs.technet.com/b/dpmcallback/

The first post is already a good one so I’m hoping for more :-)

The post describes the questions that you will get when you have issues with your DPM installation.  Whenever you want to open a case for DPM, it is good to have these questions answered in advance, it will save you some time 😉

Here is a copy of the questions:

• Is this a fresh installation of DPM using the RTM bits or was this an upgrade from a previous version or from Beta?

• When did the problem first start? You can select the Monitoring tab and review the Alerts/Jobs for details.

• Has it ever worked as expected?

• What changes (if any) were made just prior to the failures?

• Can you reproduce the problem? If so can you please provide the exact steps?

• Are other protected data sources experiencing the same problem?

• Is the error specific to one type of data source? Example, Exchange jobs fail but SQL and SharePoint are successful.

• What is the application version that is experiencing the problem? Example, SQL 2005, SQL 2008, Exchange 2007…etc.

• Is the protected data source running on a standalone server, domain controller or a cluster?

• Is the system that is experiencing the problem in the same domain as the DPM server?

• Do other protected data sources reside on the same machine? Are they also failing?

• Is the target machine for which you’re experiencing the issue on the same LAN as the DPM server or over a WAN?

• What is the error message and ID in the Details pane? If possible, please copy/paste this or provide a screenshot.

 

Cheers

Mike

System Center Data Protection Manager 2007: Important Hotfix Rollup Package

9:30 am in Uncategorized by mikeresseler

Hey All,

Microsoft has released a hotfix rollup package for SCDPM 2007 SP1.  This package resolves a lot of issues with this product:

Issue 1
If you enable library sharing, you cannot delete a protection group, and you receive the following error message:

Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.

Issue 2
The SharePoint backup process fails if DPM 2007 cannot back up a content database. If you install this update, the SharePoint backup process will finish. However, an alert will be raised if DPM 2007 cannot back up a content database.

Issue 3
DPM 2007 jobs randomly fail. In the administrator console, you see error code 0x800706BA if you check the detailed information about the failed job.

Issue 4
DPM 2007 does not delete directories that are no longer being protected from the replica volume.

Issue 5
When you restore a Microsoft SharePoint site that is configured to use a host header, the incorrect SharePoint site is restored.

Issue 6
DPM 2007 performs a Volume Shadow Copy Service (VSS) full backup. Because the transaction logs are deleted when the DPM 2007 backup job is completed, this backup may interfere with other applications that are backing up transactional applications such as Microsoft SQL Server or Microsoft Exchange.
After you install this update rollup, you can configure DPM 2007 to perform VSS copy backup. This means that the application transaction logs will not be deleted when the DPM 2007 backup job is finished.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To configure DPM 2007 to perform VSS copy backup, add the following CopyBackupEnabled registry value under the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0

Registry value: CopyBackupEnabled
Type: REG_DWORD
Value Data: 1

Issue 7
Reconciling a VSS shadow copy causes the DPM 2007 service to crash.

Issue 8
The DPM 2007 service crashes if a tape backup job is canceled during the CheckConcurrencyBlock operation.

Issue 9
The Pruneshadowcopies.ps1 script cannot delete expired recovery points.

Issue 10
If a parent backup job of a SharePoint farm fails, but the child backup succeeds, the DPM 2007 service crashes.
This hotfix also includes the following previously released rollups for Data Protection Manager 2007 Service Pack 1:

961502 (http://support.microsoft.com/kb/961502/ ) A replica may be listed as inconsistent after you install System Center Data Protection Manager 2007 Service Pack 1 on a computer that is running an x64-based version of Windows Server 2003

963102 (http://support.microsoft.com/kb/963102/ ) Description of the hotfix rollup package for System Center Data Protection Manager 2007: February 16, 2009

968579 (http://support.microsoft.com/kb/968579/ ) Description of the hotfix rollup package for System Center Data Protection Manager 2007: April 14, 2009

Make sure you install this one on all of your DPM installations:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;970867

Cheers,

Mike

Prerequisites and Known Issues with Hyper-V Protection

9:17 am in Uncategorized by evilbart

SP1 for dataprotection 2007 is now available, but if there are some prerequisites and known issues with Hyper-V protection:

 

Prerequisites:

Before protecting Hyper-V virtual machines with DPM, ensure that the following updates are installed on the target Hyper-V server:

  • The customer should be running Hyper-V RTM. The corresponding Windows update is KB950050 (http://go.microsoft.com/fwlink/?LinkID=132735). HyperV Manager version should be 6.0.6001.18016.
  • Install the following updates:
    • KB951308 (http://go.microsoft.com/fwlink/?LinkID=132733) on each cluster node for cluster deployment.
      Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role.
    • KB959962 (http://go.microsoft.com/fwlink/?LinkId=136583) on the Hyper-V host and the guest virtual machines. This update for Hyper-V writer is required for backing up Hyper-V VMs with DPM.
      Dd347840.note(en-us,TechNet.10).gifNote
      KB959962 is scheduled to release in January 2009, it enables online protection of Hyper-V guest machines. Until the update is available, virtual machines can be protected by configuring them for offline backup within each machines’ Integration Components service settings. Open the Settings window for the virtual machine and select Integration Services in the left pane. Clear the check box for Backup (volume snapshot) service and click OK. If you have set the DWORD AllowOffline registry key under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent make sure the value is not zero (0).

       

       

    • KB960038 (http://go.microsoft.com/fwlink/?LinkId=136584) on all Hyper-V hosts. This update for Windows Server 2008 fixes a crash of the Hyper-V host server which you may experience when backups are made using Hyper-V writer.
  • The version of Integration Components running inside the VM should be the same as the version of Hyper-V on the host. For Hyper-V RTM it is 6.0.6001.18016.
    You can confirm this in the Device Manager inside the guest VM. Under System Devices in Device Manager, right-click on the entry Hyper-V Volume Shadow Copy and choose Properties. Check the version under the Driver tab. If the version does not match, insert the integration services disk by choosing the option under the Action menu in the VM console. Install the integration components and reboot the VM.

Known Issues:

Issue

Symptoms

Cause

Workaround

Solution

Recommendation

Hyper-V server stops working when DPM runs backups on the server.

You may experience a Stop 0x7E when you backup a server that has the Hyper-V role installed.

This is a problem in the volsnap.sys driver when interacting with the Hyper-V VSS writer.

N/A

Download and install KB960038 on the Hyper-V host to solve this problem.

We recommend that you deploy this in the next available downtime window on the Hyper-V host.

Backup of Hyper-V virtual machine fails

Hyper-V virtual machine backups (backups using child partition) fail with following error for multiple volume virtual machines: DPM encountered a retryable VSS error. (ID 30112 Details: Unknown error (0x800423f3) (0x800423F3)).
On the Hyper-V host in the event log: VMMS Event log contains following entry:
Failed to revert to VSS snapshot on one or more virtual hard disks of the virtual machine ‘%1′. (Virtual machine ID %2).

.

Perform an offline backup of the virtual machine.

Download and install KB959962 on the Hyper-V host to solve this problem.

We recommend that you install this update on all Hyper-V hosts protected by DPM.

Recovery of Hyper-V virtual machine fails

The Hyper-V Virtual Machine Management service stops when you are restoring a virtual machine.

This issue can occur if the virtual machine is configured to use a legacy network adapter.

Restart the Hyper-V Virtual Machine Management service.

Download and install KB959962 on the Hyper-V host to solve this problem. Then recover the data to an alternate location.

We recommend that you deploy this update on all Hyper-V hosts protected by DPM.

Backup of the Hyper-V virtual machine fails

Hyper-V VSS writer is in a bad state and does not identify itself to VSS anymore. The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation (ID 30111 Details: Unknown error (0x80042319) (0x80042319)). Please check that the Event Service and the VSS service are running, and check for errors associated with these services in the Application Event Log on the server hyper01.contoso.com. Please allow 10 minutes for VSS to repair itself and then retry the operation.

This is a problem in the Hyper-V writer in Windows Server 2008.

To get the writer back to a stable state, restart the Hyper-V Virtual Machine Management service. Perform offline backups of the virtual machines to prevent the writer from going into a bad state.

Download and install KB959962 on the Hyper-V host to solve this problem.

We recommend that you deploy this update on all Hyper-V hosts protected by DPM.

 

Grtz,

Alexandre Verkinderen

http://scug.be/blogs