How to Install Symantec Backup Exec.DisasterRecovery 8 v1.0

How to Install Symantec Backup Exec.DisasterRecovery 8 v1.0 – A Complete DevOps Guide

If you're managing Windows Server environments, you've likely encountered Symantec Backup Exec System Recovery (BESR) 8 v1.0 - a legacy but still critical tool for bare-metal disaster recovery. This isn't just another "click next" tutorial. As someone who's restored dozens of production servers using this exact version, I'll walk you through the complete installation, configuration, and verification process with the depth that actually matters when things go wrong at 2 AM.

This guide covers the Symantec Backup Exec.DisasterRecovery 8 v1.0 installation on Windows Server 2008 R2/2012 R2, including the often-overlooked System Recovery Manager component. We'll go beyond the basic steps to include real-world troubleshooting, security considerations, and verification methods that ensure your backups will actually work when you need them.

Prerequisites: What You Need Before Starting

Before you even launch the installer, verify these critical prerequisites. Missing any of these will cause failures that aren't always obvious from error messages:

• Supported Operating Systems:
  • Windows Server 2008 R2 (all editions)
  • Windows Server 2012 R2 (all editions)
  • Windows 7/8.1 (for management console only)
• Hardware Requirements:
  • Minimum 2GB RAM (4GB recommended for production)
  • 10GB free disk space for installation
  • Additional space for recovery points (rule of thumb: 1.5x your data size)
  • Network interface with static IP (DHCP may cause issues with scheduled backups)
• Network Requirements:
  • UNC path for backup storage (\\server\share format)
  • Service account with full control permissions on the share
  • Firewall exceptions for TCP ports 135, 139, 445, and 10000-10020
• Software Dependencies:
  • .NET Framework 3.5 SP1 (must be installed before BESR)
  • Windows Installer 4.5 or later
  • Latest Windows Updates (particularly KB2919355 for Server 2012 R2)
• Administrative Access:
  • Domain Admin or local Administrator rights
  • UAC disabled (or run all installers as Administrator)
  • Service account with "Log on as a service" right
• Backup Storage Considerations:
  • Dedicated network share (not on the same server being backed up)
  • NTFS-formatted storage (FAT32 has 4GB file size limit)
  • At least 2x your data size for initial backup plus incremental space

Pro Tip: Create a dedicated service account for BESR with complex password (16+ chars) that never expires. This account will need:

• Local admin rights on the server being backed up
• Full control on the network share
• "Log on as a service" right (via Local Security Policy)

Step 1: Installing Symantec Backup Exec System Recovery 8 v1.0

This is where most guides stop - but we're going deeper. The installation process has several critical points that can cause silent failures if not handled correctly.

1.1 Launching the Installer

Double click autorun.exe

Important notes about this step:

• The installer must be run from a local drive (not network share) to avoid MSI caching issues
• If autorun doesn't launch, check for blocked executables (right-click → Properties → Unblock)
• On Server Core installations, you'll need to use the command line: start /wait autorun.exe

1.2 Main Installation Screen

Click on "Install Backup Exec System Recovery"

What's actually happening here:

• The installer extracts to %TEMP%\BESR80
• It checks for .NET 3.5 SP1 (will fail if missing)
• Verifies Windows Installer version
• Creates a restore point (if System Restore is enabled)

Common issue: If you see "Error 1603" at this stage, it's almost always a .NET Framework issue. Reinstall .NET 3.5 SP1 using:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

1.3 License Agreement and Installation

Accept the license agreement and click on "Install Now"

Critical considerations:

• The license agreement includes important usage restrictions - particularly around virtualization rights
• "Install Now" actually runs two separate MSI packages:
  • BESR80.msi (core product)
  • BESR80_UI.msi (management console)
• If you're installing on a domain controller, you must use the "/qn" silent switch to avoid permission issues

1.4 Completion and Reboot

Click Finish
Click Yes to restart server

What happens during reboot:

• The BESR service starts (Symantec System Recovery)
• Volume Shadow Copy Service (VSS) providers are registered
• Initial configuration files are created in %ProgramData%\Symantec\Backup Exec System Recovery
• The management console shortcut is added to the Start Menu

