topic Re: DFM Zapi failed to connect to the DFM in Data Protection

DFM Zapi failed to connect to the DFM

pdegand — Thu, 05 Jun 2025 07:05:08 GMT

When I run this command on a W2003 SP2 with SnapDrive 6.2 :

SDCLI.exe dfm_config set -host 192.168.1.16 -user xxx

I get this error :

Creating ConfigManagement web service client...

A FaultException<SDResult> occurred:

DFM Zapi failed to connect to the DFM server '192.168.1.16'.

The operation completed successfully.

The two machine have the firewall disabled, you know what i have to do ?

Thanks

Re: DFM Zapi failed to connect to the DFM

mschlaerth — Tue, 22 Mar 2011 02:30:19 GMT

have exactly the same issue... no firewall, wie open account priveleges (lab enviro) and not sure whether DFM listens on port 8088 to begin with.... (not conveniently documented....) grasping at straws to get SD-WIN into a PM integrated state shy of re-installing SD-WON.... seeing this as a weak documentation spot....

Re: DFM Zapi failed to connect to the DFM

daehnrich_bsh — Wed, 20 Apr 2011 14:07:04 GMT

same error here on sdcli dfm_config set

dfm user add -r GlobalFullControl test_tdfm

C:\>sdcli dfm_config set -host testdfm -user test_tdfm -pwd XXXXX -p 8088

Creating ConfigManagement web service client...

A FaultException<SDResult> occurred:

DFM Zapi failed to connect to the DFM server 'testdfm'.

The operation completed successfully.

C:\>sdcli dfm_config list
List of DFM Servers
------------------

HostName       :
UserName       :
Port           : 0
Protocol       : HTTP
The operation completed successfully.

Re: DFM Zapi failed to connect to the DFM

miguelvalls — Mon, 05 Sep 2011 18:19:54 GMT

Hi,

We have the same problem, but in NOW I can´t find anything about this error, we have a integration with SMSQL and QSV with Protection Manager.

[12:32:27.293] Starting dataset backup add...

[12:32:27.294] Preparing to add snapshot 'sqlinfo__bane_09-05-2011_12.06.26__daily' of LUN 'S' to dataset backup...

[12:32:27.295] Adding backup using dataset [SnapMgr_SQLServer_BANE] with backup version [1315240668]...

[12:33:27.763] SDDatasetBackupAdd failed.

[12:33:28.213] [SDAPI Error]: DFM Zapi failed to connect to the DFM server 'venbbpr1.caf.com'.

107

[12:33:28.213] Unable to add backup to dataset for VSS backup.

[12:33:28.214] [SDAPI Error]: DFM Zapi failed to connect to the DFM server 'venbbpr1.caf.com'.

107

[12:33:28.215] Backup transfer is in progress, skipping dataset transfer...

[12:33:28.215] Saving SnapInfo dataset info to SnapInfo file...

[12:33:28.425] Ending dataset backup now...

[12:34:28.488] SDDatasetBackupEnd failed.

[12:34:28.699] [SDAPI Error]: DFM Zapi to modify backup version = 0 failed. Error code: 13011. Error description: HTTP POST - Internal error.

102

[12:34:28.700] Unable to end dataset VSS backup.

[12:34:28.701] [SDAPI Error]: DFM Zapi to modify backup version = 0 failed. Error code: 13011. Error description: HTTP POST - Internal error.

We have a windows cluster server with 3 SQL instances, in cluster1, 1 instance, in cluster2, 2 instances, all integrated with protection Manager.

Versions

SDW 6.3P2

Operation Manager: 4.0.2D2

Management Console: 3.0.2

SMSQL: 5.1

Windows: 2008 SP2

Please if anybody has something similar let me know before open a case.

Many thanks

Miguel Valls

Re: DFM Zapi failed to connect to the DFM

jakub_wartak — Mon, 12 Sep 2011 08:06:29 GMT

Hi,

HTTP Post errors are indication of "internal overlaod" in DFMserver process. Please take a look on this thread http://communities.netapp.com/thread/14463 . I have no idea was it solved or not, but clearly DFM intergration with snapdrive has scalability problems. The possible solutions are to upgrade to some "D"-version of snapdrive (e.g. for UNIX) to increase the DFM connect timeout/cache some querys and upgrade to also "D"-version of DFM that scalability improvements to cache more queries.

Info comes from something like 1-2 months ago, please be sure to contact DFM product managment - they should be well aware of this problem.

-Jakub.

DFM Zapi failed to connect to the DFM

kenheal_db — Thu, 20 Oct 2011 18:20:29 GMT

Did this get resolved? What was the fix? I am seeing this at a customer. Thanks.