Review: PHD Virtual Backup


Before I start with this post I first want to welcome a new sponsor: PHD Virtual.

                                             

In this post I will be doing a short review, sponsored by PHD, of the latest version of PHD backup. In this post I will show the following topics:

  1. install the PHD Virtual Backup Console and Plug-in
  2. Deploy OVF template of the PHD Virtual Backup Appliance
  3. Configure the PHD Virtual Backup Appliance
  4. Add VMs to a Backup job
  5. Restore a complete VM
  6. Restore individual Files
  7. Conclusion

So let’s start with the installation.

Continue reading

Advertisements

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/

Proven practices for integrating Backup Software with VCB


image

Chris Skinner een Senior Technical Instructor at VMware PSO-Education heeft een aantal papers geschreven over het integreren van backup software en VCB.

Op de viops site van VMware kun je de volgende papers vinden:

 

 

Bron: http://www.ntpro.nl/blog/archives/692-Integrating-Symantec-Backup-Exec-12.5-with-VCB-1.5.html

Whitepaper: VMware and VSS: Application Backup and Recovery


Veeam schrijft het volgende:

More and more organizations are choosing VMware Infrastructure to virtualize their mission‐critical applications (Active Directory, Exchange, SharePoint, SQL Server) to create a flexible, easily administered virtual infrastructure.
Virtual machines (VMs) and any applications they contain must be protected against failure. Typically, in the virtual world, this is done by performing an image‐level backup of the whole machine (for instance, using VMware Consolidated Backup). This method results in what is known as a crash‐consistent image. Restoring a crash‐consistent image is essentially equivalent to rebooting a server after a hard reset. For operating systems, this has not been an issue, since they can easily handle this type of activity. For database applications as well as for applications featuring replication, however, such a restore will often result in lost data, data corruption, or application failure.
To illustrate this concept, let’s review the consequences of using different VM disaster recovery methods for one of the most common mission‐critical applications: a Microsoft Active Directory domain controller (DC). Depending on the solution used, the following results will be achieved:

image

Download de PDF hier: VMwareandVSS-ApplicationBackupandRecovery.pdf

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