Views:

 

Symptoms

 

 

An agentless back up to a Windows OSS server will fail with the error 'Create LUN operation failed with error code: -1'

xxx.xxx.xxx 1/5/2018 4:16:15 pm SNBSVH_826E ............Extended error: There has
been some problem in processing disk ([CETSI-ZAM-SVC-VMFS01] CSI-ZAM-DEX01-6521/CSI-ZAMDEX01-
6521.vmdk), reason (Create LUN operation failed with error code: -1.)

The BEX_iSCSITarget* logs on the OSS server will show an error in the snapshot chain in the live qtree area:

BEX_iSCSITarget36.log: CREATE_NIBBLER_LUN with parameters image file name: U:/[AG-ZAM-DEX01b]ID-14862-CSIVCENTER01@665D48B5/6000C295-e2ad-5d8b-d699-79cae8c58bc6_temp.RAW sparse_file_name: U:/[AG-ZAM-DEX01b]ID-14862-CSIVCENTER01@665D48B5/6000C295-e2ad-5d8b-d699-79cae8c58bc6.LUN lun size: 0 initiator name: iqn.2013-11.com.catalogicsoftware.dpx:csi-zam-inf02--2077547060 host name: dpx.cetsi.fr lun comment: (null) failed with error .SNAPSHOT pointing to invalid path U:\.BackupExpressSnapshots\SSSV_AG-ZAM-DEX01b\BEX-1515101621[AG-ZAM-DEX01b]ID-14862-CSIVCENTER01@665D48B5\7CBD\.SNAPSHOT

Note the error, '.SNAPSHOT point to invalid path ...'.  This is referring to the .SNAPSHOT file in the live qtree area.  Within the file, there will be a path that does not exist under .BackupExpressSnapshots.

Previous backups may or may not be able to be restored - you can check them by running an Instant VMDK restore of the latest available backup.

 

 

 

Resolution

 

 

This behavior has been addressed in a DPX Maintenance Update. The update can be automatically installed via the DPX Software Update System user interface or can be manually downloaded from the Catalogic Software Online Support site. Check the Software Update Release Notes for your DPX release referencing Issue ID DPC-29144, available within the following product patches:

 

 

  • DPX 4.5.2 patch 0177 or later


Please note the fix will not repair the currently failing jobs.  Those jobs need to be replaced with new jobs with different names.  The hotfix will prevent future instances of this issue from happening again.