Hunterlog961

Microsoft Data Protection Manger does not support external hard drives. You’re choices are to backup to disk and copy to external later, backup to SAN/DAS, or backup to tape drive.

From a Technet DPM FAQ:

Storage Pool Configuration
What types of storage can I use with DPM 2007?

• It was discovered the Hyper-V Replica Broker will still use DNS to resolve the names of each Hyper-V host and as a result will still resolve the Parent Network IP Address. The only option is to update the C: windows system32 drivers etc hosts file to include the replica network IP address on EVERY SINGLE HYPER-V Host.
• Dump report and resolution on the Blue Screen of Death (BSOD) issues, which have impacted previous Intel® Rapid Storage Technology (Intel® RST) drivers from.

Last post by nospam@cristalink.com Fri, 05 Nov 2004 04:36:53 GMT; Does usbcamd mini driver support mulitple interface device? By Jackal Huang » Mon, 04 Oct 2004 12:41:18 GMT 3 Replies 142 Views Last post by Jackal Huang Wed, 06 Oct 2004 12:41:18 GMT; DRIVERVERIFIERDMAVIOLATION in usbport.sys by U2thcmFtdXNoLkdN » Wed, 20 May 2009 16:35:01 GMT.

DPM 2007 supports use of any of the following sources for server storage:
* Direct attached storage (DAS).
* Fibre Channel storage area network (SAN)
* Internet SCSI (iSCSI) storage device or SAN, providing that the iSCSI storage device has received Windows Hardware Certification.

For many small businesses a tape library or a SAN solution is out of the IT budget.The need is still exists for an off site backup. There are two options to get around this and they are:

1. There is a utility that allows you to configure an external hard drive as a tape drive. This makes DPM think the external hard drive is a tape drive. This application is called Firestreamer. Firestreamer creates a Virtual Tape Library from your external hard drives. You can download a 3 month trial of this utility here: http://www.cristalink.com

2. You can go with external e-Sata drives. DPM will not know the difference between an internal sata drive and an external e-sata drive.

NOTE:Microsoft does not support backing up to external USB drives using DPM. I am not sure if they support backing up to external e-Sata drives.

Starting with Windows 10, Version 2004 (OS build 19041.488 or higher), two additional identifiers are available for NVMe storage disk drives which support the STOR_RICH_DEVICE_DESCRIPTION structure:

SCSIt*v(8)p(40)

Where:

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(40) is a 40-character product identifier

SCSIt*v(8)p(40)r(8)

Where:

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(40) is a 40-character product identifier

• r(8) is an 8-character revision level value

In versions of Windows prior to Windows 10, Version 2004 (OS build 19041.488 or higher), the device ID format for a small computer system interface (SCSI) device is as follows:

SCSIt*v(8)p(16)r(4)

Where:

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(16) is a 16-character product identifier

• r(4) is a 4-character revision level value

The bus enumerator determines the device type by indexing an internal string table, using a numerically encoded SCSI device type code, obtained by querying the device, as shown in the following table. The remaining components are just strings returned by the device, but with special characters (including space, comma, and any nonprinting graphic) replaced with an underscore.

The SCSI Port driver currently returns the following device type strings, the first nine of which correspond to standard SCSI type codes.

An example of a device ID for a disk drive would be as follows:

SCSIDiskSEAGATE_ST39102LW_______0004

Drivers Cristalink Scsi Command

There are four hardware IDs in addition to the device ID:

SCSIt*v(8)p(16)

SCSIt*v(8)

SCSIv(8)p(16)r(1)

V(8)p(16)r(1)

In the third and fourth of these additional identifiers, r(1) represents just the first character of the revision identifier. These hardware IDs are illustrated by the following examples:

SCSIDiskSEAGATE_ST39102LW_______

SCSIDiskSEAGATE_

SCSIDiskSEAGATE_ST39102LW_______0

SEAGATE_ST39102LW_______0

The SCSI Port driver supplies only one compatible ID, one of the variable-sized generic type codes from the previous table.

Drivers Cristalink Scsi Drive

For example, the compatible ID for a disk drive is as follows:

GenDisk

Drivers Cristalink Scsi & Raid Devices Download

The generic identifier is used in INF files for SCSI devices more than any other, because SCSI drivers are typically generic.

Drivers Cristalink Scsi & Raid Devices List

Be aware that the SCSI Port driver returns no generic name for sequential access and 'processor' devices.