Backup Exec System Recovery (BESR) Tips for Performance common issues

Article:TECH135344  |  Created: 2010-01-07  |  Updated: 2014-05-16  |  Article URL http://www.symantec.com/docs/TECH135344
Article Type
Technical Solution


Environment

Issue



Backup Exec System Recovery (BESR) Tips for Performance common issues


Solution



Backup Exec System Recovery (BESR) performance issues are most commonly fixed with basic tips that should be verified as a first  instance:
 
1° Is this a local backup? Is it backing files and/or folders on shared folder (mapped drive)?
Most backups will have a better performance and response being locally configured when compared to a backup running over a shared folder.  If compared to a version of Backup Exec for Windows Server  (BEWS) or with Backup Exec 2010, where remote agents are specifically designed to work remotely,  a performance difference can be noticed.
Tip: If the backup is being performed remotely, installing BESR locally to run the backup is recommended. If a performance difference is noticed, we can consider  the shared files as least recommended due to possible reasons such as: connectivity, NIC failures, or  just because of high network traffic.
Tip: Verify NIC configuration where Half or Full Duplex may be set. Use all NIC's as Full duplex or all NIC's as Half duplex. Do not mix.
 
2° What device is being used as Backup Destination?
BEWS allows devices such as tape libraries, stand-alone tape drives, SCSI or Fiber Channel connected, and USB external drives. All of these have a high byte transfer rate. On the other hand BESR only supports disk devices as Backup Destination.
Tip: To have a high byte transfer rate, not only the drive should be in optimal conditions, but connectivity to it should also be checked.
Tip: Avoid using RAID volumes.
Tip: Keep the Backup Destination drive constantly defragmented as maintenance.
 
3° Is the connectivity optimal?
This may seem obvious, but  obvious is usually ignored when it should not.
Tip: E.g. If the backup is going to a USB connected drive, verify the cable´s health, make sure the USB port is 2.0 and not 1.1, and connect the drive directly to a main USB port and not through a USB hub.
 
4° What is the drive format? (In case of USB connected)
Tip: If the backup is going to a USB connected drive, go to the Device Manager > Storage > Disk Management, and verify the disk is NTFS formatted. A high percentage of factory external drives come  with a FAT32 format.  If that is the case, format the disk and make it NTFS to obtain better performance results.
 
5° Tip: Verify the Windows has latest Microsoft recommended patches.
 
6° Tip: Run from a command Window SFC to check the integrity of the Windows installation.
 
7° Tip: Run from a command Window VSSADMIN LIST WRITERS (to check Writers State: Stable & No Errors.)
 
8° Tip: Run Chkdsk & Defrag to verify HDD integrity and to defrag it.
 
9° Tip: Verify which applications are running and the amount of connected users during the scheduled backup in order to analyze CPU load and NIC load.
 
 



Legacy ID



357305


Article URL http://www.symantec.com/docs/TECH135344


Terms of use for this information are found in Legal Notices