1. Manuals
  2. Brands
  3. Dell Manuals
  4. UPS
  5. PowerVault DR4100
  6. Best practices manual

Dell DR4100 Best Practices Manual

Backup and recovery appliance
Hide thumbs Also See for DR4100:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual, Reference Manual
DR4100 Best Practice Guide
Part 1: Setup, Replication and Networking
Dell Data Protection Group
April 2014
A Dell Technical White Paper

Advertisement

Table of Contents
loading

Related Manuals for Dell DR4100

Summary of Contents for Dell DR4100

  • Page 1 DR4100 Best Practice Guide Part 1: Setup, Replication and Networking Dell Data Protection Group April 2014 A Dell Technical White Paper...

  • Page 2: Revisions

    Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and/or names or their products and are the property of their respective owners. Dell disclaims proprietary interest in the marks and names of others.

  • Page 3: Table Of Contents

    Networking ....................................16     Supported Network Cards ..............................16     Network Interface Card Bonding ............................17     Secure Network Separation ..............................19     Troubleshooting .................................. 40     Resources ..................................... 41 DR4100 Best Practice Guide | April 2014...

  • Page 4: Executive Summary

    Executive summary This document contains some of the best practices for deploying, configuring, and maintaining a Dell DR 4x00 backup and deduplication appliance in a production environment. Following these best practices can help ensure the product is optimally configured for a given environment.

  • Page 5: Administration Guides

    Administration guides Dell DR Series System Administrator Guide Dell DR4100 Systems Owner’s Manual Dell DR Series System Command Line Reference Guide DR4100 Best Practice Guide | April 2014...

  • Page 6: Best Practice Guides

    Best Practices for Setting up NetVault SmartDisk DR4X00 Disk Backup Appliance Setup Guide for CommVault Simpana 10 Setting up EMC Networker on the Dell DR4X00 Disk Backup Appliance Through CIFS Setting up EMC Networker on the Dell DR4X00 Disk Backup Appliance Through NFS...

  • Page 7: Case Studies

    Case studies Haggar Case Study CGD Case Study TAGAL Steel Case Study DCIG DR4X00 and EqualLogic Better Together ESG DR4X00 Lab Validation Pacific BioSciences Case Study DR4100 Best Practice Guide | April 2014...

  • Page 8: System Setup

    • Setting up alerts: The DR product has built in monitoring through Dell Open Manage which is installed on the appliance. All critical software and hardware alerts are sent as alerts via email. All hardware related events are also sent as a trap over SNMP to the configured monitoring server.

  • Page 9: Container Creation

    • Scenario 2: Separate data that has a higher value to replicate vs. lower value • Scenario 3: Separate different types of data into different containers • Scenario 4: Separate different DMA types into different containers DR4100 Best Practice Guide | April 2014...

  • Page 10: Access Protocols

    Scenario 4: Separate different DMA types into different containers 4.4.1.4 Robert also has a VM infrastructure that he wishes to protect using Dell vRanger. This is in addition to his other DMA which is used to protect their physical servers.

  • Page 11: Marker Support

    Note: Changing the marker type after data is ingested could make the data appear unique, causing dedupe savings to be adversely impacted until all ingested data with the previous marker is removed. To avoid this problem, the proper marker should be set on containers from the start. DR4100 Best Practice Guide | April 2014...

  • Page 12: Replication Setup And Planning

    The following sections cover the various considerations and planning that should be taken into account for replication with the DR4100 backup appliance. As always, the information provided below are guidelines and best practices and are meant to be supplemental to the information provided in the DR administration guide.

  • Page 13: Bandwidth Optimization

    Replication schedules can be set to ensure one container gets more time replicating (for high priority data) or to schedule replication to occur in off-peak hours, although in most situations it is recommended to leave the default settings and let replication transfer data as needed over the network. DR4100 Best Practice Guide | April 2014...

  • Page 14: Replication Encryption

    In such instances please contact the Dell Support department, and they will assist in custom tuning the window size for the particular link. Replication Tuning In some instances it may be beneficial to prevent replication from running all the time.

  • Page 15: Domain Access

    Note: CIFS and NFS protocol access is not synced between source and target DRs. It is not known what is at the remote site so these settings are not transferred. Before failing over, make sure the target DR is setup with the appropriate protocol access as required. DR4100 Best Practice Guide | April 2014...

  • Page 16: Networking

    The following sections define the various options and configurations associated with the DR4100, including steps to optimize the appliance to a given environment. As always, the information provided below are guidelines and best practices that are meant to be supplemental to the information provided in the DR administration guide.

  • Page 17: Network Interface Card Bonding

    Network interface card (NIC) bonding provides additional throughput and/or failover functionality in the event a link is lost. The DR4100 supports two bonding modes: dynamic link aggregation and adaptive load balancing (802.3ad and ALB). Each of these modes has their own advantages and disadvantages that should be considered before choosing a mode.
  • Page 18 By default, the DR4100 sets up bonding on its fastest interfaces. If the appliance is configured with NIC combo 3 (see Table 1) the 2x 10GB interfaces will become the new bond0. If the DR4100 is configured with combo 1, the 4x 1GB interfaces will become bond0.

  • Page 19: Secure Network Separation

    • Scenario 4: Multiple appliance replication • Scenario 5: Backup to different IPs on a single DR appliance Table 2 Traffic segmentation Segment Traffic Management GUI /Telnet/ SSH Replication Replication/OST Op-dupe Backup CIFS/NFS/RDA/OST DR4100 Best Practice Guide | April 2014...
  • Page 20 For Backup and Replication Traffic, static routes should be added to allow communication between the devices. Hardware configuration • DR1 – 2x 1GB interfaces and bond0 as 2x 10GB interfaces • DR2 – 2x 1GB interfaces and 2x 10GB interfaces DR4100 Best Practice Guide | April 2014...
  • Page 21 Configure the DR to use the 1GB interfaces as bond0 members and free the 10GB interfaces for backup traffic. Perform a factory reset of the network and then reboot the appliance: network --factory_reset --auto_bonding_speed_1G system –reboot DR4100 Best Practice Guide | April 2014...
  • Page 22 Speed :1000Mb/s   eth0 Duplex :Full   eth1 MAC : BC:30:5B:F3:22:75     eth1 Max Speed :1000baseT/Full     eth1 Speed :1000Mb/s     eth1 Duplex :Full           DR4100 Best Practice Guide | April 2014...
  • Page 23 Skipping DNS Update 10.250.240.4: IP already updated. Starting the filesystem...doneting down loopback interface: [ OK ] Create a single 1GB interface using the following command: network --create_eth --nwif< ehtN> --static --ip<ip address> --netmask<netmask> -- name <name> -- restart DR4100 Best Practice Guide | April 2014...
  • Page 24 Successfully added application telnet. Restarting telnet service ... done. b. Dedicate bond1 to CIFS and NFS backup traffic using the following commands: system --backup_traffic --add --type < NFS|CIFS|OST|RDS> --interface <bond(0-N) | eth(0-N) | lo#> DR4100 Best Practice Guide | April 2014...
  • Page 25 Follow steps 1-4 to configure the network interfaces for DR2. Setup static replication between DR1 and DR2 by running the following CLI command: replication --add --name backup --role source --peer DR2-replication --peer_name backup-from-DR1 DR4100 Best Practice Guide | April 2014...
  • Page 26 On DR-2 add a route from DR1-eth1 to DR2-eth1 using the following command: network --route --add --network <ip_address>--netmask <netmask> --gateway <gateway_address> -- interface <eth(0-N)> Example administrator@DR2 > network --route --add --network 10.250.243.222 --netmask 255.255.255.0 --gateway 10.250.243.100 --interface eth1 DR4100 Best Practice Guide | April 2014...
  • Page 27 Robert has a DR4100 with firmware 2.1, 2x 10GB interfaces and 2x 1GB interfaces. He wishes to use the 1GB interfaces for replication, management and OST traffic. He wants to use the 10GB interfaces for backup traffic only. Robert will need to do the following to accomplish his goals: •...
  • Page 28 :1000baseT/Full eth0 Speed :1000Mb/s eth0 Duplex :Full eth1 MAC : BC:30:5B:F3:22:75 eth1 Max Speed :1000baseT/Full eth1 Speed :1000Mb/s eth1 Duplex :Full Create a bond for the 2x 10GB interfaces using the following command: DR4100 Best Practice Guide | April 2014...
  • Page 29 Updating DNS entry for DR1.local to 10.250.xxx.x .. Skipping DNS Update 10.250.xxx.x: IP already updated. Use the instructions in Step # 4 in Scenario #1 to configure Management, Replication, and Backup OST traffic for the respective interfaces. DR4100 Best Practice Guide | April 2014...
  • Page 30 In order for the two DRs to replicate over the dedicated links, static routes should be provisioned in such a way that the replication flows over those paths. This is done in the steps below. DR4100 Best Practice Guide | April 2014...
  • Page 31 > network --restart administrator@DR2 > network --show Use the following commands to assign IP address to eth2 and eth3 on DR2: network --create_eth --nwif <eth0,eth2,ethN> --static --ip <ip_address> --netmask <netmask> network –show DR4100 Best Practice Guide | April 2014...
  • Page 32 Add route from DR1 eth2 to DR2 eth2 and from DR1 eth3 to DR2 eth3 using the following commands: network --route --add --network <ip_address> --netmask <mask> --gateway <gateway_ip> --interface <eth0,eth1,ethN> network --show –routes DR4100 Best Practice Guide | April 2014...
  • Page 33 172.20.20.2 --role source Note: If a replication pair does not already exist between DR1 and DR2, use the steps outlined in scenario 1 for assigning replication to designated interfaces and to create a replication pair. DR4100 Best Practice Guide | April 2014...
  • Page 34 6.3.1.6 Jose has one DR4100 appliance located at his Seattle site and two DR4100s located at his Lansing site. He wants to replicate data from his Seattle site (Seattle1) to his Lansing site (Lansing1). He would also like to replicate data backed up at Lansing1 to another site, Lansing2.
  • Page 35 --route --add --network <destination_network> --gateway <gateway addresses> --interface <bond(0-N) | eth(0-N) | lo#> Example     administrator@Lansing1 > network --route --add --network <Seattle’s 1G network> --     gateway <gateway addresses> --interface bond1     DR4100 Best Practice Guide | April 2014...
  • Page 36 <ip address | hostname> --encryption <none | aes128 | aes256> Example administrator@Lansing1 > replication --update --name <source-container-name> --role source --peer <IP of 10G Bond of Lansing2> --replication_traffic <IP of 10G bond of Lansing1> DR4100 Best Practice Guide | April 2014...
  • Page 37 • Upgrade the DR to firmware to 2.1. • Set the media server to use the two interfaces of the DR appliance. The DR4100 will be configured as follows: • 1G interfaces are not exposed pre 2.1 firmware upgrade • Bond0 will contain 2x10G interfaces •...
  • Page 38 Note: Take note of the DNS names for bond0 and for the configured 1GB interface. These DNS names are required to force traffic to the specified interface. Create two CIFS containers on the DR appliance. One container called cifs-container-1 and the other cifs- container-2. DR4100 Best Practice Guide | April 2014...
  • Page 39 Create a second storage unit with the UNC path to the DR’s second container. This time use the bond0’s name in the UNC path \\dr-bond0.local\cifs-container-1 Note: Note that the two storage units do not have to point to separate containers. DR4100 Best Practice Guide | April 2014...

  • Page 40: Troubleshooting

    Testing connection to port 9915... Connected! Testing connection to port 9916... Connected! Replication troubleshooting completed successfully - Connection to all ports is OK! Make sure the management interface is up and reachable by using the following command: telnet<manamgent_ip> DR4100 Best Practice Guide | April 2014...

  • Page 41: A Resources

    Resources DR Series Manuals http://www.dell.com/support/Manuals/us/en/19/product/powervault-dr4100 Dell Support http://support.dell.com Dell TecCenter http://en.community.dell.com/techcenter/ DR4100 Best Practice Guide | April 2014...

Table of Contents