Summary
A backup or restore of a Microsoft SQL Server on a Windows cluster fails. The DPX job log displays a failed PIPE operation. To resolve this issue, make the corrections described to the DPX registry key.
Symptoms
The DPX event handler log (EHL) displays the PIPE usage error:
Thu Sep 25 19:59:44 2003 SNBEH_3067I 3840: DPX VDI support? NO
Thu Sep 25 19:59:50 2003 SNBEHD3072J 3840: Connecting to SQL Server...
Thu Sep 25 19:59:50 2003 SNBEH_3067I 3840: MS SQL Server version 8.00 (SQLDMO)
Thu Sep 25 19:59:50 2003 SNBEH_3067I 3840: Version string: Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Thu Sep 25 19:59:50 2003 SNBEH_3067I 3840: DPX VDI support? NO
Resolution
If you add the NOVDI option to the DPX registry key (HKLM\Software\Syncsort\BackupExpress\<hostname>\0) to force the use of a PIPE for backup or restore of a Microsoft SQL Server, all backup and restore jobs fail. The issue is that the Microsoft SQL Server becomes a part of the Windows cluster. The clustered environment does not support PIPEs, as a backup/restore mechanism.
To resolve this issue, remove the NOVDI option and use the --vditimeout 600 entry for SSDMBS and SSDMRR (create an HKLM\Software\Syncsort\BackupExpress\<hostname>\0 registry entry for SSDMBS and SSDMRR if they do not exist).
The following is part of a typical Catalogic Software registry entry for these values:
HKEY_LOCAL_MACHINE\Software\Syncsort\BackupExpress\<hostname>\0\SSDMBS
--vditimeout 600
HKEY_LOCAL_MACHINE\Software\Syncsort\BackupExpress\<hostname>\0\SSDMRR
--vditimeout 600