Best practice for using Backup Exec System Recover with EMC Replication Manager or Storage Foundation and High Availability Solutions for Windows (SFWHA) and hotfix for symsnap.sys

Article:TECH124816  |  Created: 2010-01-06  |  Updated: 2013-10-25  |  Article URL http://www.symantec.com/docs/TECH124816
Article Type
Technical Solution

Product(s)

Environment

Subject

Issue



Best practice for using Backup Exec System Recover with EMC Replication Manager or Storage Foundation and High Availability Solutions for Windows (SFWHA) and hotfix for symsnap.sys


Solution



EMC Replication Manager (RM) manages the EMC point-in-time replication process. Using Backup Exec System Recovery (BESR) with RM requires BESR to be run in both GUI and script mode. GUI mode is setting up a job within the BESR interface. Script mode is creating a script file to perform BESR backups. This hotfix also resolves an issue of the server hanging with SFWHA configured with the disaster recovery (DR) solution/option.

To use BESR and RM effectively or BESR 2010 and SFWHA 5.1 Service Pack 1 Application Pack 1 (SP1 AP1) in a DR environment to avoid a server from hanging:

First, Install the latest symsnap.sys driver. To install this driver:
 

    1. Download the file attached to this technote. Extract either the 32-bit or 64-bit driver.
    2. Locate the symsnap.sys file in the \windows\system32\drivers\. Rename it to symsnap.old.
    3. Copy the new driver into this folder.
    4. Restart the computer.


Second, use the BESR GUI interface to create a backup job for the operating system volume. Setup the job and let it run either base images or base+incremental's. The operating system volume cannot contain the mounted volumes or mount points created by RM.

Third, use a script file to initiate a BESR backup of the volume(s) that contain the mount points created by RM. Integrate this script into RM process to run after the mount point(s) are created. Sample VB script files can be found on the BESR installation CD-ROM in the \docs\automation folder. Because the RM mount points are deleted when  the BESR job completes, setup the script job to create base images only. Incremental images will be as large as base images, and will use excess system resources.

Here are some additional guidelines when using BESR and RM together:
 

  • The RM mount(s) should be on a non-OS volume. This will speed up the process and will ensure that backups of the OS volume aren't affected by the RM mount/dismount processes, and vice-versa.
  • Use BESR GUI to backup the OS volume and the script file to backup the other volumes. The scripted backup should be integrated in the RM process, and should be base images only.
  • Image the mount-points created by RM and not the actual SAN LUNS.
  •  




 


Attachments

Symsnap_Hotfix_346933.zip (164 kBytes)

Supplemental Materials

SourceETrack
Value1880588
Description

BSOD with BESR + EMC Repplication Manager


SourceETrack
Value2055314
Description

[BESR coexist with DR]Primary site nodes or Secondary node works abnormal when install BESR agent on the machines in DR environment



Legacy ID



346933


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


Terms of use for this information are found in Legal Notices