DPM 2007 Known Issues
Applies To: System Center Data Protection Manager 2007
This topic documents the following known issues and resolutions for System Center Data Protection Manager (DPM) 2007:
See Troubleshooting SharePoint Protection and Recovery
Microsoft SQL Server
While restoring a SQL Server 2000 database you cannot rename the database
DPM does not support recovering a SQL Server database to a file path that exceeds 256 characters
Setup fails while installing SQL Server 2005 to a directory containing Unicode characters
SQL recovery fails with error ID 30111
Cannot protect database with name ending with a space
SQL 2000 Error: Arithmetic overflow error converting expression to data type int
DPM continues protecting deleted SQL 2000 files
Microsoft Exchange Server
- Exchange writer must be turned on for the Volume Shadow Copy service in Windows Small Business Server 2003
Virtual Servers
- DPM does not support backup of host clustered virtual servers
Tape
DPM 2007 does not support data recovery from Beta 1 tapes
Issues with DPM 2007 supported tape libraries
IO device errors during tape backups
While restoring a SQL Server 2000 database you cannot rename the database
You cannot change the name of a SQL Server 2000 database when restoring it to the protected computer.
DPM does not support recovering a SQL Server database to a file path that exceeds 256 characters
If you are recovering a SQL Server database to an alternate location whose file path exceeds 256 characters, the recovery will fail. You must ensure that the file path of the alternate location is fewer than 256 characters.
Setup fails while installing SQL Server 2005 to a directory containing Unicode characters
If you are running an English version of Windows Server 2003 SP2 with a localized Multilingual User Interface (MUI) Pack, DPM Setup will fail if your are installing SQL Server 2005 to a directory that contains Unicode characters.
You must select an installation directory that does not contain extended Unicode characters (for example, <drive letter>:\DPM2007).
SQL recovery fails with error ID 30111
Recovery of a SQL server may fail with the following error “The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation (ID 30111)”.
One of the reasons for this could be that the default path of the file being recovered points to the quorum disk of the cluster to which it is being recovered.
Cannot protect database with name ending with a space
If you have a SQL database that has a space at the end of the name, for example ‘TextDB “, then SQL Server writer cannot display it, and therefore it cannot be protected by DPM.
SQL 2000 Error: Arithmetic overflow error converting expression to data type int
You will see this error if the value for max_size of the log (.ldf) file when multiplied by 8 is larger than the maximum ‘int’ size (2,147,483,647). For more details, refer to KB911851 (https://go.microsoft.com/fwlink/?LinkID=128345).
DPM continues protecting deleted SQL 2000 files
Due to SQL 2000 writer issues, DPM will continue to show successful backups of a SQL 2000 file that has been deleted from the database. If you try to recover the deleted database from a recovery point that was created after the file was deleted, the recovery will fail.
Exchange writer must be turned on for the Volume Shadow Copy service in Windows Small Business Server 2003
By default, the Setup program for Microsoft Windows Small Business Server 2003 turns off the Microsoft Exchange Server 2003 writer for the Volume Shadow Copy service. To protect data using DPM 2007, the Exchange 2003 writer must be turned on.
For more information about this issue, see Knowledge Base article "How to turn on the Exchange writer for the Volume Shadow Copy service in Windows Small Business Server 2003" (https://go.microsoft.com/fwlink/?LinkId=77040).
To turn on the Exchange writer
Click Start, click Run, type regedit, and then click OK.
Locate and then double-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Double-click the Disable Exchange Writer value.
In the Value data text box, change the value from 1 to 0, and then click OK.
Quit Registry Editor.
Click Start, point to Administrative Tools, and then click Services.
Stop and then restart the Microsoft Exchange Information Store service.
DPM does not support backup of host clustered virtual servers
DPM does not support backup of clustered virtual servers on the host computer. To protect clustered virtual servers, you must perform a guest backup by installing the protection agent inside the virtual machine.
DPM 2007 does not support data recovery from Beta 1 tapes
The RTM release of DPM 2007 does not support data recovery from tapes that were used in DPM Beta 1. DPM 2007 supports data recovery only from tapes that DPM used in the Beta 2 release and later.
Issues with DPM 2007 supported tape libraries
The following table lists the tape libraries that DPM supports and the issues that you might encounter when using them.
Note
DPM does not support Write-Once Read-Many (WORM) media.
The driver/firmware levels listed for the tape libraries in the following table have been tested with DPM 2007. The latest revisions of these driver/firmware levels might not be up-to-date, but it is assumed that future driver/firmware revisions will work with DPM 2007.
| Library | Issue | Resolution |
|---|---|---|
Assorted tape libraries |
Some tape libraries contain a slot which can be marked as a cleaning slot. This slot is used for storing media cleaner that the drive picks up from this slot. In various libraries, DPM does not see this slot as present and therefore will not be able to access any media or cleaner that is in the slot. This feature is implemented in the library firmware, and DPM does not use them for drive cleaning. |
DPM has its own "Drive Cleaning Logic" that detects a dirty drive; therefore, we recommend that you disable "Setting the Cleaner Slot" from the library panel before using the library. |
Assorted tape libraries |
DPM is unable to map tape drives that belong to assorted tape libraries. This causes the tape drives to appear outside the tape libraries as stand-alone tape drives. |
To remap the tape drives, we recommend that you perform the procedures in "Remapping Tape Drives" in the DPM 2007 Operations Guide (https://go.microsoft.com/fwlink/?LinkId=66738). |
ADIC Scalar 100, 1000, i500, i2K |
DPM does not detect non-barcoded media that is kept inside the ADIC Scalar 100, 1000, i500, and i2k tape libraries. |
We recommend that you use only barcoded media on ADIC Scalar 100, 1000, i500, and i2k tape libraries. |
Compaq 20/40 GB DLT tape drive |
Detailed inventory on a blank tape shows the tape as Unknown. |
To use the tape mark it as Free using the Set-Tape cmdlet in DPM 2007 Management Shell. |
Dell PowerVault 120T |
The cleaning drive does not work on this library. The library detects the mounted cleaning drive as DLT media. |
We recommend that you use the library panel to clean the tape drive. Do not use DPM to clean the tape drive. |
Dell PowerVault 136T |
DPM does not detect non-barcoded media that is kept inside the Dell PowerVault 136T tape library. |
We recommend that you use only barcoded media on Dell PowerVault 136T tape libraries. If non-barcoded media is required, you must enable "Touch On Init" using the library panel. |
Exabyte Autopak 1x7 tape autoloader |
When there is media in the tape drive, a Fast Inventory returns a stale state of the slot and drive occupancy. For example, new media that has been added to the library might not show as being in the library. Because this is a single drive tape library, the only time this occurs is when the user inserts media into the tape drive when it is loaded and being used to archive data. |
We recommend that you do not handle the library (import and export media) when the library is actively in use. DPM will correct the stale state after the library is idle again. |
Exabyte libraries with Mammoth tape drives, such as Exabyte 215M, Exabyte 430M, and Exabyte EZ-17 |
During a fast inventory operation, the tape library sporadically reports that media is in the tape drive when no media is present. Therefore, DPM does not use the tape drive or tries to dismount the non-existent media into a slot, which results in an error. |
There is no resolution for this tape library with Mammoth tape drives. |
HP DAT72 tape drive Driver/Firmware revisions: hpdat.sys, |
DPM does not detect the media in the tape drive if you use the hpdat.sys driver, which is the driver shipped by Hewlett Packard. |
We recommend that you use the 4mmdat.sys driver that comes with Windows Server 2003. Note The 4mmdat.sys driver does not report that it supports the HP DAT72 tape drive. However, it does work and therefore you will need to force this driver on the tape device. |
NEC N8160-67 |
DPM reports that the library has a barcode reader; however, it does not detect the media barcodes. |
Use DPM with the NEC N8160-67 tape library with non-barcoded media. |
Overland PowerLoader |
DPM might lose barcode information on tapes that are mounted in a tape drive. |
Dismount the tape, and then perform an inventory using the Fast Inventory option on the tape library. A fast inventory will read the barcode for each tape in the library. |
Qualstar RLS Series |
The tape library does not retract its IEPort even though it reports Changer Controlled. Note This issue exists in all Qualstar RLS Series tape libraries. |
There is no resolution for this RTM release of DPM 2007. |
Qualstar RLS, TLS, and XLS Series |
When the user accesses the IEPort of the tape library, the library reports "Device Not Ready" or "Device Door Open". This results in the failure of other library operations while the user accesses the IEPort. This can cause a degradation of other library operations. Note This issue exists in all Qualstar RLS Series tape libraries. |
We recommend that you do not access the IEPort of the tape library while other library operations are occurring. Otherwise, you might experience a degradation of your library operations. |
Quantum Benchmark VS640 DLT |
DPM lists multiple entries for different media types. For example, a cleaning media label might be repeated three to four times in the Management task area on the Library tab. |
No resolution for this RTM release of DPM 2007. |
Quantum PX502, Quantum M1500, M1800 |
When the user accesses the IEPort of the tape library, the library reports "Device Door Open". This results in the failure of other library operations while the user accesses the IEPort. This can cause a degradation of other library operations. |
We recommend that you do not access the IEPort of the tape library while other library operations are occurring. Otherwise, you might experience a degradation of your library operations. |
Sony TSL SA300C/SA400C/SA500C |
The tape library automatically dismounts the media in the tape drive when DPM performs a fast inventory operation. This can cause potential problems if the media is dismounted while a write is in progress on any media in the drive. |
There is no resolution for this tape library. |
Spectralogic 2K |
If a library magazine is removed, the library reports the magazine slots as empty instead of absent from the library. |
We recommend that you do not remove any magazines from the library. |
Spectralogic sl2MC |
DPM is unable to match the sl2MC.sys driver to support the Spectralogic tape library. |
We recommend you use the spectramc.sys driver. |
Sun StorageTek SL500 |
DPM does not detect non-barcoded media that is kept inside the Sun StorageTek SL500 tape library. |
We recommend that you use only media that is barcoded on the Sun StorageTek SL500 tape library. |
I/O device errors during tape backups
The I/O device error DPM encountered a critical error while performing an I/O operation on the tape <Tape Name> in drive <Drive Name> can occur because of the following reasons:
Bad tape or bad sector on tape.
Bad drive or drive is dirty. Cleaning the drive will solve the problem.
When the media reaches the end, a few drivers incorrectly return "Device I/O error" instead of "End of tape reached" error.
You can solve this problem by creating the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent] "TapeSize"=dword:<Value in MBs>.
If the tape size is not set, it defaults to 30 GB.Some tape drives have trouble handling multiple queue buffers.
You can solve this by reducing the buffers that DPM uses by setting the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent] "BufferQueueSize"=dword:00000001.