cancel
Showing results for 
Search instead for 
Did you mean: 

How to identify the bottleneck for slow backups?

Sanya
Level 3

Hi,

 

I'm new in NetBackup and i have a customer that backups their 900GB of data for 2 days.

- 1Gbe backup via lan

–900 GB data size

–4 GB SAN Switch2.08

–2 x LTO3 tape drive

-NBU 6.5 (customer is planning to upgarde this year)

 

What are the thing i need to get from customer to determine the cause of the slow backups.

 

Thanks sanya

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

Finding the bottleneck and Performance Tuning is a lengthy process where you have to test the abilities of each component in the backup path. 

Please download the Performance Tuning Guide: http://www.symantec.com/docs/TECH62317

On a Solaris media server, you can use OS utilities (tar, dd, etc) to test the media server's ability to write to one tape drive at an acceptable rate. LTO3 should be able to write at +- 100MB/sec. 
Find something big enough on the media server itself to write to the tape drive. Test with one tape drive and then write to both drives simultaneously to test media server's ability to write to both drives.
Also see the above guide for ways to test media server.

Next, test client's ability to read data from disk.
Look in the above guide for the bpbkar test - the command is slightly different for Windows and Unix clients.
Do this test for each filesystem on the client.

Next test is the network.
Find +- 1GB file on the client and ftp to the media server.

The above tests will show where the bottleneck is. In most cases it's the client's ability to read and generate data stream.

View solution in original post

2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified

Finding the bottleneck and Performance Tuning is a lengthy process where you have to test the abilities of each component in the backup path. 

Please download the Performance Tuning Guide: http://www.symantec.com/docs/TECH62317

On a Solaris media server, you can use OS utilities (tar, dd, etc) to test the media server's ability to write to one tape drive at an acceptable rate. LTO3 should be able to write at +- 100MB/sec. 
Find something big enough on the media server itself to write to the tape drive. Test with one tape drive and then write to both drives simultaneously to test media server's ability to write to both drives.
Also see the above guide for ways to test media server.

Next, test client's ability to read data from disk.
Look in the above guide for the bpbkar test - the command is slightly different for Windows and Unix clients.
Do this test for each filesystem on the client.

Next test is the network.
Find +- 1GB file on the client and ftp to the media server.

The above tests will show where the bottleneck is. In most cases it's the client's ability to read and generate data stream.

revarooo
Level 6
Employee

Fully agree with Mariannes post. Also, if multiple clients are slow to the same storage unit, it's more likely than not, either the network or the backend storage destination. something to consider!