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.0.2 and BESR 8.0.3.


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.0.2 and BESR 8.0.3.


BESR 8 Backup Performance

BESR 8 has 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 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 show 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 large file. This is called spanning. The backup can be configured to do this by bringing up the Advanced Options dialog from the Options prompt of the Define Backup Wizard. The first check box on this dialog, “Divide into smaller files to simply archiving” specifies 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.

Beyond changing to use spanned recovery points, the default performance settings are recommended except in situations where the user's backup window must be highly optimized. To facilitate performance tuning in these limited situations, Symantec has included a set of registry (.reg) files that modify the default performance settings. In some cases the alternate settings may improve performance. Alternate performance settings generally have the most impact when the recovery point (V2i file) is being saved to a network share. When the recovery point is being saved to a second internal hard drive or to an external USB or Firewire hard drive, the default settings will generally provide the best results.

BESR backup performance across a network is affected by both the configuration of the machine running the backup and the network share where the backup is being created. The optimal settings for machine A backing up to network share N may not be the optimal settings when A backs up to network share M . If machine B is configured identically to machine A (same motherboard, NIC, OS version and patches), the settings that are optimal for A will generally also be optimal for B. However, if B is different from A, the optimal settings for A backing up to network share N may actually be poor for machine B backing up to this same destination.

BESR performance is also affected by the compression level that is selected. The optimal performance settings may vary depending on the 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 stand-alone, 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. Then, 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 aren't usually 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.

The zip available in this technote contains a total of ten files.  Five files are designed for an x86 system and the other five files are designed for a 64 bit system.  

NOTE: Only use the x86 registry files on 32 bit operating systems, and x64 registry files on a 64 bit operating systems.

NOTE: These registry files only work with BESR 8.0.2 and 8.0.3.  If using 8.0.1, it is recommended to update to a newer service pack, check performance and, if needed, apply the registry files.

AltPerformance1.reg: These settings frequently improve the performance of servers saving recovery points to a network share, making the backup 2-3 times faster. However, for some machines, most commonly laptops, they result in a slowdown that is 10-20 times slower than the default settings. Many machines will see no significant difference in performance with these settings.

AltPerformance2.reg: These are the default settings on single-processor, single-core computers. They are also the default setting used when the recovery point is not being compressed or encrypted. On a multi-processor and/or multi-core system, these settings restrict the compression and encryption to run on a single CPU. This will almost always result in slower performance when high compression is used. In some cases it may improve performance for Standard and Medium compression.

AltPerformance3.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.reg: This file will restore BESR to its default performance settings.

BESR8_03_Performance.reg: This file will configure BESR 8.0.2 to use the performance settings that are the default in BESR 8.0.3.  For 8.0.2 users who are experiencing performance problems, this should be the first registry file to be tried.  BESR 8.0.3 users should not use this file, but DefaultPerformance.reg instead.







Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)