Veeam Backup and Symantec Backup Exec side by side


imageimage

In this post I will show you how easy it is to run Backup Exec Job when Veeam Backup is ready with his job.

First you have to configure your backup job. The only thing different to the “normal” configuration is the Schedule tab. Set the job to Run now. Submit the job and cancel the job.

image

You will see the job under the Job Setup.

image

Now we’re going to test the job. Open a command prompt and run the following command:

“C:\Program Files\Symantec\Backup Exec\bemcmd.exe” -o01 -jJobName_Backup

image

If everything went ok, the Backup job should be running now.

More information about bemcmd.exe can be found here: http://seer.entsupport.symantec.com and in one of my earlier posts: backup-exec-start-a-backup-job-from-the-commandline

Now there is only one thing we need to configure in Veeam Backup. Open the Veeam Backup Job. Go to the Backup Destination window and click on Advanced.

image

Enable the Run the following command check box and enter the bemcmd.exe commando which we used earlier in the command prompt. After that, enable the Run every 1 backup cycle checkbox too.

image

Now you’re ready to go! When the Veeam Backup job is ready, it will start the Backup job of Symante Backup Exec and writes the Veeam Backup file to the tape drive.

Backup Exec: Start a Backup Job from the Commandline


Today I found some information about the tool called bemcmd.exe. With this little tool you can run and create backup jobs in Symantec Backup Exec.

If you run bemcmd.exe /? >c:\bemcmd.txt a help file will be created. You can also download the file here: bemcmd.pdf

You can run a created job with the following command:

C:\Program Files\Symantec\Backup Exec\bemcmd.exe -o01 –j<backupjob>

image

As you can see, the backup job is started in Backup Exec.

image

BackupExec: Disable Corrupt Data Encounterd error.


Het kan zijn dat je Backup via Symantec Backup Exec in een error eindigt met de volgende foutmelding:

image

Deze melding kun je negeren. Hoe dit in zijn werk gaat lees je hier onder.

Voor Backup Exec 11/12

Als je deze melding wilt uitzetten voer je de volgende key in.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Backup]
"Fail Jobs On Corrupt Files"=dword:00000000

Als je deze melding wilt aanzetten voer je de volgende key in.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Backup]
"Fail Jobs On Corrupt Files"=dword:00000001

 

Voor Backup Exec 9/10

Als je deze melding wilt uitzetten voer je de volgende key in.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup]
"Fail Jobs On Corrupt Files"=dword:00000000

 
Als je deze melding wilt aanzetten voer je de volgende key in.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup]
"Fail Jobs On Corrupt Files"=dword:00000001

 

Bron: http://thebackroomtech.com/2008/12/04/howto-stop-backup-exec-from-failing-entire-backup-jobs-when-corrupt-files-are-encountered/

Citrix: Antivirus Strategy for Symantec Antivirus


De volgende processen kun je het beste uit de HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run verwijderen.  Zodra dit is gedaan worden deze processen niet meer in elke user sessie gestart en dat scheelt weer in het resource verbruik.

Process Info
ccApp Symantec Common Client User Session Process. ccApp calls the different program features in the Symantec products and makes sure that those programs are running, such as the Auto-Protect and E-mail Scanning mechanisms.
vptray Symantec Gold Shield Tray Icon. This is the Taskbar Icon and User Interface.

De poster op http://www.jhouseconsulting.com geeft nog de volgende tips mee

Tip Description
1 Scan local drives only. DO NOT scan network drives.
2 Only scan "Incoming" files (ie. write events).
3 Exclude the pagefile(s) from being scanned.
4 Exclude the "%ProgramFiles%\Citrix" folder from being scanned (the heavily accessed local host cache and Resource Manager local database are contained inside this folder).
5 We would recommend excluding the Profiles ("%SystemDrive%\Documents and Settings") folder, as well as the Print Spooler (%SystemRoot%\System32\spool\PRINTERS) folder.
6 If you do not exclude the Profiles, then exclude the user‘s Presentation Server Client bitmap cache ("%UserProfile%\Application Data\ICAClient\Cache" or "%AppData%\ICAClient\Cache") used for ICA pass-through connections by the locally installed PNClassic and PNAgent.

De bovenstaande tips kun je het beste instellen op een los staande antivirus group in Symantec System Center

image

Daarna kun je bij Exclusions de verschillende folders excluden.

image

Mocht je de Citrix Edgesite Agent op de Citrix server draaien, dan kun je het beste het volgende document nog even na te lopen: CTX111062

 

Bron: http://www.jhouseconsulting.com/articles/antivirus_strategy_for_citrix_servers.html

Backup Exec: Snapshot provider error (0x8007000E): Ran out of mem


Sinds ik SP2 op de SQL server had geïnstalleerd, kreeg ik de onderstaande foutmelding in mijn Backup Exec log file.

Click an error below to locate it in the job log


Backup- SQL1 
AOFO: Initialization failure on:
\\SQL\Shadow?Copy?Components.
Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0x8007000E): Ran out of memoryCheck the Windows Event Viewer for details.

Dit probleem kun je oplossen door de hotfix te bestellen die vermeldt word in het volgende KB document: KB940239

Symantec: Backup Exec and an error with Shadow Copy Components


De onderstaande foutmelding kreeg ik toen ik een SQL server wilde toevoegen in mijn backup list van Symantec Backup Exec 10d.

SQLServer_Shadow_copies_error

Meer informatie over deze foutmelding vind je hier: http://seer.entsupport.symantec.com/docs/291014.htm

 

Deze foutmelding kun je oplossen door de volgende dll opnieuw te registreren ole32.dll

Dit doe je als volgt: Start – Run – regsrv32 ole32.dll {Enter}

 

De oplossing kwam uit een post van Zhu [MSFT] welke je hier kunt vinden: http://forums.techarena.in/showthread.php?t=498777