Backup devices are an important part of guaranteeing data availability at a corporate site. Windows 2000 Server includes a graphical tool named Backup that supports backup of Windows 2000 Server-based data.
If a backup device is provided in a server system, it must comply with the requirements and recommendations in this section.
195. System includes device for local backup
Recommended
System administrators will commonly want offline backup capabilities to be available. If a backup device is provided with a server system, either as a built-in or peripheral add-on device, it must meet the minimum requirements defined in this section.
|
Windows 2000 Server
|
Advanced Server, Datacenter Server
|
Small Business Server
|
Basic Server:
|
10 GB required
|
10 GB required
|
10 GB required
|
Enterprise:
|
20 GB required
|
20 GB required
|
20 GB required
|
SOHO:
|
10 GB required
|
10 GB required
|
10 GB required
|
Minimum uncompressed, formatted storage capacity is required for any backup device designed to comply with these guidelines.
Recommendation
Recommended: 20 GB minimum capacity for Basic and SOHO servers.
197. Backup device meets industry standards
Required
A SCSI tape or SCSI backup peripheral must comply with the appropriate SCSI command set and with the requirements defined in “SCSI Controllers and Peripherals” earlier in this chapter.
ATA is not recommended for servers, but if an ATA backup peripheral is implemented, it must comply with the appropriate ATA/ATAPI 5 standard sections covering that device’s operation.
198. Driver integrated with Removable Storage Manager
Required
For a backup device designed for Windows 2000 Server, the manufacturer must provide a Windows 2000 driver that integrates with Removable Storage Manager (RSM), formerly Windows NT Media Services. This ensures that applications which are RSM-aware (such as the native Windows 2000 backup and hierarchical storage management applications) will be properly able to utilize the backup device.
RSM is intended to allow software that accesses backup devices to be independent of the specific device. A hardware vendor can also choose to include a backup application. However, such software should also be integrated with and use the RSM infrastructure.
Media Changers
This section defines requirements for media changers.
CD Changers
This section provides requirements for CD changers.
There is no requirement or recommendation for providing a CD changer with a server system, but if present or designed to be compatible with Windows 2000, it must comply with these requirements.
199. If present, CD changer for seven or fewer discs meets MMC-2 standard
Required
If an ATAPI-compatible CD changer is present that has a capacity for seven or fewer discs, the device must comply with MMC-2 standard.
Tape and Optical Disk Changers
This section provides requirements for tape and optical disk changers. There is no requirement or recommendation for providing a tape or optical disk changer, but if a device is present or is designed to be compatible with Windows 2000, it must meet the requirements defined in this section.
This includes changers that support the following drive/media types:
-
3.5 inch, 5.25 inch, and 12 inch magneto-optical or phase-change drives and media
-
All magnetic tape drives and media
It does not include changers that support CD ROM, CD R, CD RW, or DVD drive/media types.
200. SCSI changer and drive support auto-configuration
Required
To meet requirements for auto-configuration of changers and their associated drives, the following changer requirements and configuration restrictions are defined:
-
For changers where autoconfiguration under RSM control is a targeted feature, all changer tape or optical disk drives must be connected to the same SCSI bus as the changer.
Changer systems that are not configured this way will not be autoconfigurable under RSM in Windows 2000 and must provide documentation that describes the appropriate manual configuration process for use with RSM. Examples of proper documentation are available in Appendix A of Windows NT Removable Storage Manager Programming Documentation, at http://www.highground.com/developer/documents/ntmsdocu.htm.
The Removable Storage Manager functions are documented in the Microsoft Platform SDK at http://msdn.microsoft.com/library/psdk/zaw/ntms_api_5nz9.htm.
-
The changer’s Read Element Status–Data Transfer Element Descriptor must support the reporting of the SCSI Bus Address and LUN of each drive in the library unit.
-
If drive cleaning is required and can be automated, a specific slot that is accessible by way of a Move Medium command must be designated in the Operator’s Guide.
-
The changer must be able to report if a bar-code reader is installed in the unit.
-
The changer must be able to report on the current of (magazine) slots and drives by using the Read Element Status command.
Recommendation
Recommended for changers: SCSI changers should avoid behaviors as a side effect of SCSI bus reset which unduly delay operations of the changer and availability of media via the changer. An example would be a lengthy auto-inventory process which delays media loading.
Required
The following commands or features must be supported by the changer:
-
Initialize Element Status (with/without bar-code reading)
-
Mode Sense—Pages 1D, 1E, 1F
-
Move Medium
-
Prevent/Allow Media Removal (door access and IEPORT locking)
-
Read Element Status
-
Reserve, Release
-
Send Volume Tag, Request Volume Element Address
-
Test Unit Ready, Request Sense, Inquiry
Recommendation
Recommended: Inquiry with support for reporting serial number or other unique unit ID should be supported by the changer.
Chapter 6
Physical Design and Hardware Security Requirements
This chapter summarizes physical design and hardware security requirements and recommendations.
Share with your friends: |