Converse agora com nosso suporte
Chat com o suporte

DR Series Software 4.0 - Administrator Guide

Introducing the DR Series system documentation Introducing the DR Series system Setting up the DR Series system Configuring the DR Series system settings Managing containers Managing replications Monitoring the DR Series system Using GlobalView Configuring and using Rapid NFS and Rapid CIFS Configuring and using Rapid Data Access with NetVault Backup and with vRanger Configuring and using RDA with OST
Understanding RDA with OST Guidelines Terminology Supported RDA with OST software and components Best Practices: RDA with OST and the DR Series System Setting client-side optimization Configuring an LSU Installing the RDA with OST plug-in Configuring DR Series system information using NetBackup Backing Up Data From a DR Series System (NetBackup) Using Backup Exec with a DR Series system (Windows) Understanding the OST CLI commands Understanding RDA with OST Plug-In Diagnostic Logs Collecting Diagnostics Using a Linux Utility Guidelines for Gathering Media Server Information
Configuring and using VTL Configuring and Using Encryption at Rest Support, maintenance, and troubleshooting Supported Ports in a DR Series System

Configuring networking settings

Configuring networking settings

In the DR Series system GUI, you can view and modify the network settings (for example, if you want to change the settings you configured when you first initialized the system)

To view and modify networking settings, complete the following steps.

1.
In the left navigation menu, click System Configuration > Networking.
The Networking page is displayed.
2.
Under Hostname, you can view the following settings.
◦
Hostname
▪
Hostname (FQDN)
▪
iDRAC IP Address
◦
DNS
▪
Domain Suffix
▪
Primary DNS
▪
Secondary DNS
3.
To edit the Hostname or DNS settings, in the Action menu in the upper right corner of the page, click Edit.
a.
In the Hostname field, modify the hostname as needed. The hostname entry must meet the following requirements:
▪
Alphabetic—allows A-Z, a-z, or a combination of upper and lower case alphabetic characters.
▪
Numeric—allows numerals zero (0) through 9.
▪
Special characters—allows only the dash (-) character.
▪
Length limit—hostnames cannot exceed the maximum length of 19 characters.
b.
Modify the DNS fields as needed (Domain Suffix, Primary DNS, Secondary DNS).
▪
Domain Suffix — enter a domain suffix to use. For example, acme.local. This is a required field.
▪
Primary DNS—enter an IP address that represents the primary DNS server for your system. This is a required field.
▪
Secondary DNS—enter an IP address that represents the secondary DNS server for your system. This is an optional field.
c.
Click Save.
4.
Under Interfaces, you can view the following columns of information for a selected NIC bond or Ethernet port.
◦
Device—The name of the device.
◦
Enabled—Yes or no.
◦
IP Address—The IP address of the NIC bond or Ethernet port.
◦
MAC Address—The IP address of the NIC bond or Ethernet port.
◦
MTU—The Maximum Transmission Unit setting. (The MTU setting accepts values between 512 and 9000.)
◦
Traffic—The type of traffic as Replication, Management, Backup, and Opdup.
You can click the Device to expand to view more details, such as the interface name, mode, member interfaces, netmask address, gateway address, bonding option, NIC, MAC, maximum speed, and duplex.
5.
To modify settings for a selected interface (NIC bond or Ethernet port), in the Action column, click the Edit icon.
a.
In the Edit Interface pane, for IP Mode, select Static (to set static IP addressing for your system) or DHCP (to set dynamic IP addressing for your system).
b.
If you selected Static for the IP Mode, enter the IP , Netmask, and Gateway addresses. (the system IP address and netmask identify the network to which your system belongs).
c.
For MTU, enter a number to set as the maximum. (The MTU setting accepts values between 512 and 9000.)
 
NOTE: Ensure that the value that you enter in MTU is the same for the clients, Ethernet Switch, and the appliance. The connection between the clients, the Ethernet switches, and the appliance will break if the MTU number is not the same on all the components.
 
NOTE: In computer networking, jumbo frames are Ethernet frames with more than 1500 bytes of payload (but in some cases, jumbo frames can carry up to 9000 bytes of payload). Many Gigabit Ethernet switches and Gigabit Ethernet network interface cards support jumbo frames. Some Fast Ethernet switches and Fast Ethernet network interface cards also support jumbo frames. Some computer manufacturers use 9000 bytes as the conventional limit for jumbo frame sizes. To support jumbo frames used in an Internet Protocol subnetwork, both the host DR Series system (initiator or source) and the target DR Series system have to be configured for 9000 MTU.
NOTE: Consequently, interfaces using a standard frame size and those using the jumbo frame size should not be in the same subnet. To reduce the chance of interoperability issues, network interface cards capable of supporting jumbo frames require specific configurations to use jumbo frames.
NOTE: To verify that the destination system can support a specific frame size, use the DR Series system CLI command network --ping --destination <IP address> --size <number of bytes>. For more information, contact Technical Support for assistance.
 
NOTE: Make sure that if you are using any Dell network switches that you take full advantage of the latest switch firmware upgrades and application notes. The application notes provide procedures that assist you in performing switch firmware upgrades and saving configuration files (for complete details, see support.dell.com/ and navigate to Drivers and Downloads for your system type).
 
NOTE: When setting or changing the MTU value, make sure that you verify that the Ethernet network switch is capable of supporting an MTU size that is equal to or larger than the value you are setting. Any mismatch in MTU values between the clients, Ethernet network switch, and the DR Series system appliance will make it inoperable.
d.
In the Bonding Configuration drop-down list, select one of the following bonding configurations.
▪
ALB—Configures adaptive load balancing (ALB), which is the default setting.
 
NOTE: ALB load balancing does not balance the load properly when your backup servers are on a remote subnet. This is because ALB uses the address resolution protocol (ARP) and ARP updates are subnet-specific. Because this is the case, ARP broadcasts and updates are not sent across the router. Instead, all traffic is sent to the first interface in the bond. To resolve this ARP-specific issue, make sure that your data source systems reside on the same subnet as the DR Series system.
▪
802.3ad—Configures dynamic link aggregation using the IEEE 802.ad standard.
 
CAUTION: If you change the existing bonding setting, the connection to the DR Series system may be lost unless you are sure that the system can accept this bonding type.
e.
Click Save.
6.
Under Bandwidth Limits, you can view the following columns of information, which represent network bandwidth for replication connections:
◦
Target System—The DR Series system to which network traffic is being sent.
◦
Target IP—The IP address of the DR Series system to which network traffic is being sent.
◦
Bandwidth Limit—This limit is shown in KBps, MBps, or GBps and represents the user-set value of the Max Speed.
7.
To modify Bandwidth Limit settings, in the Action column, click the Edit icon.
a.
In the Edit Bandwidth Limit pane, for Bandwidth Speed Rate, select Unlimited or Limited.
b.
If you select Limited, for Bandwidth Speed Value, enter a number for the bandwidth speed, and then select KBps, MBps or GBps from the drop-down list.
c.
Click Save.
 
 
Parent topic 

Understanding the networking page and Ethernet port values

Understanding the networking page and Ethernet port values

In the DR Series system GUI, the Networking page displays the currently configured multiple Ethernet ports for the DR Series system in the Interfaces list. For 1–Gigabit Ethernet (GbE) ports in the DR4000 system this could be Eth0, Eth1, Eth2, and Eth3, and in the DR4100 system this could be Eth0, Eth1, Eth2, Eth3, Eth4, and Eth5. For 10-GbE/10-GbE SFP+ NICs, this means that the two ports are bonded together into a single interface. For example, the DR Series system port configuration is as follows:

In a 1-GbE NIC configuration: the DR4000 system supports up to four 1–GbE ports, which consists of up to two internal LAN on Motherboard (LOM) ports and two ports on an expansion card that are bonded together. The DR4100 system supports up to six 1–GbE ports, which consists of up to four internal LOM ports on the network daughter card (NDC) and two ports on a PCI Express expansion card.
•
In a 10-GbE or 10-GbE SFP+NIC configuration: the DR4000 system supports up to two 10–GbE or 10–GbE SFP+ ports on an expansion card that are bonded together. The DR4100 system supports up to two 10-GbE or 10-GbE SFP+ ports that reside on the NDC that are bonded together.
 
NOTE: For more information on advanced networking options see the DR Series Command Line Interface Reference Guide available at support.quest.com/dr-series by selecting your specific DR model and then navigating to Technical Documentation.

The ports for bonded NICs display: MAC address, port speed in megabtyes per second (MB/s), maximum speed, and duplex setting. The following example shows Ethernet port values for the four ports in a 1-GbE NIC bonded configuration on a DR4000 system:

Eth0:

•
MAC: 00:30:59:9A:00:96
•
Speed: 1000Mb/s
•
Max Speed: 1000baseT/Full
•
Duplex: Full

Eth1:

•
MAC: 00:30:59:9A:00:97
•
Speed: 1000Mb/s
•
Max Speed: 1000baseT/Full
•
Duplex: Full

Eth2:

•
MAC: 00:30:59:9A:00:98
•
Speed: 1000Mb/s
•
Max Speed: 1000baseT/Full
•
Duplex: Full

Eth3:

•
MAC: 00:30:59:9A:00:99
•
Speed: 1000Mb/s
•
Max Speed: 1000baseT/Full
•
Duplex: Full
Parent topic 

Understanding system operation scheduling

Understanding system operation scheduling

Configuring replication schedules

By scheduling system operations, you can optimize your system resources and achieve the best possible DR Series system performance. The most important thing to remember when scheduling critical DR Series system operations is that you want to ensure that you perform each of these operations at a time when it will not overlap or interfere with the running of any of the other key system operations.

You should carefully plan and schedule time periods in which to perform the following critical system operations:

•
Data ingests (which are dependent upon your usage of your DMA(s))
•
Replication
•
System cleaner (space reclamation)
 
NOTE: Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from system containers in which files were deleted as a result of deduplication.

In the DR Series system, the main goal in planning and scheduling operations should be to run the Cleaner and Replication operations at times when they do not overlap or interfere with other important system operations. You want to make sure that by properly scheduling and planning, your system can perform each of these key operations independent of the other.

The best practice is to run these two operations during non-standard business hours, so that they do not conflict with any of your other backup or ingest operations.

To view currently scheduled operations and to access the Schedules page to configure system schedules, follow these steps.

•
On the left navigation menu, click System Configuration > Schedules.

The Schedules page is displayed, showing a daily/hourly calendar representation of currently scheduled operations.

 
 
Parent topic 

Configuring cleaner schedules

Configuring cleaner schedules

Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from the system. The recommended method is to schedule a time when you can run the Cleaner on your DR Series system with no other planned processes running.

 
NOTE: Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed, the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest was completed, and that the Replication process is not running (the Cleaner process runs as a lower system priority operation than the Replication process).
 
NOTE: Running the Cleaner while ingesting data reduces system performance. Ensure that you schedule the Cleaner to run when backup or replication is not in progress. For more information about best practices for using the system cleaner, refer to the DR Series System Cleaner Best Practices white paper for your specific DR Series system at support.quest.com/DR-Series.

To schedule cleaner operations on your system, complete the following steps.

1.
On the left navigation menu, click System Configuration > Schedules.

The Schedules page is displayed, showing a weekly/daily calendar representation of currently scheduled operations.

2.
To add a cleaner schedule, on the Action menu in the upper right corner of the page, select Add Cleaner Event.
a.
In the Cleaner pane, select a day from the Set Event At Day drop-down list.
b.
In the From and To drop-down lists, select the time (hour) of the day for the cleaner to run.
c.
Click Save.
 
NOTE: Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed, the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest was completed, and that the Replication process is not running (the Cleaner process runs as a lower system priority operation than the Replication process).
 
NOTE: You can also use the DR Series system command line interface (CLI) to create, view, and delete the cleaner schedule. The available commands are:
schedule --add --day <Day of the Week> --start_time <HH:MM> --stop_time <HH:MM> --cleaner
schedule --show --cleaner
schedule --delete --day <Day of the Week> --cleaner
NOTE: For full details on running the cleaner schedule commands, help is available by entering:
schedule --help
3.
To run the cleaner now, on the Action menu in the right corner of the page, select Run Cleaner Now.
Viewing cleaner status

The current Cleaner Status is shown at the top of the Schedules page as one of the three following states:

•
Pending—displays any scheduled window for the Cleaner operation.
•
Running—displays when the Cleaner operation is running.
•
Idle—displayed only if there is no Cleaner operation running.

On the Dashboard page, you can also view a graph of cleaner statistics.

•
In the Action menu in the upper right corner, click Detailed Graphs, and then click the Cleaner tab.
 
 
Parent topic 
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação