Export (0) Print
Expand All

Troubleshoot application protection

Updated: May 6, 2015

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

SQL Server

 

Issue Possible Cause Resolution

DPM calculating space requirements incorrectly.

The database you are protecting contains a SQL FILESTREAM.

DPM only considers the size of the mdf and ldf when calculating space requirements for a database.

The DPM server stops responding when performing backup and consistency check of databases on clusters.

There are a larger number (>500) database files in a database on the SQL Server cluster.

Protecting SQL Server clusters with a large number of database files in a database affects the performance of the DPM server. You have to wait for DPM to complete the process.

Scheduled SQL Server protection jobs not starting.

Resources on the protected computer are unavailable and hence SQL Server agent is not able to start.

Restart the computer.

DPM is unable to protect a SQL Server database.

You must have the required software installed to protect a computer running SQL Server.

The following versions of SQL Server must be installed on the instance of SQL Server that is hosting the database that you want to protect:

  • SQL Server 2000 with Service Pack 4 (SP4)

    - OR -

  • SQL Server 2005 with Service Pack 2 (SP2)

noteNote
DPM supports Standard, Enterprise, Workgroup, and Express Editions of SQL Server.

ImportantImportant
You must start the SQL Server VSS Writer Service on the SQL Server. By default, the SQL Server VSS Writer Service is turned off when you install SQL Server 2005.

To start the SQL Server VSS Writer Service

  1. Click Start, point to Administrative Tools, and then click Services.

  2. On the Services screen, scroll down and right-click SQL Server VSS writer, and then click Start.

CautionCaution
After you start the SQL Server VSS Writer Service, we recommend that you do not stop the service. If your backups begin to fail, check to ensure that the SQL Server VSS Writer Service is started.

The SQL Server VSS Writer service fails during protection.

If you are protecting SQL Server 2005 on a Windows Server 2008 operating system, you must install SQL Server 2005 SP2.

