Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.11 File System User Guide

Disaster recovery

You might encounter the following issues while performing disaster recovery with the File System agent.

BMR and SSR operations fail to run and a start_subscriber error appears in the agent-service log

A BMR or SSR operation might fail to display the start or completion of a job, and the DPSAPPS\AgetService log shows an error similar to msg_server.py-create_subscriber()Line 617 Exception occurred during start_subscriber Permission denied occurred.

This is caused when another service uses port 7010 or 7011.

Reconfigure any service that uses port 7010 or 7011 to use a different port.

Backing up BMR data fails with a ddfssv error

Backing up BMR data can fail with the error ddfssv FATAL <12128: Attempt to create a backup with no data is unsuccesful.

The Event Viewer system log might also contain an error similar to the following:

The shadow copies of volume H: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

This is a known Microsoft issue that affects all backup products.

Retry the backup procedure after leaving more free space on the drive or when the drive is not as busy.

Network connectivity issues after a BMR

A BMR can fail to recover network configuration information such as IP address, subnet mask, gateway, and DNS. If the recovered host experiences network connectivity issues, confirm its network configuration and make any necessary changes.

SSRs fail to restore a VSS writer

If an SSR fails to recover a VSS writer, you might see an error similar to the following:

ddfsrc Error <0000>: Unable to select W component from V for restore: The specified object was not found. (VSS error 0x80042308)

This occurs when writer .xml files are missing from the C:\Windows\Vss\Writers\System directory.

Restart the host, run the command vssadmin list writers to confirm the VSS writer status, and then retry the SSR.

BMR recovers critical volumes, but a disk is marked as offline

This can happen with disks that host Microsoft SQL Server instances.

Manually bring the disk online, and then restart the host.

SSRs show a RegSetValueEx() error and fail to recover files after a restart.

An SSR might show Error <10958>: RegSetValueEx() for replace files, but complete successfully. After the host is restarted, certain files have not been recovered.

A file that is in use cannot be replaced by its recovered version. If you restart a host to have a file replaced but the file is not replaced, it might be because antivirus software is preventing access to the pendingfilerenameoperations registry key.

Perform one of the following tasks as a workaround.

  • Use file exclusion:
    1. Retry the SSR, but do not restart the host.
    2. Exclude ddfssv.exe, ddfsrc.exe, ddfscon.exe, and restserver.exe from the antivirus software.
    3. Restart the host.
    4. Optionally, remove the files from the exclusion list.
  • Temporarily disable the antivirus software:
    1. Retry the SSR, but do not restart the host.
    2. Disconnect the host from the network.
    3. Disable the antivirus software.
    4. Restart the host.
    5. Enable the antivirus software.
    6. Connect the host to the network.

Temporary files can be deleted manually after a recovery operation

The temporary files that are generated during the recovery operation are stored in C:\dbapps_temp_dir. You can delete these temporary files manually after the recovery operation and the reboot.
NOTE
  • Replace C: with the drive to which Windows is installed.
  • You may require special permissions to delete some temporary files. To delete such files, contact Customer Support.

BMR restore errors

When performing a BMR restore, you might see the errors similar to the following:
Assigning volume letters or mount points failed.
Unable to do VSS restore: Bare metal recovery remount volumes step failed.

Perform the BMR restore again.

Cluster assets backup failure

The cluster assets backup fails when there is a combination of either stand-alone and cluster assets, or disaster recovery and cluster assets in the same policy.

Workaround is to run the cluster backup in a different policy and schedule.

BMR backup fails on EFI based system for a few times when backing up the BCD files

Backup for Extensible Firmware Interface (EFI) partition is performed from the live volume as the snapshot volume of the EFI partition cannot be created. If the system process uses the Boot Configuration Data (BCD) files, the ddfssv process tries to export a temporary copy for BCD files using the Microsoft bcdutil tool. This issue occurs if the export operation causes any change in the exported file.
A sample ddfssv log file with errors:
--------------------------------------------------------

2022-05-18T08:10:08.914Z [TRACE_ID:a559c76a1e886397;JOB_ID:9333c654df01e5af;EXEC_ID:af0c561e68d3aa75] ddfssv Info <0000>: Exported bcd file to temporary location
2022-05-18T08:10:08.920Z [TRACE_ID:a559c76a1e886397;JOB_ID:9333c654df01e5af;EXEC_ID:af0c561e68d3aa75] ddfssv Error <16507>: Path \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD: Total processed bytes 32768 is inconsistent with original data size xxxxx
2022-05-18T08:10:08.926Z [TRACE_ID:a559c76a1e886397;JOB_ID:9333c654df01e5af;EXEC_ID:af0c561e68d3aa75] ddfssv Error <16507>: Path \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD.LOG: Total processed bytes 32768 is inconsistent with original data size xxxxx
...

2022-05-18T10:51:25.078Z [TRACE_ID_a559c76a1e886397_EXEC_ID_af0c561e68d3aa75] ddfssv Info <6149>: Error summary: 2 errors: 16507(2)
2022-05-18T10:51:25.102Z [TRACE_ID_a559c76a1e886397_EXEC_ID_af0c561e68d3aa75] ddfssv Info <5314>: Command completed with exceptions (2 errors, exit code 10020: completed with errors, client log should be examined)
...
------------------------------------------------------------
Workaround is to rerun the backup.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\