Chat now with support
Chat with Support

DR Series DR2000v - Deployment Guide

Specifications and notes for using the DR2000v

This section describes special notes on usage, licensing information, GUI usage limitations, and latest driver downloads for the DR2000v system.

* 
NOTE: For detailed information about supported virtual machine platforms and versions, platform configuration limits, virtual infrastructure and memory requirements, and other related system information, see the DR Series System Interoperability Guide.

Virtual Tape Library

Virtual Tape Library (VTL) support is available on the DR2000v in demo mode for trial and proof of concept only. To learn more about this functionality, contact your sales representative to request a VTL demo license for the DR2000v. To download the trial version, visit the following link: https://www.quest.com/products/dr2000v-virtual-backup-appliance/software-downloads.asp

Licensing

The DR2000v uses a standalone license.

* 
NOTE: The DR2000v 30-day trial version does not require a license to be installed on a DR Series hardware system for operation.

DR2000v Hyperscale licensing

VM Hyperscale licenses are deployed on the DR Series appliance to support and maintain multiple virtual DR2000v appliances that are licensed by a single DR Series hardware system. A DR Series hardware system can support up to 3,000 virtual machines.
* 
NOTE: A DR Series hardware system with a Hyperscale license can function as a regular DR Series system.

For more information on DR2000v license limits, see the DR Series System Interoperability Guide. For more information about DR2000v Hyperscale licensing, contact your sales representative or Quest support.

DR2000V VM cloning and importing/exporting

When cloning or importing/exporting a VM, a cloned VM requires a new license. Contact Quest support for assistance.

DR Series system GUI usage

Refer to the following notes about GUI usage specific to the DR2000v.

•
You should not change the MTU setting for the DR2000v but should leave the setting at the system default of 1500.
•
The DR Series system GUI Usage menu displays only statistics related to DR2000v; no underlying hosting virtual machine platform information is available through this menu.
•
DR Series system alerts and events are applicable only to DR2000v; no underlying hosting virtual machine platform alerts/events are handled.
•
The DR2000v system is a Global View-managed unit, which means it can be added to the Global View of your DR Series hardware system.
•
Hardware Health is not displayed in the GUI for the DR2000v as this is managed via the hosting platform.

NIC drivers and settings

Hyervisor host NIC driver updates for VMQ
DR2000v NIC settings

Refer to the following topics for important information about NIC driver updates for your hypervisor host and NIC settings for the DR2000v.

Hyervisor host NIC driver updates for VMQ

Before deploying the DR2000v, you may need to update certain hypervisor host NIC drivers to support the VMQ feature. Check your Hypervisor host NIC feature list and update the driver to the latest version as needed. For example, you should update the Broadcom NetXtreme I and NetXtreme II Ethernet adapter driver to 17.6.0 (or later) to add VMQ support; otherwise, you might experience performance degradation during normal operations. Refer to the following links for downloading:

•
Driver for NetXtreme I and NetXtreme II Ethernet adapter:

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=CYKKJ&osCode=MWS80&fileId=3197327398&languageCode=EN&categoryId=NI

•
Firmware for NetXtreme I and NetXtreme II Ethernet adapter:

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=P32M4&osCode=MWS80&fileId=3197328666&languageCode=EN&categoryId=NI

DR2000v NIC settings

The DR2000v is designed to work with two virtual NICs. Internally, the DR2000v bond’s both the NICs to be Transmit Load Balancing (TLB), which requires the eth-0 MAC address for the ethernet traffic. For the DR2000v appliance to work properly, you should ensure the following settings:

1.
Ensure that the eth-0 NIC is always connected to a valid Hypervisor Virtual Switch topology.
2.
Ensure that eth-0 line is always up and running.
3.
Enabling the eth-1 is optional, but if you enable it:
a.
Ensure the virtual switch settings MAC address changes and Forged Transmits are set to Accept, if you are planning to use eth-1 in an ESXi hypervisor environment.
b.
Ensure the eth-1 interface is not connected if you do not have the administrator privileges.
4.
If you are making any network setting changes on your hypervisor, execute the stats –network CLI command to list all the NIC ports status, especially with the Rx/Tx counts.
5.
If the eth-1 “Rx” counters are not getting incremented, but the “Tx” counters are getting incremented, then you might have a problem with your switch settings, where the return traffic is getting dropped by your Hypervisor vSwitch. To resolve this, see Step 3 above.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating