Category: Backup

No log truncation on SQL 2012 with Veeam B&R

Today I had a SQL 2012 server with a log drive there was running full. Veeam 7 is setup with application awareness, and should truncate the log for all databases. But to my big surprise it did non of the kind. The scarey part is that Veeam did not repport any errors in the backup status/history log. It turns out that there is a KB on veeam’s website, pointing out that the local SYSTEM account do not have permissions to trunkate the log’s. So you will have to give the SYSTEM account these right on the SQL server from the SQL managment studio.
SQL2012_Veeam_log
I hope this will help you in some way, please leave a comment. Thanks for reading this!
   

Veeam error vm is disconnected

So to day a had a customer which Veeam 6.1 B&R show a lot of errors. The error show was: Error: VM ‘SERVERNAME’ (ref: ‘vm-144’) is ‘Disconnected’ The source and the destination where fine, so I¬†decided to see if the Patch 1 for veeam 6.1 was installed and it was not. The install process is the same as with 6.5 patch 1. After the patch was installed and the backup ran successfully again. ūüôā You can download the patch 1 for Veeam 6.1 from veeam’s website.
vm_discover_step2
Once more if you found this usefull, pleas comment below. Thanks!


Patch 1 for Veeam Backup & Replication 6.5

Veeam has released a patch for Veeam 6.5 You can download the patch from Veeam’s website. This patch fixes some issues with Veeam B&R 6.5, Veeam one, Veeam Explorer for SAN Snapshots and Veeam Explorer for Microsoft Exchange. Its a easy install and I recommend that you always keep you’re Veeam installation up-to-date.
First thing you have to do is to run the setup .exe file ūüôā
VP1_step1
Click next at the Welcome screen
VP1_step2
Next click ‘install’
VP1_step3


Upgrading Veeam Backup & Replication 6.1 to 6.5 Step-by-step

UPDATE: There is now a patch 3 out so be sure to use this. You can download the patch here Here is a step-by-step guide for upgrading Veeam 6.1 to 6.5. I have seen some post on the veeam forum regarding upgrading SQL 2005 express (standard in 6.1) to a newer version that is supported by Veaam B&R 6.5 this is not necessary, the installer will upgrade the SQL to the version used with Veeam R&B 6.5.
Download the latest installer from Veeam’s home page and run the .exe. The installer will check for prerequisites and prompt for installation and reboot if necessary.
step1
step2
Next the Veeam B&R installer will detect the older version and ask if you would like to upgrade, click ‘yes’
step3
A welcome- and EULA screen will show, click ‘next’ and ‘next’
step4


How to backup VMware vCenter Server Virtual Appliance (VCSA) with Veeam

When you use Veeam to backup a vCenter cluster that is running on vSphere 5.x VCSA, there is a chance you will get an error when trying to backup the VCSA it self. This only applies when you have Enable VMware tools quiescence in you backup job. One way to backup the VCSA is to make a separate job for the VCSA and uncheck “Enable VMware tools quiescence” in this job. Another way is to disable it from within the eg. “cluster backup job”.
First Edit the job containing the VCSA in the step called “Guest Processing” click the “Advanced” button.


Gratis Veeam Backup & Replication v6

Hvis du er¬†VMware¬†vExpert, VMware Certified Professional (VCP), VMware Certified Instructor (VCI) eller VMware User Group (VMUG) member kan du f√• en gratis, et √•rs, 2-socket NFR version af Veeam Backup & Replication v6. Udfyld skemaet p√• denne side og modtag en licens n√łgle. Du kan download Veeam Backup & Reolication her    

Symantec Backup Exec 2010 R2 sletter ikke snapshots

VMware agenten til Symantec’s Backup Exec 2010 R2 har et problem med at slette de snapshots den laver n√•r den tager en imagebackup af en VM, dette kan resultere i laaang cataloging jobs og i sidste end at backuppen fejler. Problemet er l√łst i R3 med alle updates. Man skal dog lige huske at slette alle de snapshots som BE har lavet. Log p√• dit vCenter med PowerCLI og brud denne kommando Get-VM | Get-Snapshot | where {$_.name -match “SYMC”} | fl VM, created ¬†til at se om der er nogle symantec snapshots der skal slettes. Her efter kan du via vSphere klienten g√• ind og slette de shapshots der ikke er blevet slettet fra BE side.