• United States

Microsoft works to fix backup compatibility flaw

May 23, 20034 mins
Backup and RecoveryData CenterMicrosoft

A change to Microsoft’s tape backup feature makes file backup tapes created with Windows Server 2003 incompatible with previous versions of Windows including Windows XP and Windows 2000.

A change to Microsoft’s tape backup feature makes file backup tapes created with Windows Server 2003 incompatible with previous versions of Windows including Windows XP and Windows 2000.

The problem is due to a change in the Windows Server 2003 version of the free ntbackup.exe utility that comes with Windows operating systems and was first disclosed in the online security news group NTBugtraq.

The change means that backup tapes formatted using Windows Server 2003 cannot be used to restore data to Windows 2000 or Windows XP machines, according to Brian Bergin, president of Terabyte Computers, a Boone, N.C., IT consulting company.

When contacted about the problem, a Microsoft spokeswoman confirmed that the problem affects Windows 2000 Server and Professional as well as Windows XP.

Whereas the backup feature in Windows 2000 and Windows XP wrote data to removable media such as magnetic tape drives in 32K-byte blocks, Windows Server 2003’s backup feature writes data in 64K-byte blocks, according to the spokeswoman.

According to Bergin, a manager in Microsoft’s storage services group said the problem stemmed from an “oversight” in testing data migration scenarios from Windows 2003 to the Windows 2000 and XP platforms.

Bergin discovered the problem while working on behalf of his customers, which are mostly small businesses with between eight and 12 workstations connected to a common file server.

“Typically, if I have a customer with a server that goes down, I pull the tape drive and the controller out of the server and put it in a workstation and restore the files they need. When the server comes back up, I can copy the files back. It works like a champ. You can go from 2000 to XP and vice versa all day long, but not from Windows Server 2003,” he said.

After discovering the problem in late April, Bergin reported it to Microsoft technical support, who initially seemed uninterested in it.

“Their initial response to me was to tell me to buy third-party backup software,” he said.

After explaining the problem to Microsoft support in more detail, however, the company became more interested, confirming the problem’s existence and assigning him a case number for it, Bergin said.

“The problem doesn’t affect the integrity or reliability of the systems, but it delivers a customer experience that is inconsistent with Microsoft’s intended design,” the Microsoft spokeswoman said.

Microsoft has created and is testing a fix for the problem. The company will be issuing the “correction” within days, after the fix has been tested and documented.

Microsoft could not comment on whether the fix would be to the ntbackup.exe program, or to another Windows software component involved in handling removable storage media.

Third-party data backup and recovery software for Windows Server 2003 is not affected by the problem, Bergin said.

In the absence of a patch for the problem, Windows 2003 customers with backup tapes that were formatted on that platform have to copy the Windows Server 2003 version of ntbackup.exe to the non-Windows Server 2003 machine.

However, that work-around is not supported by Microsoft and may be in violation of the company’s licensing agreement, Bergin said.

For organizations that have not yet formatted their backup tapes, doing the initial format on a Windows 2000 or Windows XP platform first will ensure that the tapes are formatted using 32K-byte data blocks and can be used on all the platforms, Bergin said.

While a fix for the backup compatibility issue will likely be available soon, Bergin worries that the problem is just the tip of the iceberg and may indicate that the code bases for the various Microsoft operating systems are diverging from one another.

“Once the ntbackup problem is fixed, what else are we going to find that’s incompatible between (Windows) XP in Windows Server 2003?” he said.