For information about running editions of SQL Server on Windows Server 2008, see Running SQL Server on Windows Server 2008 R2 or Windows Vista (http://go.microsoft.com/fwlink/?LinkId=130555).

The SQL Server database backup fails.

If you physically delete one of the database files from the SQL Server and do not remove it from the database, the SQL Server VSS Writer Service will continue to report the deleted file and DPM will not be able to locate it while performing backups.

Delete the database log files using the following query:

ALTER DATABASE <file name>.mdf

REMOVE FILE <file name>_log.ldf

Note that you will not be able to restore to the original location from the backups that existed before you deleted the log files because the file does not exist. To resolve this issue, you must restore the database files, and then attach the database to the instance of SQL Server.

When you perform an inquiry job in the DPM New Protection Group Wizard, such as viewing a list of data sources, if two different SQL Server VSS Writers are enumerating the same data source, the DPM server will crash.

This can occur in the following scenario, where you have two SQL Server VSS writers: SqlServerWriter and MSDEWriter.

  • You install an instance of SQL Server 2005. (The SQL Server VSS Writer Service is turned off by default)

  • Because the SQL Server VSS Writer Service is turned off, the MSDEWriter writer enumerates the SQL Server 2005 databases.

  • You turn on the SQL Server VSS Writer Service in the Service Control Manager, which sets the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings\MSDEVersionChecking registry key value to 1.

  • After the registry key value is set to 1, the MSDEWriter writer stops enumerating the SQL Server 2005 databases, and the SQLServerWriter writer starts enumerating them.

You then set the value of the registry key to zero (0), which causes both the MSDEwriter and SQLServerWriter writers to start enumerating the SQL Server 2005 databases.

To resolve this issue, you must set the value of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings\MSDEVersionChecking registry key to 1 (a non-zero value), so the MSDEWriter is the only writer that enumerates the SQL Server 2005 databases.

Database protection on an instance of SQL Server 2005 fails.

If you are protecting a database on an instance of SQL Server 2000 and then upgrade to SQL Server 2005, database protection on the instance of SQL Server 2005 will fail.

After you upgrade to SQL Server 2005 and then restart the SQL Server VSS Writer service, DPM will not map the existing replica to the protected database. This is because the new VSS writer enumerates the new database, and therefore DPM recognizes it as a new data source.

If this issue occurs, we recommend that you stop protection for the database that is hosted on the upgraded instance of SQL Server 2005, and then use the Create New Protection Wizard to reconfigure protection.

noteNote
After you reconfigure protection, DPM Administrator Console displays the protected database as two separate nodes. The protection status in the Protection task area appears as Inactive replica for one of the database nodes, and the DPM Recovery user interface displays two database nodes with the same name.

No data loss occurs with this issue.

SQL Server 2000 database replica creation job fails running on a 64 bit computer.

Replica creation jobs may fail on a SQL Server 2000 database running on a 64-bit computer in Windows in Windows (WOW) mode.

If a replica creation job fails on a SQL Server 2000 database running on a 64-bit computer in Windows (WOW) mode, check the event viewer on the SQL Server computer for Event ID 20 "Volume Shadow Copy Service error."

For information about a supported hotfix to correct this issue, see Event ID 20 (http://go.microsoft.com/fwlink/?LinkId=73718).

SQL Server full transaction log causes synchronization job failures.

If the database transaction log unexpectedly becomes full on a computer that is running SQL Server, your synchronization jobs will start to fail.

For information about how to resolve this problem, see Microsoft Knowledge Base article 317375, "A transaction log grows unexpectedly or becomes full on computer that is running SQL Server "(http://go.microsoft.com/fwlink/?LinkId=72730).

DPM protection jobs start to fail.

If DPM is protecting a SQL Server database that is using mirroring or log shipping, after a failover the protected primary database will no longer be online and your DPM protection jobs will start to fail.

If you plan to fail-back to the primary database, do the following:

  • After your protection jobs start to fail and the replica is no longer valid, perform a consistency check.

    noteNote
    If you fail-back to the primary database in a short period of time and the replica remains valid, then you do not have to perform a consistency check.

  • If there is a delay in the fail-back to the primary database, you must create a protection group using the New Protection Group Wizard to protect the new active database.

    noteNote
    After the failover, you can stop protection on the new protection group.

If you do not plan to fail-back to the primary database, we recommend that you remove it from protection and then configure protection for the new database. To remove the primary database, do the following:

  1. In DPM Administrator Console, click Protection on the navigation bar.

  2. In the Protection task area, select the database that you want to remove, and then in the Actions pane, select Remove from protection.

  3. In the Stop Protection - <Protection Group name> dialog box, select the Retain Protected Data option, and then click Stop Protection.

After you remove the primary database, configure protection for the new database using the New Protection Group Wizard.

Incremental synchronizations fail for the SQL Server master database.

DPM does not support configuring incremental synchronizations for SQL Server master databases.

DPM allows log backups for databases configured in the full and bulk-logged recovery models. However, log backups cannot run against the SQL Server master database.

Additionally, do not set the synchronization frequency for the master database to "just before a recovery point," because there are no backup logs to obtain from the protected server during the recovery.

DPM is not protecting SQL Server 2005 databases.

SQL Server 2005 includes database snapshots that appear in the New Protection Group Wizard as regular databases. However, DPM does not support protecting database snapshots for recovery.

You can view database snapshots in the Microsoft SQL Server Management Studio in the Database Snapshots folder.

Hyper-V server

 

Issue Reason Workaround

Backups failing for replica virtual machines.

Other jobs may be in progress.

Ensure there are no clashing jobs when the backup is happening.

DPM error 30169: The operation failed for <DatasourceType> <DatasourceName> on <ServerName> because the data source is not available.

Error ID: 30169

Hyper-V virtual machine backups not working.

You may have iSCSI target storage provider enabled on the protected computer.

Add the following key to the registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent\UseSystemSoftwareProvider

Migrating a virtual machine using remote storage from a stand-alone backend to a CSV backend will cause Consistency Check to fail with an “Access Denied” message.

Data Protection Manager (DPM) runs a nightly job that will update the data source information. Run a manual Consistency Check to resolve this issue.

DPM error: DPM failed to synchronize changes for Microsoft Hyper-V \Backup Using Child Partition Snapshot\<<VM Name>> on <<Resource Group>> because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer (ID 30115 Details: Unknown error (0x8004231f) (0x8004231F))

Insufficient storage in snapshot pool.

Verify that the SAN has enough available storage to create hardware snapshots.

DPM error: 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 (0x800423f4) (0x800423F4))

VMMS event: No snapshots to revert were found for virtual machine 'CSVVM02'. (Virtual machine ID 4774EF60-F4B6-47D6-A0B9-60452C6B7FE8)

Auto-mounting of volumes might not be enabled on the protected computer.

Enable auto-mounting by using the following command: Mountvol /E

DPM error: 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 (0x80042306) (0x80042306))

The hardware provider has vetoed snapshot creation.

This is potentially a configuration issue. Check the application event logs for VSS hardware provider events and validate the storage configuration with your SAN vendor.

The operation failed for Microsoft Hyper-V \Backup Using Child Partition Snapshot\Win7.01 on Win7.01.dpmcsv1.DC505.LAB because the data source is not available. (ID 30169 Details: Unknown error (0x80042308) (0x80042308))

Live migration caused the virtual machine to move to another node while the backup was in progress.

Cluster disks are in a bad state.

Data source was deleted.

  1. Rerun the backup job.

  2. Diagnose the storage volume for the virtual machine.

    For information about how to back up virtual machines on CSV, in the DPM 2010 Operations Guide, see Considerations for Backing Up Virtual Machines on CSV with the System VSS Provider.

DPM error: Failed to prepare a Cluster Shared Volume (CSV) for backup as another backup using the same CSV is in progress. (ID 32612 Details: Unknown error (0x8007173d) (0x8007173D))

Too many parallel backups are competing for the same CSV LUN.

For information about how to enforce serial backups, in the DPM 2010 Operations Guide, see Considerations for Backing Up Virtual Machines on CSV with the System VSS Provider.

DPM error: An unexpected error occurred during job execution. (ID 104 Details: Element not found (0x80070490))

There might be a failed disk in the cluster.

Repair or remove the failed disk in the cluster.

Backup of Hyper-V virtual machines are stalled and no data transfer is happening.

TCP Chimney Offloading maybe active.

Run netsh int tcp set global chimney=disabled to disable TCP Chimney Offloading.

Windows servers

 

Issue Possible Cause Resolution

When using WSB, the following errors might occur:

  • DPM has detected a discontinuity in the log chain for <DatasourceType> <DatasourceName> on <ServerName> since the last synchronization.

  • The recovery to the latest point in time failed. During a recovery to the latest point in time, DPM attempts to perform a SQL Server transaction log backup to receive the latest changes from the SQL Server database <DatasourceName> on <ServerName> before starting the recovery. This transaction log backup has failed.

  • DPM attempted to perform a SQL Server log backup, either as part of a backup job or a recovery to latest point in time job. The SQL Server log backup job has detected a discontinuity in the SQL Server log chain for <DatasourceType> database <DatasourceName> since the last backup. All incremental backup jobs will fail until an express full backup runs.

Performing backups using WSB on a server which DPM is protecting can interfere with the backups DPM uses.

If you are using WSB, do the following:

  • Ensure that WSB always takes a COPY backup using the WSB Backup Once Wizard.

  • If you are using WSB Scheduled Backups, ensure that the volumes you are backing up do not contain any application data such as Exchange Server data or SQL Server data.

  • After you reconfigure WSB, on the DPM server, run a new express full backup.

File server

 

Issue Possible Cause Resolution

A Volume Missing error occurs for some of your protected server volumes.

The DPM server cannot identify the volumes.

Perform the following steps to remove the Volume Missing status.

  1. In Administrator Console, click Management and then click Disks.

  2. On the tool ribbon, click Rescan. The current disk data is displayed.

  3. Close Administrator Console, and then restart it. Check for any missing volume alerts in the details pane, and address them.

  4. In the Protection task area, verify that DPM removed the Volume Missing status.

Inconsistent drive letter references in the New Protection Group Wizard.

If you change a volume drive letter and then do not restart the computer before creating a protection group for that volume, inconsistent drive letter references may appear in the New Protection Group Wizard.

To display the correct drive letters in the New Protection Group Wizard, you must refresh the drive letters in SQL by performing the following steps:

  1. Remove the volume from the protection group, retaining the replicas.

  2. Read the volume to the protection group.

The recovery point time is not consistent with synchronization time.

When a recovery point is created, it reflects the time of the most recent change to the protected volume.

For example, if a recovery point is scheduled to be created at 11:00 A.M. and the most recent change to the protected volume occurred at 8:30 A.M., the recovery point that was created at 11:00 A.M. will display a time stamp of 8:30 A.M.

No action is required.

Replicas are marked as inconsistent.

Once a volume is marked as Missing, DPM only brings the volume back online during the next disk modification operation, such as Allocate disk space, or after restarting the computer. DPM then marks the replica as inconsistent.

You must perform a manual consistency check. For information about performing a consistency check, in DPM Help, see How to Synchronize a Replica.

Client computers

 

Issue Possible Cause Solution

Missing recovery points

If a scheduled recovery point creation and a synchronization/consistency check for a client are run concurrently, the recovery point creation is skipped.

To avoid the loss of a recovery point for such clients, schedule an additional recovery point creation at a low usage time so the client computers that miss the recovery point creation have a recovery point created later.

Backups of client computers connected to corporate network through DirectAccess failure with RPC server unavailable error.

Edge traversal is blocked in the firewall settings.

  1. Open the Windows Firewall console (Click Start , click Run, and then type firewall.cpl).

  2. In the left pane, click Advanced settings.

  3. Select Inbound rules, and then scroll down to DPMRA and DPMRA_DCOM_135.

  4. Double-click each rule, and then navigate to the Advanced tab.

  5. In the Edge traversal group item, select Allow edge traversal.

When trying to retrieve information from the Windows Management Instrumentation (WMI) service on <ServerName>, access was denied.

This error can occur when you attempt to add a computer that is running Windows XP SP3 to the DPM server and a Group Policy setting is blocking the WMI service on the targeted computer.

To resolve this error, do the following:

  1. On the targeted computer, click Start, click Run, type regedit, and then click OK.

    CautionCaution
    Serious problems can occur if you modify the registry incorrectly. These problems could require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Always make sure that you back up the registry before you modify it, and that you know how to restore the registry if a problem occurs.

  2. Navigate to the following registry key, and then delete it:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftFirewall\DomainProfile\RemoteAdminSettings
    
  3. Restart the targeted computer, and then try to add the targeted computer to the DPM server again.

SharePoint

 

Issue Possible Cause Resolution

The SQL Server alias did not resolve on the SQL Server Agent and protection for the Windows SharePoint Services farm fails.

The Windows SharePoint Services farm is unable to use a SQL Server alias that was created by using cliconfg.exe.

You must reconfigure the SQL Server alias by using the SQL Server Configuration Manager.

Not all the SQL Server aliases are configured on the front-end Web server.

Check the list of servers on the Central Admin page of the SharePoint farm. Identify the SQL Server aliases from the list of SQL Server computers. Verify if all the SQL Server aliases have been configured on the SharePoint front-end Web server (the one that communicates with the DPM server).

The SQL Server alias is not of type TCP/IP.

DPM supports only TCP/IP SQL Server aliases. Reconfigure the aliases to type TCP/IP.

SQL Server client connectivity components are not installed on the front-end Web server.

Install the SQL Server client connectivity components on the front-end Web server.

For Windows SharePoint Services 3.0/MOSS 2007 farms, SQL Server 2005 client connectivity components are not installed on the front-end Web server.

Irrespective of the version of SQL Server on the back-end servers, for MOSS 2007 and Windows SharePoint Services 3.0, you should install the SQL Server 2005 client connectivity components on the front-end Web server. Also, ensure that all the aliases are configured using this version of the client connectivity components.

Windows SharePoint Services database log files are not truncated.

If the path to any Windows SharePoint Services database log file exceeds 150 characters, DPM cannot truncate the log file.

We recommend running periodic scripts to truncate your Windows SharePoint Services database log files.

The Copy-Only registry value has been set for the specific SharePoint farm on the DPM server.

This registry entry needs to be deleted. It can be found under the following path on the DPM server: “HKLM\Software\Microsoft\Microsoft Data Protection Manager\CopyBackups” with the name equivalent to the name of the Config database of the farm.

The “Do not truncate logs” setting has been enabled for the SQL Server computer on which the SharePoint databases reside.

This can be reset by using the following Windows PowerShell command: Set-DPMGlobalProperty -Dpmserver $DPMMachineName -TruncateSharePointDbLogs $true.

The server process could not be started because the configured identity is incorrect. Check the username and password (0x8000401A).

If the password is reset for the Windows SharePoint Services farm, protection will fail.

From the command prompt, run ConfigureSharePoint.exe to reset the password.

For more information about how to manage password changes, see How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0.

Replica Inconsistent alerts for one or more SQL Server databases that were earlier a part of the SharePoint farm appear in the Monitoring pane.

DPM retains the existing recovery points of the databases that have been removed from the SharePoint farm. This can happen if the removed database is recovered by using DPM or if DPM has been upgraded.

Resolve the alert by clicking Inactivate the alert.

Some of the SharePoint farm’s consistency check jobs appear to have stopped (no data transfer has occurred for a long time).

The consistency check was triggered while recovery of one of the farm’s components was in progress.

Cancel the consistency check job and restart the consistency check for the farm from the Protection pane.

The SharePoint catalog task fails with HR 0x80004003 (Invalid Pointer)

There is a network connectivity issue between the SharePoint front-end Web server and the back-end server.

Rerun the catalog job by using Windows PowerShell.

Exchange

 

Issue Possible Cause Details

Exchange Server data is unavailable for protection.

Before you can protect Exchange Server 2007 data, you must install hotfix 940006. For more details, see Knowledge Base article 940006, Description of Update Rollup 4 for Exchange 2007.

The following versions of Exchange Server must be installed on the computer that you want to protect:

  • Exchange Server 2003 with Service Pack 2 (SP2)

    - Or -

  • Exchange Server 2007

ImportantImportant
To protect Exchange Server data, the Exchange Server databases must be mounted within each storage group.

DPM cannot protect Exchange Server data.

The eseutil.exe and ese.dll versions that are installed on the most recent edition of Exchange Server must be the same versions that are installed on the DPM server.

You must update eseutil.exe and ese.dll on the DPM server if they are updated on a computer running Exchange Server after applying an upgrade or an update.

For more information about updating eseutil.exe and ese.dll, see Protected Computer Software Requirements.

After you rename an Exchange Server storage group, the new name does not appear in the New Protection Group Wizard.

If you use the original storage group name, data recovery fails when trying to dismount the database.

After you rename an Exchange Server storage group, you must restart the Microsoft Exchange Information Store service before you create a new protection group.

To start the Microsoft Exchange Information Store service

  1. Click Start, point to Administrative Tools, and then click Services.

  2. On the Services screen, scroll down and right-click Microsoft Exchange Information Store, and then click Restart.

DPM does not support incremental backups if circular logging is enabled for Exchange Server storage groups.

You cannot enable circular logging if you want incremental backups for Exchange Server storage groups.

For successful incremental backups, we recommend that you disable circular logging for the protected storage group. After you disable circular logging, restart the Microsoft Exchange Information Store service (MSExchangeIS).

To disable circular logging

  1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

  2. If the Administrative Groups branch exists in the left pane, expand it, expand the appropriate administrative group's branch, expand the Servers branch, and then expand the appropriate server's branch.

    If the Administrative Groups branch does not exist, expand the Servers branch in the left pane, and then expand the appropriate server's branch. To expand a branch, double-click the branch or click the plus sign (+) to the left of the branch.

  3. Right-click the storage group for which you want to disable circular logging, and then click Properties.

  4. Clear the Enable Circular Logging check box, and then click OK.

  5. Restart the Microsoft Exchange Information Store service (MSExchangeIS).

To restart MSExchangeIS

  1. Click Start, click Run, and then type services.msc to start the Services snap-in.

  2. Right-click Microsoft Exchange Information Store, and then click Start.

noteNote
If you do not want to disable circular logging, you can modify the protection group properties so that synchronizations occur just before creating the recovery point.

To change the synchronization frequency

  • In the New Protection Group Wizard, on the Specify Short-Term Protection Policy page, select Just before a recovery point.

Replica initialization and express full backup operations stop prior to completion.

When you are protecting data on a computer running a version of Exchange Server, the DPM server must include the Ese.dll and eseutil.exe files that are located in the Exchange Server installation location.

To protect data on a computer running Exchange Server, perform the following steps:

  1. On the computer running Exchange Server, copy Ese.dll and eseutil.exe located in the Exchange Server installation location to the DPM server installation location. The default installation location on the DPM server is <drive>:\Program Files\Microsoft Data Protection Manager\DPM\bin.

  2. Cancel the replica initialization and express full backup jobs that did not complete.

  3. Restart the canceled express full backup jobs.

  4. Run a synchronization with consistency check for canceled replica initialization jobs.

noteNote
We recommend that you use the same processor architecture for the DPM server and the computer running Exchange Server.

If your processor architecture is different, you must do the following:

  1. Install the version of Exchange Server that you are protecting on a test server that is consistent with the hardware of the DPM server.

  2. From the test server, copy Ese.dll and eseutil.exe located in the Exchange Server installation location to the DPM server installation location. The default installation location on the DPM server is <drive:>\Program Files\Microsoft Data Protection Manager\DPM\bin.

The VSS writer does not clear Backup in progress state for the storage group.

In Exchange Server 2007 RTM and Exchange Server 2003 RTM, if you cancel the backup on a storage group within a particular interval (between PrepareForBackup and DoSnapshot), the VSS writer does not clear Backup in progress state for the storage group.

To recycle the VSS writer for:

Event ID 2024 A: Restart the Microsoft Exchange Information Store service to recycle the VSS writer.

Event ID 2024 B: Restart the Exchange Server Replication service (Exssrv.exe) to recycle the VSS writer.

The Microsoft Exchange Information Store service does not appear on the Select Group Members page of the New Protection Group Wizard.

If the Exchange Local Continuous Replication (LCR) VSS replica writer is enabled, the Microsoft Exchange Information Store service will not appear on the Select Group Members page of the New Protection Group Wizard.

To display the Exchange LCR-enabled storage groups in the DPM New Protection Group Wizard, use the following set key command to disable the (LCR) VSS replica writer:

set key EnableVssWriter under
HKLM\Software\Microsoft\Exchange\Replay\Parameters to 0

DWORD type

noteNote
After setting the registry key, you must restart the Microsoft Exchange Server Replication service.

All data replication jobs fail.

If the versions of Exchange Server Database Utilities (eseutil.exe) and ese.dll that are installed on the most recent edition of the protected Exchange Server are different from the versions that are installed on the DPM server, all data replication jobs will fail.

The eseutil.exe and ese.dll versions that are installed on the most recent edition of Exchange Server must be the same versions that are installed on the DPM server. For example, if you are protecting Exchange Server 2003 SP2, Exchange Server 2007, and Exchange Server 2007 SP1, you must copy eseutil.exe and ese.dll from the server running Exchange Server 2007 SP1 to the DPM server.

The following scenarios show the versions of eseutil.exe and ese.dll that you must install on the DPM server:

  • 32-bit operating system

    • If DPM is protecting only computers running Exchange Server 2003 on a 32-bit operating system, copy eseutil.exe and ese.dll from the computer running Exchange Server 2003.

    • If DPM is protecting computers running Exchange Server 2007, the 32-bit versions of eseutil.exe and ese.dll are required from Exchange Server 2007. You can obtain these versions from the Exchange Server 2007 Setup DVD.

  • 64-bit operating system

    • If DPM is protecting only computers running Exchange Server 2003 on a 32-bit operating system, copy eseutil.exe and ese.dll from the computer running Exchange Server 2003.

    • If DPM is protecting Exchange Server 2007, copy eseutil.exe and ese.dll from the computer running Exchange Server 2007.

Exchange Server protection fails.

If the Exchange writer is turned off for the Volume Shadow Copy service in Windows Small Business Server 2003, protection will fail.

By default, the Setup program for Windows Small Business Server 2003 turns off the Microsoft Exchange Server 2003 writer for the Volume Shadow Copy service. To protect data using DPM, the Exchange Server 2003 writer must be turned on.

For more information about this issue, see Knowledge Base article 838183 How to turn on the Exchange writer for the Volume Shadow Copy service in Windows Small Business Server 2003.

To turn on the Exchange writer

  1. Click Start, click Run, type regedit, and then click OK.

  2. Locate and then double-click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

  3. Double-click the Disable Exchange Writer value.

  4. In the Value data text box, change the value from 1 to 0, and then click OK.

  5. Quit Registry Editor.

  6. Click Start, point to Administrative Tools, and then click Services.

  7. Stop and then restart the Microsoft Exchange Information Store service.

Local continuous replication (LCR) protection fails with a VSS error.

If the Exchange Server replication service is not restarted after the registry key is set, LCR fails for the storage group.

Restart the replication service after updating the registry key.

Setting and unsetting the eseutil flag through the command line interface (CLI) fails.

The preferred server may not have been specified.

Provide the topology as PT_CCR_ACTIVE_ONLY along with the RunEseUtilConsistencyCheck option.

The consistency check fails with RMGenericError.

The consistency check will fail if indexing, encryption, or Single Instance Storage (SIS) is enabled for the folder containing the .edb file.

To resolve this issue, disable indexing, encryption, and SIS for the folder containing the .edb file.

System protection

 

Issue Possible Cause Resolution

Bare Metal Recovery (BMR) backups fail with “Access Denied” error.

You have just migrated from System State protection to BMR protection.

  1. Remove BMR protection.

  2. Modify protection group and include BMR protection.

One or more prerequisites for protecting this data source are missing on your Windows Server 2008 operating system.

This error occurs if the Windows Server Backup utility is not installed on the protected server.

To resolve this issue, do the following:

  1. To install the Windows Server Backup utility, open a command prompt with administrator privileges, and then type Start /wait ocsetup WindowsServerBackup /quiet /norestart.

    noteNote
    To open a command prompt with administrator privileges, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

Virtual server

 

Issue Possible Cause Resolution

You may see the error One or more volumes are missing for the following application: <Virtual machine name>. Ensure that the dependent volumes for the data sources are online. when you select a Virtual Server 2005 R2 based virtual machine.

For Virtual Server 2005 R2, DPM does not support backing up virtual machines hosted on a volume that does not have a drive letter.

noteNote
This problem does not apply to Hyper-V virtual machines.

Provide a drive letter mount point for the volumes on which the VHD files exist and attempt to select for backup with DPM again.

Data on the virtual machine is unavailable for protection.

Virtual Server 2005 R2 Service Pack 1 (SP1) may not be installed on the server you want to protect.

Install Virtual Server 2005 R2 Service Pack 1 (SP1) on the server that you want to protect.

Backup fails on the virtual machine with unknown error 0x800423f3.

The Virtual Server VSS Writer service does not support online backup for the client virtual machine.

Use Windows Event Viewer on the Virtual Server machine to find if Event ID 1044 exists. If this event exists, the virtual machine cannot perform online backups.

You can perform offline backups by updating the following registry key:

Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual Server\1.0\Backup\BackupType\<VMNAME> to 0.

Online backup fails.

Online backups fails if the virtual machine contains volumes that do not support shadow copies (FAT 32 file systems). Additionally, if the shadow copies exist on different virtual machine volumes, the backup fails.

Install Knowledge Base article 940349 “Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues” on the virtual machine.

Ensure that the virtual machine is running before configuring the backup, and then delete the entries for the virtual machines for which the online backup is failing. Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual Server\1.0\Backup\BackupType.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft