Professional Documents
Culture Documents
Page 4
Page 4
Page 4
Page 4
Page 5
Page 5
Page 6
Page 6
Identifying Bottlenecks
Page 6
Related Documentation
The Documentation page at https://my.datadomain.com/documentation provides
access to documents that have information related to use of this application with Data
Domain products. Be sure to read the Data Domain Operating System User Guide and
release notes, under Product Documentation. Also be sure to read the Data Domain
integration guide or application introduction for your backup application.
Also refer to the following Microsoft documents:
Name
Type
Tcp1323Opts
REG_DWORD
Name
Type
TCPWindowSize
REG_DWORD
TcpTimedWaitDelay REG_DWORD
30
Use the Windows Performance Monitor (perfmon) to test system performance. In the
Performance Monitor, you can choose:
The default view of the data is a real-time line chart. However, you can log or format
the data as reports and generate alerts when counters reach specified limits.
Use a tool such as the freeware application Lmdd.exe to determine the baseline
performance of the network between the client and the backup server, or between the
backup server and the Data Domain system. Data Domain also recommends Iometer
and Iperf.
Use a network sniffing application to monitor network data and detect the
bottlenecks. Data Domain recommends the Microsoft Network Monitor (netmon)
application or the freeware application Ethereal.
3. Use Data Domain system autosupport reports and the output of the DD OS command
system show performance can help you locate the bottleneck. The autosupport
report includes historical data on the transfer rate and system load.
Identifying Bottlenecks
Systematically eliminate as many factors as possible to isolate the root cause of the
problem. First, determine whether the problem lies in the Data Domain system or
outside. Search for performance bottlenecks in the following sequence:
1. Data Domain system
2. Application (backup) server
3. Network
4. Hardware
5. Client
The following sections give troubleshooting tips for the first three of these possible
sources. To troubleshoot hardware and client problems, see the vendor documentation
for those products.
0%
0%
35%
48%
34%
38%
29%
30%
V
V
0
0
1433
1746
1597
1624
1246
976
0%
0%
97%
98%
95%
99%
95%
98%
0%
0%
1%
1%
1%
1%
1%
1%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
2%
5%
4%
0%
4%
1%
0
0
30
32
50
60
52
66
1
0
0
2
1
1
3
1
2. From the Windows server, manually map a drive to the Data Domain share /backup
as drive Z.
the Windows server to create a 10 GB file of zeros on Data Domain share via drive Z:
CMD:c:\lmdd.exe if=/dev/zero of=z:\allzero bs=32768 count=327680
The output on the Data Domain system shows the transfer rate for each interface in
KB/s. One lmdd thread should provide 50 MB/s. Running three lmdd instances
concurrently should fully utilize a gigabit link at about 110 MB/s.
4. Examine the NFS proc, recv, send, and idle columns. In the example in Step 1, the
5. Check the State column to rule out normal system maintenance activity as the cause
Details
Cleaning
Degraded RAID
Verify data
6. If the system State does not explain the bottleneck as a temporary problem, use
Possible Sources of
the Bottleneck
Troubleshooting Suggestions
Network
Backup server
Backup server clients
Network
Backup server
Backup server
Backup server
7. If you determine that there is a problem with the Data Domain system, generate a
support upload bundle and contact Data Domain Support. Use these DD OS
commands to generate the support upload bundle:
# perf start trace
# perf stop trace trace.bin
# support upload bundle trace.bin
Otherwise, proceed to the next section and continue troubleshooting with the backup
server.
Pages/sec: when the number of pages per second exceeds 50 per paging disk on your
system, this indicates that there is not enough RAM to meet your server's needs.
Available Bytes: when the value is less than 10% of the actual RAM, this indicates that
insufficient memory is available.
When the Processor counter runs near 100% for extended periods, drill down at the
process level by examining the Process (instance)\% Processor Time counter for various
process instances on your system. This will help to determine if the system load is
handled effectively or if the system is underutilized.
The Disk Performance counters help you evaluate the performance of the disk
subsystem.
PhysicalDisk : Disk Reads Bytes/sec: use this counter to determine the disk
throughput for the disk subsystem.
LogicalDisk : Disk Reads Bytes/sec: for the partition, use this counter to see an
indication of the data transfer rate. A small value indicates a large number of random
reads of smaller sections.
Bytes received per second: this counter shows how many bytes of data are sent to the
NIC.
Bytes sent per second: this counter shows how many bytes are received from the NIC.
MTU size
Ensure that all of the other systems that are connected to the same switch (VLAN)
have jumbo frames enabled, and that the switch itself supports jumbo frames.
Network adapter
To ensure that the network adapter is not at fault, check the following:
10
All network interfaces of systems on the same network must have the same
network address.
The MTU sizes of systems on the same physical network or VPN must match.
The values for Ierrs and Oerrs should always be zero. If they are not, check the
network hardware and interfaces for problems. On Ethernet networks, the
collision field is not supported and always displays 0 (zero).