Improve performance when creating backups. These reg files can be used to improve slow performance when creating a recovery point with Backup Exec System Recovery 8.5 and 2010.
| Article:TECH125631 | | | Created: 2010-01-17 | | | Updated: 2012-07-06 | | | Article URL http://www.symantec.com/docs/TECH125631 |
Problem
Improve performance when creating backups. These .reg files can be used to improve slow performance when creating a recovery point with and Backup Exec System Recovery (BESR) 8.5 and 2010
Environment
NOTE: This document includes a downloadable zip that contains files designed for BESR 8.5 and BESR 2010.
Cause
BESR 8.5 and BESR 2010 have been configured to provide good performance for all users. Typically when a backup is saved locally, such as to an external (USB/Firewire) hard drive or to an internal hard drive, different from the drive containing the source volume, performance is very good. Performance issues are more common when the recovery point is being saved to a network destination, such as a NAS box or Windows share. Some network destinations exhibit very poor performance with very large files (more than 30 GB in size). An easy way to resolve this problem is to store the recovery point as a bunch of small files rather than a single big file. This is called spanning. Backup jobs can be configured to span by bringing up the Advanced Options dialog from the Options dialog of the Define Backup Wizard. The first check box on this dialog, "Divide into smaller files to simplify archiving" can be used to specify a span size. After checking the box, select 5078 from the "File size (MB)" drop down list. For very large recovery points, those resulting in files over 100 GB, performance is often two and sometimes as much as six times faster with this setting.
BESR performance is also affected by the compression level that is selected. The optimal performance settings may be different for different compression levels. On most systems with optimal performance settings, medium compression will provide the fastest performance, but it is generally very close in time to Standard compression.
The easiest way to test performance is to create a BESR job that creates standalone, independent full recovery points. Run this job once to find out how long a backup takes with the default settings. After the backup completes, delete the backup file so that the next backup can be saved to the same location. Next, double click on one of the performance .reg files to load that file's settings. Run the backup job again to see if there are any differences. Jobs can show slight variations so performance differences of less than 10% or less than 1 minute likely aren't meaningful. Typically, the best settings will be 2-3 times as fast as other settings. On many systems, multiple .reg files will provide essentially the same performance.
Solution
The zip available in this technote contains a total of eight files for each version of BESR. Four files are designed for an 32 bit system and the other four files are designed for a 64 bit system. In order to implement one of the .reg files, first extract out the .zip file. Then, browse in the extracted files to find the appropriate version (BESR8.5 or BESR 2010) and the appropriate operating system type (x86 or x64). Double-click on one of the .reg files and confirm the prompt to allow the merging of this information to the registry.
NOTE: Only use the x86 registry files on 32 bit operating systems, and x64 registry files on 64 bit operating systems.
AltPerformance3-x86.reg or AltPerformance3-x64.reg : This is a combination of the settings in AltPerformance1 and AltPerformance2. For single-processor, single-core systems or when the recovery point is not compressed or encrypted, these settings will be identical to AltPerformance1.
DefaultPerformance-x86.reg or DefaultPerformance-x64.reg: This file will restore BESR to its default performance settings.
Attachments
|
|
|
Related Articles
Legacy ID
345861
Article URL http://www.symantec.com/docs/TECH125631
Terms of use for this information are found in Legal Notices









Thank you.