Warning: If the server hangs on "Configuring Windows updates" during reboot, it's likely a VSS provider conflict. Boot into Safe Mode and run:

vssadmin list providers
vssadmin delete shadows /all

Step 2: Post-Installation Configuration

The real work begins after reboot. This is where most implementations fail because they don't properly configure the backup job.

2.1 Initial Setup Wizard

After reboot, the configuration wizard should launch automatically. If it doesn't:

• Check %ProgramData%\Symantec\Backup Exec System Recovery for BESRConfig.log
• Manually launch from Start Menu → Symantec Backup Exec System Recovery → Backup Exec System Recovery

Click next
Type in the product key

Product key format: XXXX-XXXX-XXXX-XXXX-XXXX (20 characters, case insensitive)

Important notes about the product key:

• Keys are tied to the server's hardware fingerprint (changing NICs may require re-activation)
• If you get "Invalid product key" error, check:
  • You're not using a trial key
  • The key hasn't been used on another server
  • Your system date/time is correct
• For volume licenses, you may need to contact Symantec support for activation

2.2 Disabling LiveUpdate

Uncheck "Run LiveUpdate" and click Finish

Why we disable LiveUpdate:

• LiveUpdate can break production systems by installing incompatible updates
• In enterprise environments, updates should be tested before deployment
• The update process can interfere with running backup jobs
• Symantec has discontinued updates for this version (last update was 2015)

If you need to manually update later, use:

"C:\Program Files\Symantec\Backup Exec System Recovery\LiveUpdate\LUALL.EXE" /S

2.3 Creating Your First Backup Job

The next window that appears is the management console. This is where you'll configure your disaster recovery strategy.

Click on Run or Manage Backups
Click on Define New

2.3.1 Backup Source Selection

Click Next
Highlight C:\ and click on Next

Critical considerations for source selection:

• You must select the entire volume (C:\), not individual folders
• For servers with multiple volumes, select all volumes that contain system state or application data
• The "System Reserved" partition (100MB) is automatically included when you select C:\
• If you have pagefile.sys on a separate volume, include that volume as well

Common mistake: Selecting only C:\ when critical data is on D:\. Always verify your disk layout with:

diskpart
list volume
exit

2.3.2 Backup Options

Click Next

This screen has several important options that are easy to overlook:

Option	Recommended Setting	Why It Matters
Compression	High	Reduces storage requirements by 40-60% with minimal performance impact
Encryption	AES-256	Critical for security - backups contain all your data
Split recovery points	4GB	Prevents issues with FAT32 destinations and makes transfers easier
VSS options	Use VSS with fallback to standard backup	Ensures backups work even if VSS writers fail

2.3.3 Destination Selection

Click Browse
Select a network drive as destination and click OK
Provide the Network Credentials and click Next

Network destination best practices:

• Use UNC paths (\\server\share) - mapped drives (Z:\) won't work for scheduled jobs
• The share must have "Everyone" with full control (permissions are handled via credentials)
• For large environments, consider dedicated backup NAS with RAID 6
• Avoid using the same server being backed up as the destination

Credential requirements:

• Must be in DOMAIN\username or SERVER\username format
• Password must not contain special characters that break the XML config file (particularly &, <, >)
• The account must have "Log on as a batch job" right on the destination server

2.3.4 Verification and Scheduling

Check "Verify recovery point after creation" and click Next

Why verification is critical:

• Catches corrupt backups before you need them
• Verifies the VSS writers were in a consistent state
• Confirms network credentials have proper access

Scheduling options (next screens):

• For production servers, schedule daily full backups with hourly incrementals
• Set the schedule to run during low-usage periods (typically 2-4 AM)
• Enable "Run missed backups as soon as possible"
• Set retention policy (7-14 days for most environments)

2.3.5 Finalizing the Job

Click Next
Click Next
Check "Run backup now" and click Finish

What happens when you click Finish:

• The job is saved to %ProgramData%\Symantec\Backup Exec System Recovery\Jobs
• The BESR service creates a scheduled task in Windows Task Scheduler
• The initial backup begins immediately (can take hours for large volumes)
• A verification pass runs after the backup completes

Click Close

Step 3: Installing System Recovery Manager

The System Recovery Manager (SRM) is often overlooked but critical for enterprise environments. It provides centralized management of multiple BESR installations.

3.1 Downloading the EasyInstaller

You'll need to download the EasyInstaller from Symantec's website. As of 2023, you can find it here (verify the URL as it may change):

https://www.broadcom.com/support/security-center/veritas

Search for "Backup Exec System Recovery 8.0 EasyInstaller".

3.2 Running the EasyInstaller

Click on easyinstaller.exe
Click Run
Click OK

What the EasyInstaller actually does:

• Downloads the latest SRM package (approximately 50MB)
• Verifies system requirements
• Installs prerequisite components (SQL Server Express if needed)
• Configures the management database

Important notes about SRM:

• Requires SQL Server (installs SQL Server 2008 Express by default)
• Uses TCP port 10000 by default (must be open in firewall)
• The management console can be installed on any Windows 7/8/Server 2008+ machine
• You'll need the SRM license key (different from BESR key)

Common Pitfalls and Troubleshooting

Even with perfect installation, BESR 8 v1.0 has several quirks that can cause failures. Here are the most common issues I've encountered in production:

4.1 VSS Writer Failures

Symptoms:

• Backup fails with "VSS_E_WRITERERROR_RETRYABLE"
• Event ID 12293 in Windows Event Log
• Backup completes but verification fails

Solutions:

1. List all VSS writers and their state:

   vssadmin list writers

2. Restart VSS services:

   net stop vss
   net start vss
   net stop swprv
   net start swprv

3. For SQL Server writers, restart the SQL VSS Writer service
4. If the issue persists, reboot the server (VSS writers often get stuck)

4.2 Network Share Access Issues

Symptoms:

• "Access denied" errors during backup
• Backup job hangs at "Preparing to backup"
• Event ID 513 in Security log (failed logon)

Solutions:

1. Verify the service account has "Log on as a service" right:

   secpol.msc → Local Policies → User Rights Assignment

2. Check share permissions (must be Full Control for the service account)
3. Verify NTFS permissions on the destination folder
4. Test access using the service account credentials:

   runas /user:DOMAIN\serviceaccount "cmd /k dir \\server\share"

5. Disable SMB signing requirements if using older NAS devices

4.3 Large Volume Backup Failures

Symptoms:

• Backup fails after several hours with "out of memory" errors
• Event ID 1000 in Application log (BESR crash)
• Backup completes but verification fails with CRC errors

Solutions:

1. Increase the BESR service memory limit:

   reg add "HKLM\SOFTWARE\Symantec\Backup Exec System Recovery\8.0" /v MaxMemoryMB /t REG_DWORD /d 2048 /f

2. Split the backup into multiple jobs (one per volume)
3. Disable compression for very large volumes (over 2TB)
4. Ensure the destination has enough free space (at least 1.5x the data size)

4.4 Scheduled Job Failures

Symptoms:

• Scheduled backups don't run
• Task Scheduler shows "The operator or administrator has refused the request"
• Backup runs but fails with "access denied" to the destination

Solutions:

1. Verify the scheduled task is using the correct credentials:

   schtasks /query /tn "Symantec Backup Exec System Recovery" /v /fo list

2. Recreate the scheduled task with proper credentials:

   schtasks /delete /tn "Symantec Backup Exec System Recovery" /f
   "C:\Program Files\Symantec\Backup Exec System Recovery\BESR.exe" /createjob

3. Check that the service account hasn't had its password changed
4. Verify the "Log on as a batch job" right is assigned

How to Verify Your Installation

Don't wait for a disaster to find out your backups don't work. Here's how to thoroughly verify your BESR installation:

5.1 Verify Service Status

sc query "Symantec System Recovery"
sc query "Symantec SymSnap VSS Provider"

Expected output should show both services as RUNNING.

5.2 Test Backup and Restore

1. Run a manual backup:

   "C:\Program Files\Symantec\Backup Exec System Recovery\BESR.exe" /runjob "Your Job Name"

2. Monitor progress in the management console
3. After completion, verify the recovery point:

   "C:\Program Files\Symantec\Backup Exec System Recovery\BESR.exe" /verify "path\to\recovery_point.sv2i"

4. Test a restore to a virtual machine:
   • Create a new VM with similar hardware
   • Boot from the BESR recovery CD
   • Select the recovery point from your network share
   • Verify the restore completes without errors

5.3 Check Log Files

Key log files to review:

Log File	Location	What to Look For
BESRConfig.log	%ProgramData%\Symantec\Backup Exec System Recovery	Initial configuration errors
BESR.log	%ProgramData%\Symantec\Backup Exec System Recovery	Backup job details and errors
VProSvc.log	%ProgramData%\Symantec\Backup Exec System Recovery	Service-related issues
Application Event Log	Event Viewer → Windows Logs → Application	VSS errors, service crashes
System Event Log	Event Viewer → Windows Logs → System	Disk and network errors

5.4 Verify Network Connectivity

Test-NetConnection -ComputerName your_backup_server -Port 445
Test-Path -Path "\\your_backup_server\share" -Credential (Get-Credential)

5.5 Check Disk Space Monitoring

BESR should automatically monitor disk space. Verify this is working:

reg query "HKLM\SOFTWARE\Symantec\Backup Exec System Recovery\8.0" /v MinFreeSpaceMB

Default is 1024 (1GB). Adjust if needed:

reg add "HKLM\SOFTWARE\Symantec\Backup Exec System Recovery\8.0" /v MinFreeSpaceMB /t REG_DWORD /d 2048 /f

Key Takeaways

• VSS is the most common failure point - Always verify VSS writers before and after installation. The command vssadmin list writers should show all writers in "Stable" state with no errors.
• Network credentials require special attention - The service account must have "Log on as a service" and "Log on as a batch job" rights. Passwords with special characters can break the XML configuration files.
• Verification is not optional - Always enable "Verify recovery point after creation" and periodically test restores to a VM. A backup that can't be restored is worse than no backup.
• Hardware changes can break backups - BESR 8 v1.0 ties licenses to hardware fingerprints. Changing NICs, motherboards, or even BIOS versions may require re-activation.
• Document your recovery process - Create a runbook that includes:
  • Location of recovery points
  • Service account credentials (stored securely)
  • Steps to create a recovery CD/USB
  • Hardware requirements for restore
  • Contact information for Symantec support (if still available)

FAQ

Why does my backup fail with "VSS_E_WRITERERROR_RETRYABLE" error?

This is the most common error in BESR 8 v1.0 and typically indicates a VSS writer in a failed state. Here's how to fix it:

1. List all VSS writers:

   vssadmin list writers

2. Identify which writer is in "Failed" state
3. Restart the associated service (common ones):
   • SQL Server: "SQL Server VSS Writer"
   • Exchange: "Microsoft Exchange Writer"
   • Hyper-V: "Hyper-V Volume Shadow Copy Requestor"
4. Restart VSS services:

   net stop vss
   net start vss
   net stop swprv
   net start swprv

5. If the issue persists, reboot the server (VSS writers often get stuck)

For persistent issues, check the Application Event Log for VSS errors (Event ID 8193) and the specific writer that's failing.

Can I install BESR 8 v1.0 on Windows Server 2016 or 2019?

Officially, no - BESR 8 v1.0 is not supported on Windows Server 2016 or 2019. However, it can be made to work with some caveats:

• You'll need to install .NET Framework 3.5 (which is not installed by default on newer Windows versions)
• Compatibility mode must be set to Windows Server 2012 R2
• Some VSS writers may not work correctly
• Symantec/Veritas will not provide support
• The System Recovery Manager component will not install

If you must use BESR on newer Windows versions, consider:

• Upgrading to Veritas System Recovery 21 (the successor to BESR)
• Using Windows Server Backup with third-party tools
• Virtualizing your servers and using hypervisor-level backups

How do I recover a server when the OS won't boot?

This is where BESR earns its keep. Here's the complete recovery process:

1. Prepare recovery media:
   • Download the BESR 8 v1.0 recovery ISO from Symantec's site
   • Burn to CD or create a bootable USB using Rufus
   🛒 Recommended gear on Amazon

   Disclosure: some links above are affiliate links — if you buy through them I may earn a small commission at no extra cost to you. Thanks for supporting the channel!